fix reference enum field - Part 5 (#3094)

* fix reference enum field

* Apply suggestions from docs review

Co-Authored-By: Ron Petrusha <[email protected]>

* Apply suggestions from docs review 2

* feedback

* fix broken link

Author: mairaw

xml/System.Windows.Media/BitmapScalingMode.xml

@@ -19,12 +19,12 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When animating the scale of any bitmap, the default high-quality image re-sampling algorithm can sometimes consume sufficient system resources to cause frame rate degradation. This frame rate degradation can cause animations to skip frames or stutter. By setting the <xref:System.Windows.Media.RenderOptions.BitmapScalingMode%2A> property of the <xref:System.Windows.Media.RenderOptions> object to LowQuality you can create a smoother animation when scaling a bitmap.  
+ When animating the scale of any bitmap, the default high-quality image resampling algorithm can sometimes consume sufficient system resources to cause frame rate degradation. This frame rate degradation can cause animations to skip frames or stutter. By setting the <xref:System.Windows.Media.RenderOptions.BitmapScalingMode%2A?displayProperty=nameWithType> property to `LowQuality`, you can create a smoother animation when scaling a bitmap.  
   
    
   
 ## Examples  
- The following example shows how to set the <xref:System.Windows.Media.BitmapScalingMode.LowQuality> for an image object.  
+ The following example shows how to use the <xref:System.Windows.Media.RenderOptions.SetBitmapScalingMode%2A?displayProperty=nameWithType> method to set the bitmap scale mode to `LowQuality` for an image object:
   
  [!code-csharp[RenderOptions#RenderOptionsSnippet2](~/samples/snippets/csharp/VS_Snippets_Wpf/RenderOptions/CSharp/Window1.xaml.cs#renderoptionssnippet2)]
  [!code-vb[RenderOptions#RenderOptionsSnippet2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/RenderOptions/visualbasic/window1.xaml.vb#renderoptionssnippet2)]  

xml/System.Windows.Media/EdgeMode.xml

@@ -19,14 +19,14 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Text objects are always displayed by using anti aliasing, and are not affected by setting the edge mode value. The default value for non-text drawing primitives, such as <xref:System.Windows.Shapes.Ellipse> and <xref:System.Windows.Shapes.Polygon>, is Unspecified.  
+ Text objects are always displayed by using anti aliasing and are not affected by setting the edge mode value. The default value for non-text drawing primitives, such as <xref:System.Windows.Shapes.Ellipse> and <xref:System.Windows.Shapes.Polygon>, is `Unspecified`.  
   
- When you set the edge mode value of a visual object, all the child drawing primitives of that visual object are set to the same <xref:System.Windows.Media.EdgeMode.Unspecified> value.  
+ When you set the edge mode value of a visual object, all the child drawing primitives of that visual object are set to the same `EdgeMode` value.  
   
    
   
 ## Examples  
- The following example shows how to use the <xref:System.Windows.Media.RenderOptions.SetEdgeMode%2A> method to set the edge mode for a drawing primitive to Aliased.  
+ The following example shows how to use the <xref:System.Windows.Media.RenderOptions.SetEdgeMode%2A?displayProperty=nameWithType> method to set the edge mode for a drawing primitive to `Aliased`:  
   
  [!code-csharp[VisualSnippets#SetEdgeMode](~/samples/snippets/csharp/VS_Snippets_Wpf/VisualSnippets/CSharp/Snippets.cs#setedgemode)]
  [!code-vb[VisualSnippets#SetEdgeMode](~/samples/snippets/visualbasic/VS_Snippets_Wpf/VisualSnippets/visualbasic/snippets.vb#setedgemode)]  

xml/System.Windows.Media/HitTestFilterBehavior.xml

@@ -19,18 +19,18 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The return value of the hit test filter callback is a <xref:System.Windows.Media.HitTestFilterBehavior>, which determines what type of action should be taken when processing the visual tree for hit testing. For example, if your hit test filter callback return the value, ContinueSkipSelfAndChildren, you can remove the current visual object and its descendants from the hit test results evaluation.  
+ The return value of the hit test filter callback is a `HitTestFilterBehavior`, which determines what type of action should be taken when processing the visual tree for hit testing. For example, if your hit test filter callback returns the value `ContinueSkipSelfAndChildren`, you can remove the current visual object and its descendants from the hit test results evaluation.  
   
 > [!NOTE]
->  Pruning the visual tree of objects decreases the amount of processing that is required during the hit test results evaluation pass.  
-  
- ![Pruning a visual tree using a hit test filter](~/add/media/filteredvisualtree-01.png "Pruning a visual tree using a hit test filter")  
+> Pruning the visual tree of objects decreases the amount of processing that is required during the hit test results evaluation pass.  
+>
+> ![Pruning a visual tree using a hit test filter](~/add/media/filteredvisualtree-01.png "Pruning a visual tree using a hit test filter")  
 Pruning a visual tree  
   
    
   
 ## Examples  
- The following example shows how to return a <xref:System.Windows.Media.HitTestFilterBehavior.ContinueSkipSelfAndChildren> value from a hit test filter callback method. In this case, the filter skips labels and their descendants and hit tests everything else.  
+ The following example shows how to return a `HitTestFilterBehavior` value from a hit test filter callback method. In this case, the filter skips labels and their descendants and hit tests everything else.  
   
  [!code-csharp[HitTestingOverview#106](~/samples/snippets/csharp/VS_Snippets_Wpf/HitTestingOverview/CSharp/Window1.xaml.cs#106)]
  [!code-vb[HitTestingOverview#106](~/samples/snippets/visualbasic/VS_Snippets_Wpf/HitTestingOverview/visualbasic/window1.xaml.vb#106)]  

xml/System.Windows.Media/HitTestResultBehavior.xml

@@ -19,14 +19,14 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A hit test results callback method defines the actions that you perform when a hit test is identified on a particular visual object in the visual tree. After you perform the actions, you return a <xref:System.Windows.Media.HitTestResultBehavior> value that determines whether to continue the enumeration of any other visual objects.  
+ A hit test results callback method defines the actions that you perform when a hit test is identified on a particular visual object in the visual tree. After you perform the actions, you return a `HitTestResultBehavior` value that determines whether to continue the enumeration of any other visual objects.  
   
- You can enumerate all visual objects in a visual tree whose geometry contains a specified coordinate value. By returning Continue in your hit test callback method, you can identify all visual objects that are hit, even those that may be partly or wholly obscured by other visual objects.  
+ You can enumerate all visual objects in a visual tree whose geometry contains a specified coordinate value. By returning `Continue` in your hit test callback method, you can identify all visual objects that are hit, even those that may be partly or wholly obscured by other visual objects.  
   
    
   
 ## Examples  
- The following example shows how to return a <xref:System.Windows.Media.HitTestResultBehavior.Continue> value from a hit test results callback method.  
+ The following example shows how to return a `HitTestResultBehavior` value from a hit test results callback method.  
   
  [!code-csharp[HitTestingOverview#102](~/samples/snippets/csharp/VS_Snippets_Wpf/HitTestingOverview/CSharp/Window1.xaml.cs#102)]
  [!code-vb[HitTestingOverview#102](~/samples/snippets/visualbasic/VS_Snippets_Wpf/HitTestingOverview/visualbasic/window1.xaml.vb#102)]  

xml/System.Windows.Threading/DispatcherPriority.xml

@@ -19,14 +19,14 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- There is no specific system state or "idleness" corresponding to ApplicationIdle and ContextIdle in the current version of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  Both are still valid priorities; therefore, an operation with a priority of ContextIdle has a higher priority than an operation with a priority of SystemIdle.  
+ There is no specific system state or "idleness" corresponding to `ApplicationIdle` and `ContextIdle` in the current version of WPF. Both are still valid priorities; an operation with a priority of `ContextIdle` has a higher priority than an operation with a priority of `SystemIdle`.  
   
- The <xref:System.Windows.Threading.DispatcherPriority.ApplicationIdle> does not throttle the execution of an operation if it exceeds a certain percentage of the CPU.  One way to throttle a process it to use a timer.  
+ The <xref:System.Windows.Threading.Dispatcher> does not throttle the execution of an operation if it exceeds a certain percentage of the CPU. One way to throttle a process it to use a timer.  
   
- If an operation is posted using <xref:System.Windows.Threading.Dispatcher.Invoke%2A> on its own <xref:System.Windows.Threading.DispatcherPriority.ContextIdle> at a priority of Send, the operation bypasses the queue and is immediately executed.  
+ If an operation is posted using <xref:System.Windows.Threading.Dispatcher.Invoke%2A?displayProperty=nameWithType> on its own <xref:System.Windows.Threading.Dispatcher> at a priority of `Send`, the operation bypasses the queue and is immediately executed.  
   
 ## Examples  
- The following example is a call to <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A> that passes a delegate which accepts an argument.  The priority is set to Normal.  
+ The following example calls the <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A?displayProperty=nameWithType> method and passes it a delegate with one argument. The priority is set to `Normal`.
   
  [!code-csharp[ThreadingWeatherForecast#ThreadingWeatherDispatcherOneArge](~/samples/snippets/csharp/VS_Snippets_Wpf/ThreadingWeatherForecast/CSharp/Window1.xaml.cs#threadingweatherdispatcheronearge)]
  [!code-vb[ThreadingWeatherForecast#ThreadingWeatherDispatcherOneArge](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThreadingWeatherForecast/visualbasic/window1.xaml.vb#threadingweatherdispatcheronearge)]  
@@ -53,7 +53,7 @@
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>The enumeration value is 2.  Operations are processed when the application is idle.</summary>
+        <summary>The enumeration value is 2. Operations are processed when the application is idle.</summary>
       </Docs>
     </Member>
     <Member MemberName="Background">
@@ -74,7 +74,7 @@
       </ReturnValue>
       <MemberValue>4</MemberValue>
       <Docs>
-        <summary>The enumeration value is 4.  Operations are processed after all other non-idle operations are completed.</summary>
+        <summary>The enumeration value is 4. Operations are processed after all other non-idle operations are completed.</summary>
       </Docs>
     </Member>
     <Member MemberName="ContextIdle">
@@ -95,7 +95,7 @@
       </ReturnValue>
       <MemberValue>3</MemberValue>
       <Docs>
-        <summary>The enumeration value is 3.  Operations are processed after background operations have completed.</summary>
+        <summary>The enumeration value is 3. Operations are processed after background operations have completed.</summary>
       </Docs>
     </Member>
     <Member MemberName="DataBind">
@@ -116,7 +116,7 @@
       </ReturnValue>
       <MemberValue>8</MemberValue>
       <Docs>
-        <summary>The enumeration value is 8.  Operations are processed at the same priority as data binding.</summary>
+        <summary>The enumeration value is 8. Operations are processed at the same priority as data binding.</summary>
       </Docs>
     </Member>
     <Member MemberName="Inactive">
@@ -137,7 +137,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>The enumeration value is 0.  Operations are not processed.</summary>
+        <summary>The enumeration value is 0. Operations are not processed.</summary>
       </Docs>
     </Member>
     <Member MemberName="Input">
@@ -158,7 +158,7 @@
       </ReturnValue>
       <MemberValue>5</MemberValue>
       <Docs>
-        <summary>The enumeration value is 5.  Operations are processed at the same priority as input.</summary>
+        <summary>The enumeration value is 5. Operations are processed at the same priority as input.</summary>
       </Docs>
     </Member>
     <Member MemberName="Invalid">
@@ -179,7 +179,7 @@
       </ReturnValue>
       <MemberValue>-1</MemberValue>
       <Docs>
-        <summary>The enumeration value is -1.  This is an invalid priority.</summary>
+        <summary>The enumeration value is -1. This is an invalid priority.</summary>
       </Docs>
     </Member>
     <Member MemberName="Loaded">
@@ -200,7 +200,7 @@
       </ReturnValue>
       <MemberValue>6</MemberValue>
       <Docs>
-        <summary>The enumeration value is 6.  Operations are processed when layout and render has finished but just before items at input priority are serviced. Specifically this is used when raising the Loaded event.</summary>
+        <summary>The enumeration value is 6. Operations are processed when layout and render has finished but just before items at input priority are serviced. Specifically this is used when raising the Loaded event.</summary>
       </Docs>
     </Member>
     <Member MemberName="Normal">
@@ -221,7 +221,7 @@
       </ReturnValue>
       <MemberValue>9</MemberValue>
       <Docs>
-        <summary>The enumeration value is 9.  Operations are processed at normal priority.  This is the typical application priority.</summary>
+        <summary>The enumeration value is 9. Operations are processed at normal priority. This is the typical application priority.</summary>
       </Docs>
     </Member>
     <Member MemberName="Render">
@@ -242,7 +242,7 @@
       </ReturnValue>
       <MemberValue>7</MemberValue>
       <Docs>
-        <summary>The enumeration value is 7.  Operations processed at the same priority as rendering.</summary>
+        <summary>The enumeration value is 7. Operations processed at the same priority as rendering.</summary>
       </Docs>
     </Member>
     <Member MemberName="Send">
@@ -263,7 +263,7 @@
       </ReturnValue>
       <MemberValue>10</MemberValue>
       <Docs>
-        <summary>The enumeration value is 10.  Operations are processed before other asynchronous operations.  This is the highest priority.</summary>
+        <summary>The enumeration value is 10. Operations are processed before other asynchronous operations. This is the highest priority.</summary>
       </Docs>
     </Member>
     <Member MemberName="SystemIdle">
@@ -284,7 +284,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>The enumeration value is 1.  Operations are processed when the system is idle.</summary>
+        <summary>The enumeration value is 1. Operations are processed when the system is idle.</summary>
       </Docs>
     </Member>
   </Members>

xml/System.Windows/FrameworkPropertyMetadataOptions.xml

@@ -24,19 +24,19 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this enumeration when you construct a <xref:System.Windows.FrameworkPropertyMetadata> instance where you want to specify one or more  the framework-level metadata option settings.  
+ Use this enumeration when you construct a <xref:System.Windows.FrameworkPropertyMetadata> instance, and you want to specify one or more the framework-level metadata option settings.  
   
- You no longer use this enumeration after the constructor call. Instead, query the particular metadata option that was set during registration by checking the `true` or `false` value of a specific property of an existing <xref:System.Windows.FrameworkPropertyMetadata>. These property names match the <xref:System.Windows.FrameworkPropertyMetadataOptions> enumeration values except for NotDataBindable, which is <xref:System.Windows.FrameworkPropertyMetadata.IsNotDataBindable%2A> on the finished <xref:System.Windows.FrameworkPropertyMetadata.IsNotDataBindable%2A>.  
+ You no longer use this enumeration after the constructor call. Instead, query the particular metadata option that was set during registration by checking the `true` or `false` value of a specific property of an existing <xref:System.Windows.FrameworkPropertyMetadata>. These property names match the `FrameworkPropertyMetadataOptions` enumeration values except for NotDataBindable, which is <xref:System.Windows.FrameworkPropertyMetadata.IsNotDataBindable%2A> on the finished <xref:System.Windows.FrameworkPropertyMetadata>.  
   
- The Journal option only specifies the intention to be journaled. The actual journaling may or may not be addressed by journaling services such as those that are present in the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] viewer application. In particular, journaling has some known limitations if the element tree was constructed through code rather than [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. For details, see [Navigation Overview](~/docs/framework/wpf/app-development/navigation-overview.md).  
+ The `Journal` option only specifies the intention to be journaled. The actual journaling may or may not be addressed by journaling services such as those that are present in the WPF viewer application. In particular, journaling has some known limitations if the element tree was constructed through code rather than XAML. For details, see [Navigation Overview](~/docs/framework/wpf/app-development/navigation-overview.md).  
   
 > [!NOTE]
->  Although property value inheritance might appear to work for nonattached dependency properties, the inheritance behavior for a nonattached property through certain element boundaries 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.  
+> Although property value inheritance might appear to work for nonattached dependency properties, the inheritance behavior for a nonattached property through certain element boundaries in the runtime tree is undefined. Always use the <xref:System.Windows.DependencyProperty.RegisterAttached%2A?displayProperty=nameWithType> method to register properties where you specify <xref:System.Windows.FrameworkPropertyMetadata.Inherits%2A?displayProperty=nameWithType> in the metadata.  
   
    
   
 ## Examples  
- The following example calls the <xref:System.Windows.FrameworkPropertyMetadata> constructor, and sets several options by using values from the <xref:System.Windows.FrameworkPropertyMetadataOptions> enumeration.  
+ The following example calls the <xref:System.Windows.FrameworkPropertyMetadata> constructor and sets several options by using values from the `FrameworkPropertyMetadataOptions` enumeration:
   
  [!code-csharp[PropertyMetadataAPIs#FPMCtor_DV_FPMO_PCC_CVC](~/samples/snippets/csharp/VS_Snippets_Wpf/PropertyMetadataAPIs/CSharp/Class1.cs#fpmctor_dv_fpmo_pcc_cvc)]  
   
@@ -209,7 +209,7 @@
       </ReturnValue>
       <MemberValue>1024</MemberValue>
       <Docs>
-        <summary>The values of this dependency property should be saved or restored by journaling processes, or when navigating by [!INCLUDE[TLA#tla_uri#initcap#plural](~/includes/tlasharptla-urisharpinitcapsharpplural-md.md)].</summary>
+        <summary>The values of this dependency property should be saved or restored by journaling processes, or when navigating by Uniform resource identifiers (URIs).</summary>
       </Docs>
     </Member>
     <Member MemberName="None">
@@ -230,7 +230,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>No options are specified; the dependency property uses the default behavior of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] property system.</summary>
+        <summary>No options are specified; the dependency property uses the default behavior of the WPF property system.</summary>
       </Docs>
     </Member>
     <Member MemberName="NotDataBindable">