merge main branch

dotnet-desktop-guide/framework/wpf/advanced/componentresourcekey-markup-extension.md

@@ -1,6 +1,7 @@
 ---
 title: "ComponentResourceKey Markup Extension"
 ms.date: "03/30/2017"
+ms.custom: devdivchpfy22
 f1_keywords: 
   - "ComponentResourceKey"
   - "ComponentResourceKeyExtension"
@@ -38,8 +39,8 @@ Defines and references keys for resources that are loaded from external assembli
   
 ## XAML Values  
   
-|||  
-|-|-|  
+| Value | Description |  
+|-------|-------------|  
 |`targetTypeName`|The name of the public common language runtime (CLR) type that is defined in the resource assembly.|  
 |`targetID`|The key for the resource. When resources are looked up, `targetID` will be analogous to the [x:Key Directive](/dotnet/desktop/xaml-services/xkey-directive) of the resource.|  
   

dotnet-desktop-guide/framework/wpf/advanced/documents-in-wpf.md

@@ -1,6 +1,7 @@
 ---
-title: "Documents"
+title: "Documents Overview"
 ms.date: "03/30/2017"
+ms.custom: devdivchpfy22
 ms.topic: overview
 helpviewer_keywords: 
   - "documents [WPF], packaging"
@@ -72,8 +73,8 @@ ms.assetid: 6e8db7bc-050a-4070-aa72-bb8c46e87ff8
 ### Package Components  
  The [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] packaging APIs allow application data and documents to be organized into a single portable unit. A ZIP file is one of the most common types of packages and is the default package type provided with [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)].  <xref:System.IO.Packaging.Package> itself is an abstract class from which <xref:System.IO.Packaging.ZipPackage> is implemented using an open standard XML and ZIP file architecture.  The <xref:System.IO.Packaging.Package.Open%2A> method uses <xref:System.IO.Packaging.ZipPackage> to create and use ZIP files by default. A package can contain three basic types of items:  
   
-|||  
-|-|-|  
+| Item | Description |  
+|------|-------------|  
 |<xref:System.IO.Packaging.PackagePart>|Application content, data, documents, and resource files.|  
 |<xref:System.IO.Packaging.PackageDigitalSignature>|[X.509 Certificate] for identification, authentication and validation.|  
 |<xref:System.IO.Packaging.PackageRelationship>|Added information related to the package or a specific part.|  

dotnet-desktop-guide/framework/wpf/advanced/documents.md

@@ -1,6 +1,7 @@
 ---
 title: "Documents"
 ms.date: "03/30/2017"
+ms.custom: devdivchpfy22
 f1_keywords: 
   - "AutoGeneratedOrientationPage"
 helpviewer_keywords: 

dotnet-desktop-guide/framework/wpf/advanced/dynamicresource-markup-extension.md

@@ -1,6 +1,7 @@
 ---
 title: "DynamicResource Markup Extension"
 ms.date: "03/30/2017"
+ms.custom: devdivchpfy22
 f1_keywords: 
   - "DynamicResource"
   - "DynamicResourceExtension"
@@ -30,8 +31,8 @@ Provides a value for any [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla
   
 ## XAML Values  
   
-|||  
-|-|-|  
+| Value | Description |  
+|-------|-------------|  
 |`key`|The key for the requested resource. This key was initially assigned by the [x:Key Directive](/dotnet/desktop/xaml-services/xkey-directive) if a resource was created in markup, or was provided as the `key` parameter when calling <xref:System.Windows.ResourceDictionary.Add%2A?displayProperty=nameWithType> if the resource was created in code.|  
   
 ## Remarks  

dotnet-desktop-guide/framework/wpf/advanced/how-to-alter-the-typography-of-text.md

@@ -1,7 +1,8 @@
 ---
-title: How to Alter the Typography of Text
+title: "How to alter the typography of text"
 description: To alter the telegraphy of text, set the telegraphy attribute. You can set the typographic property of text programmatically. You can see how altered and default telegraphy properties of text render on screen each with an example.
 ms.date: "03/30/2017"
+ms.custom: devdivchpfy22
 dev_langs: 
   - "csharp"
   - "vb"

dotnet-desktop-guide/net/wpf/events/how-to-create-a-custom-routed-event.md

@@ -59,18 +59,18 @@ In code-behind, the WPF application defines the `Handler_ConditionalClick` event
 When `CustomButton` is clicked:
 
 1. The `ConditionalClick` routed event is raised on `CustomButton`.
-1. The `Handler_ConditionalClick` event handler assigned to `CustomButton` is triggered.
+1. The `Handler_ConditionalClick` event handler attached to `CustomButton` is triggered.
 1. The `ConditionalClick` routed event traverses up the element tree to `StackPanel1`.
-1. The `Handler_ConditionalClick` event handler assigned to `StackPanel1` is triggered.
-1. The `ConditionalClick` routed event continues up the element tree potentially triggering other `ConditionalClick` event handlers assigned to other traversed elements.
+1. The `Handler_ConditionalClick` event handler attached to `StackPanel1` is triggered.
+1. The `ConditionalClick` routed event continues up the element tree potentially triggering other `ConditionalClick` event handlers attached to other traversed elements.
 
 The `Handler_ConditionalClick` event handler obtains the following information about the event that triggered it:
 
-- The [sender](xref:System.Windows.RoutedEventHandler) object, which is the element that the event handler is assigned to. The `sender` will be `CustomButton` the first time the handler runs, and `StackPanel1` the second time.
+- The [sender](xref:System.Windows.RoutedEventHandler) object, which is the element that the event handler is attached to. The `sender` will be `CustomButton` the first time the handler runs, and `StackPanel1` the second time.
 - The <xref:System.Windows.RoutedEventArgs.Source?displayProperty=nameWithType> object, which is the element that originally raised the event. In this example, the `Source` is always `CustomButton`.
 
 > [!NOTE]
-> A key difference between a routed event and a CLR event is that a routed event traverses the element tree, looking for handlers, whereas a CLR event is created by a source object and handled by an event subscriber. As a result, a routed event `sender` can be any traversed element in the element tree.
+> A key difference between a routed event and a CLR event is that a routed event traverses the element tree, looking for handlers, whereas a CLR event doesn't traverse the element tree and handlers can only attach to the source object that raised the event. As a result, a routed event `sender` can be any traversed element in the element tree.
 
 You can create a tunneling event the same way as a bubbling event, except you'll set the routing strategy in the event registration call to <xref:System.Windows.RoutingStrategy.Tunnel>. For more information on tunneling events, see [WPF input events](/dotnet/desktop/wpf/advanced/routed-events-overview?view=netframeworkdesktop-4.8&preserve-view=true#wpf-input-events).