Add docs verifier check (#2188)

adegeo · web-flow · commit 5330b6a6debf · 2026-02-17T14:02:24.000-08:00
* Add markdown-links-verifier-config.json file

* Add MSDocs build verifier workflow

* Hide .github folder from docs validation

Add step to hide .github folder before validation

* Fix links

* Update readme
diff --git a/.github/workflows/docs-verifier.yml b/.github/workflows/docs-verifier.yml
@@ -0,0 +1,29 @@
+name: MSDocs build verifier
+on: pull_request
+
+permissions:
+  contents: read
+
+env:
+  GITHUB_PR_NUMBER: ${{ github.event.pull_request.number }}
+  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+jobs:
+  validate:
+    name: MSDocs build verifier
+    runs-on: ubuntu-latest
+    steps:
+      - name: Harden Runner
+        uses: step-security/harden-runner@e3f713f2d8f53843e71c69a996d56f51aa9adfb9 # v2.14.1
+        with:
+          egress-policy: audit
+
+      - name: Checkout the repository
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+
+      - name: Hide .github folder from validate
+        run: |
+          rm -rf "${{ github.workspace }}/.github"
+
+      - name: Validate
+        uses: dotnet/docs-actions/actions/docs-verifier@5e8bcc78465d45a7544bba56509a1a69922b6a5a # main
diff --git a/README.md b/README.md
@@ -8,7 +8,7 @@ This repository contains the conceptual documentation for .NET desktop technolog
 
 We have a large community using these resources. We make our best effort to respond to issues in a timely fashion. You can read more about our procedures for classifying and resolving issues in our [Issues policy](issues-policy.md) topic.
 
-We welcome contributions to help us improve and complete the .NET docs. This is a very large repo, covering a large area. If this is your first visit, see our [labels and projects roadmap](styleguide/labels-projects.md) for help navigating the issues and projects in this repository.
+We welcome contributions to help us improve and complete the .NET docs.
 
 ## Migrate old examples
 
diff --git a/dotnet-desktop-guide/winforms/forms/events.md b/dotnet-desktop-guide/winforms/forms/events.md
@@ -106,7 +106,7 @@ When you need to update UI controls from background threads within async operati
 
 # [.NET](#tab/dotnet)
 
-.NET 9 introduced <xref:System.Windows.Forms.Control.InvokeAsync%2A?displayProperty=nameWithType>, which provides async-friendly marshaling to the UI thread. Unlike `Control.Invoke` which **sends** (blocks the calling thread), `Control.InvokeAsync` **posts** (non-blocking) to the UI thread's message queue. For more information about `Control.InvokeAsync`, see [How to make thread-safe calls to controls](../controls/how-to-make-thread-safe-calls.md#).
+.NET 9 introduced <xref:System.Windows.Forms.Control.InvokeAsync%2A?displayProperty=nameWithType>, which provides async-friendly marshaling to the UI thread. Unlike `Control.Invoke` which **sends** (blocks the calling thread), `Control.InvokeAsync` **posts** (non-blocking) to the UI thread's message queue. For more information about `Control.InvokeAsync`, see [How to make thread-safe calls to controls](../controls/how-to-make-thread-safe-calls.md).
 
 **Key advantages of InvokeAsync:**
 
diff --git a/dotnet-desktop-guide/wpf/advanced/annotations-overview.md b/dotnet-desktop-guide/wpf/advanced/annotations-overview.md
@@ -79,7 +79,7 @@ Another example scenario involves applications that enable the exchange of annot
 - <xref:System.Windows.Controls.FlowDocumentReader>
 - <xref:System.Windows.Annotations.IAnchorInfo>
 - [Annotations Schema](annotations-schema.md)
-- [ContextMenu Overview](../controls/contextmenu-overview.md)
+- [ContextMenu Overview](../controls/contextmenu.md)
 - [Commanding Overview](commanding-overview.md)
 - [Flow Document Overview](flow-document-overview.md)
 - [How to: Add a Command to a MenuItem](/previous-versions/dotnet/netframework-3.5/ms741839(v=vs.90))
diff --git a/dotnet-desktop-guide/wpf/advanced/hosting-win32-content-in-wpf.md b/dotnet-desktop-guide/wpf/advanced/hosting-win32-content-in-wpf.md
@@ -365,7 +365,7 @@ public partial class Window1 : Window {
 
 Which gives you:
 
-![Screenshot of the WPF app running.](./media/hosting-win32-content-in-wpf/windows-presentation-foundation-application.png)
+![Screenshot of the WPF app running.](./media/hosting-win32-content-in-wpf/windows-presentation-foundation-application.PNG)
 
 ## See also
 
diff --git a/dotnet-desktop-guide/wpf/advanced/how-to-handle-the-contextmenuopening-event.md b/dotnet-desktop-guide/wpf/advanced/how-to-handle-the-contextmenuopening-event.md
@@ -61,4 +61,4 @@ The final scenario, writing a handler that suppresses a menu totally, is uncommo
 - <xref:System.Windows.Controls.ContextMenu>
 - <xref:System.Windows.FrameworkElement.ContextMenu%2A?displayProperty=nameWithType>
 - [Base Elements Overview](base-elements-overview.md)
-- [ContextMenu Overview](../controls/contextmenu-overview.md)
+- [ContextMenu Overview](../controls/contextmenu.md)
diff --git a/dotnet-desktop-guide/wpf/advanced/how-to-use-a-thicknessconverter-object.md b/dotnet-desktop-guide/wpf/advanced/how-to-use-a-thicknessconverter-object.md
@@ -32,4 +32,4 @@ This example does not run.
 - <xref:System.Windows.Controls.Border>
 - [How to: Change the Margin Property](/previous-versions/dotnet/netframework-3.5/ms750561(v=vs.90))
 - [How to: Convert a ListBoxItem to a new Data Type](/previous-versions/dotnet/netframework-3.5/ms749147(v=vs.90))
-- [Panels Overview](../controls/panels-overview.md)
+- [Panels Overview](../controls/panel.md)
diff --git a/dotnet-desktop-guide/wpf/advanced/layout.md b/dotnet-desktop-guide/wpf/advanced/layout.md
@@ -159,12 +159,12 @@ Layout rounding is disabled by default. To enable layout rounding, set the <xref
 
 ## What's Next
 
-Understanding how elements are measured and arranged is the first step in understanding layout. For more information about the available <xref:System.Windows.Controls.Panel> elements, see [Panels Overview](../controls/panels-overview.md). To better understand the various positioning properties that can affect layout, see [Alignment, Margins, and Padding Overview](alignment-margins-and-padding-overview.md). When you are ready to put it all together in a lightweight application, see [Walkthrough: My first WPF desktop application](../get-started/walkthrough-my-first-wpf-desktop-application.md).
+Understanding how elements are measured and arranged is the first step in understanding layout. For more information about the available <xref:System.Windows.Controls.Panel> elements, see [Panels Overview](../controls/panel.md). To better understand the various positioning properties that can affect layout, see [Alignment, Margins, and Padding Overview](alignment-margins-and-padding-overview.md). When you are ready to put it all together in a lightweight application, see [Walkthrough: My first WPF desktop application](../get-started/walkthrough-my-first-wpf-desktop-application.md).
 
 ## See also
 
 - <xref:System.Windows.FrameworkElement>
 - <xref:System.Windows.UIElement>
-- [Panels Overview](../controls/panels-overview.md)
+- [Panels Overview](../controls/panel.md)
 - [Alignment, Margins, and Padding Overview](alignment-margins-and-padding-overview.md)
 - [Layout and Design](optimizing-performance-layout-and-design.md)
diff --git a/dotnet-desktop-guide/wpf/advanced/optimizing-performance-layout-and-design.md b/dotnet-desktop-guide/wpf/advanced/optimizing-performance-layout-and-design.md
@@ -49,7 +49,7 @@ The layout pass process is invoked again if any of the following actions occur:
 
 The complexity of the layout process is directly based on the layout behavior of the <xref:System.Windows.Controls.Panel>-derived elements you use. For example, a <xref:System.Windows.Controls.Grid> or <xref:System.Windows.Controls.StackPanel> control provides much more functionality than a <xref:System.Windows.Controls.Canvas> control. The price for this greater increase in functionality is a greater increase in performance costs. However, if you do not require the functionality that a <xref:System.Windows.Controls.Grid> control provides, you should use the less costly alternatives, such as a <xref:System.Windows.Controls.Canvas> or a custom panel.
 
-For more information, see [Panels Overview](../controls/panels-overview.md).
+For more information, see [Panels Overview](../controls/panel.md).
 
 ### Update Rather than Replace a RenderTransform
 
diff --git a/dotnet-desktop-guide/wpf/advanced/use-automatic-layout-overview.md b/dotnet-desktop-guide/wpf/advanced/use-automatic-layout-overview.md
@@ -57,7 +57,7 @@ Using the automatic layout approach requires a set of coding and design standard
 
 - Use <xref:System.Windows.Controls.DockPanel>, <xref:System.Windows.Controls.StackPanel>, and <xref:System.Windows.Controls.Grid> to position controls.
 
-For a discussion about various types of panels, see [Panels Overview](../controls/panels-overview.md).
+For a discussion about various types of panels, see [Panels Overview](../controls/panel.md).
 
 **Do not set a fixed size for a window**
 
diff --git a/dotnet-desktop-guide/wpf/controls/gridview.md b/dotnet-desktop-guide/wpf/controls/gridview.md
@@ -49,7 +49,7 @@ When defining the data field to display in a <xref:System.Windows.Controls.GridV
 
 To specify the alignment of content in a column of a <xref:System.Windows.Controls.GridView>, define a <xref:System.Windows.Controls.GridViewColumn.CellTemplate%2A>. Do not use the <xref:System.Windows.Controls.Control.HorizontalContentAlignment%2A> and <xref:System.Windows.Controls.Control.VerticalContentAlignment%2A> properties for <xref:System.Windows.Controls.ListView> content that is displayed by using a <xref:System.Windows.Controls.GridView>.
 
-To specify template and style properties for column headers, use the <xref:System.Windows.Controls.GridView>, <xref:System.Windows.Controls.GridViewColumn>, and <xref:System.Windows.Controls.GridViewColumnHeader> classes. For more information, see [GridView Column Header Styles and Templates Overview](gridview-column-header-styles-and-templates-overview.md).
+To specify template and style properties for column headers, use the <xref:System.Windows.Controls.GridView>, <xref:System.Windows.Controls.GridViewColumn>, and <xref:System.Windows.Controls.GridViewColumnHeader> classes. For more information, see [GridView Column Header Styles and Templates Overview](gridview.md).
 
 <a name="AddingVisualElementstoaGridViewView"></a>
 
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-build-a-standard-ui-dialog-box-by-using-grid.md b/dotnet-desktop-guide/wpf/controls/how-to-build-a-standard-ui-dialog-box-by-using-grid.md
@@ -36,4 +36,4 @@ Finally, the example adds three <xref:System.Windows.Controls.Button> elements t
 - <xref:System.Windows.Controls.Grid>
 - <xref:System.Windows.GridUnitType>
 - [Panel](panel.md)
-- [How-to Topics](grid-how-to-topics.md)
+- [How-to Topics](grid.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-create-an-expander-with-a-scrollviewer.md b/dotnet-desktop-guide/wpf/controls/how-to-create-an-expander-with-a-scrollviewer.md
@@ -28,5 +28,4 @@ Note that the example sets the <xref:System.Windows.FrameworkElement.Height%2A>
 ## See also
 
 - <xref:System.Windows.Controls.Expander>
-- [Expander Overview](expander-overview.md)
-- [How-to Topics](expander-how-to-topics.md)
+- [Expander Overview](expander.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-customize-the-thumb-size-on-a-scrollbar.md b/dotnet-desktop-guide/wpf/controls/how-to-customize-the-thumb-size-on-a-scrollbar.md
@@ -29,4 +29,4 @@ The following example creates a <xref:System.Windows.Controls.Primitives.ScrollB
 
 ## See also
 
-- [ScrollBar Styles and Templates](scrollbar-styles-and-templates.md)
+- [ScrollBar Styles and Templates](scrollbar.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-make-sure-that-a-gridsplitter-is-visible.md b/dotnet-desktop-guide/wpf/controls/how-to-make-sure-that-a-gridsplitter-is-visible.md
@@ -33,4 +33,4 @@ To prevent hidden <xref:System.Windows.Controls.GridSplitter> controls, do one o
 ## See also
 
 - <xref:System.Windows.Controls.GridSplitter>
-- [How-to Topics](gridsplitter-how-to-topics.md)
+- [How-to Topics](gridsplitter.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-override-the-panel-onrender-method.md b/dotnet-desktop-guide/wpf/controls/how-to-override-the-panel-onrender-method.md
@@ -32,5 +32,5 @@ Use the <xref:System.Windows.Controls.Panel.OnRender%2A> method in order to add
 ## See also
 
 - <xref:System.Windows.Controls.Panel>
-- [Panels Overview](panels-overview.md)
+- [Panels Overview](panel.md)
 - [Panel](panel.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-partition-space-by-using-the-dockpanel-element.md b/dotnet-desktop-guide/wpf/controls/how-to-partition-space-by-using-the-dockpanel-element.md
@@ -37,4 +37,4 @@ The compiled application yields a new UI that looks like this.
 ## See also
 
 - <xref:System.Windows.Controls.DockPanel>
-- [Panels Overview](panels-overview.md)
+- [Panels Overview](panel.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-resize-columns-with-a-gridsplitter.md b/dotnet-desktop-guide/wpf/controls/how-to-resize-columns-with-a-gridsplitter.md
@@ -36,4 +36,4 @@ The following example shows how to define a vertical <xref:System.Windows.Contro
 ## See also
 
 - <xref:System.Windows.Controls.GridSplitter>
-- [How-to Topics](gridsplitter-how-to-topics.md)
+- [How-to Topics](gridsplitter.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-resize-rows-with-a-gridsplitter.md b/dotnet-desktop-guide/wpf/controls/how-to-resize-rows-with-a-gridsplitter.md
@@ -38,4 +38,4 @@ The following example shows how to define a horizontal <xref:System.Windows.Cont
 ## See also
 
 - <xref:System.Windows.Controls.GridSplitter>
-- [How-to Topics](gridsplitter-how-to-topics.md)
+- [How-to Topics](gridsplitter.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-use-templates-to-style-a-listview-that-uses-gridview.md b/dotnet-desktop-guide/wpf/controls/how-to-use-templates-to-style-a-listview-that-uses-gridview.md
@@ -24,7 +24,7 @@ The following example shows how to use these <xref:System.Windows.Style> and <xr
 
 [!code-xaml[ListViewTemplate#GridViewColumnTemplate](~/samples/snippets/csharp/VS_Snippets_Wpf/ListViewTemplate/CS/window1.xaml#gridviewcolumntemplate)]
 
-The <xref:System.Windows.Controls.GridViewColumn.HeaderContainerStyle%2A> and <xref:System.Windows.Controls.GridViewColumn.HeaderTemplate%2A> are only two of several properties that you can use to customize column header appearance for a <xref:System.Windows.Controls.GridView> control. For more information, see [GridView Column Header Styles and Templates Overview](gridview-column-header-styles-and-templates-overview.md).
+The <xref:System.Windows.Controls.GridViewColumn.HeaderContainerStyle%2A> and <xref:System.Windows.Controls.GridViewColumn.HeaderTemplate%2A> are only two of several properties that you can use to customize column header appearance for a <xref:System.Windows.Controls.GridView> control. For more information, see [GridView Column Header Styles and Templates Overview](gridview.md).
 
 The following example shows how to define a <xref:System.Windows.DataTemplate> that customizes the appearance of the cells in a <xref:System.Windows.Controls.GridViewColumn>.
 
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-use-the-attached-properties-of-canvas-to-position-child-elements.md b/dotnet-desktop-guide/wpf/controls/how-to-use-the-attached-properties-of-canvas-to-position-child-elements.md
@@ -34,6 +34,6 @@ Each <xref:System.Windows.Controls.Button> is positioned relative to the parent
 - <xref:System.Windows.Controls.Canvas.Right%2A>
 - <xref:System.Windows.Controls.Canvas.Top%2A>
 - <xref:System.Windows.Controls.Button>
-- [Panels Overview](panels-overview.md)
+- [Panels Overview](panel.md)
 - [Canvas](canvas.md)
 - [Attached Properties Overview](../properties/attached-properties-overview.md)
diff --git a/dotnet-desktop-guide/wpf/controls/how-to-wrap-a-border-around-the-content-of-a-canvas.md b/dotnet-desktop-guide/wpf/controls/how-to-wrap-a-border-around-the-content-of-a-canvas.md
@@ -25,4 +25,4 @@ The following example shows how to display `Hello World!` inside a <xref:System.
 
 - <xref:System.Windows.Controls.Canvas>
 - <xref:System.Windows.Controls.Border>
-- [Panels Overview](panels-overview.md)
+- [Panels Overview](panel.md)
diff --git a/dotnet-desktop-guide/wpf/controls/scrollbar.md b/dotnet-desktop-guide/wpf/controls/scrollbar.md
@@ -93,4 +93,4 @@ The following table lists the visual states for the <xref:System.Windows.Control
 - <xref:System.Windows.Controls.VirtualizingStackPanel>
 - [Documents in WPF](../advanced/documents-in-wpf.md)
 - [How to: Create a Scroll Viewer](/previous-versions/dotnet/netframework-3.5/ms752352(v=vs.90))
-- [ScrollBar Styles and Templates](scrollbar-styles-and-templates.md)
+- [ScrollBar Styles and Templates](scrollbar.md)
diff --git a/dotnet-desktop-guide/wpf/controls/scrollviewer.md b/dotnet-desktop-guide/wpf/controls/scrollviewer.md
@@ -101,4 +101,4 @@ For additional information about document formats and presentation options, see
 - [Documents in WPF](../advanced/documents-in-wpf.md)
 - [How to: Create a Scroll Viewer](/previous-versions/dotnet/netframework-3.5/ms752352(v=vs.90))
 - [Layout](../advanced/layout.md)
-- [Panels Overview](panels-overview.md)
+- [Panels Overview](panel.md)
diff --git a/dotnet-desktop-guide/wpf/controls/wpf-content-model.md b/dotnet-desktop-guide/wpf/controls/wpf-content-model.md
@@ -190,7 +190,7 @@ The following classes inherit from the <xref:System.Windows.Controls.Panel> clas
 
 - <xref:System.Windows.Controls.WrapPanel>
 
-For more information, see [Panels Overview](panels-overview.md).
+For more information, see [Panels Overview](panel.md).
 
 <a name="classes_that_affects_the_appearance_of_a_uielement"></a>
 
diff --git a/dotnet-desktop-guide/wpf/data/data-templating-overview.md b/dotnet-desktop-guide/wpf/data/data-templating-overview.md
@@ -219,4 +219,4 @@ The example shows that with the use of <xref:System.Windows.HierarchicalDataTemp
 - [Find DataTemplate-Generated Elements](how-to-find-datatemplate-generated-elements.md)
 - [Styling and Templating](../controls/styles-templates-overview.md)
 - [Data Binding Overview](index.md)
-- [GridView Column Header Styles and Templates Overview](../controls/gridview-column-header-styles-and-templates-overview.md)
+- [GridView Column Header Styles and Templates Overview](../controls/gridview.md)
diff --git a/dotnet-desktop-guide/wpf/graphics-multimedia/wpf-graphics-rendering-overview.md b/dotnet-desktop-guide/wpf/graphics-multimedia/wpf-graphics-rendering-overview.md
@@ -122,7 +122,7 @@ The <xref:System.Windows.Controls.Button> control contains a <xref:Microsoft.Win
 
 ### Control Templates
 
-The key to the expansion of a control into a hierarchy of controls is the <xref:System.Windows.Controls.ControlTemplate>. A control template specifies the default visual hierarchy for a control. When you explicitly reference a control, you implicitly reference its visual hierarchy. You can override the default values for a control template to create a customized visual appearance for a control. For example, you could modify the background color value of the <xref:System.Windows.Controls.Button> control so that it uses a linear gradient color value instead of a solid color value. For more information, see [Button Styles and Templates](../controls/button-styles-and-templates.md).
+The key to the expansion of a control into a hierarchy of controls is the <xref:System.Windows.Controls.ControlTemplate>. A control template specifies the default visual hierarchy for a control. When you explicitly reference a control, you implicitly reference its visual hierarchy. You can override the default values for a control template to create a customized visual appearance for a control. For example, you could modify the background color value of the <xref:System.Windows.Controls.Button> control so that it uses a linear gradient color value instead of a solid color value. For more information, see [Button Styles and Templates](../controls/button.md).
 
 A user interface element, such as a <xref:System.Windows.Controls.Button> control, contains several vector graphics instruction lists that describe the entire rendering definition of a control. The following code shows a <xref:System.Windows.Controls.Button> control defined in markup.
 
diff --git a/dotnet-desktop-guide/wpf/properties/dependency-properties-overview.md b/dotnet-desktop-guide/wpf/properties/dependency-properties-overview.md
@@ -145,7 +145,7 @@ The following example sets the <xref:System.Windows.Controls.ContentControl.Cont
 > [!NOTE]
 > Bindings are treated as a local value, which means that if you set another local value, you'll eliminate the binding. For details, see [Dependency property value precedence](dependency-property-value-precedence.md).
 
-Dependency properties, or the <xref:System.Windows.DependencyObject> class, don't natively support <xref:System.ComponentModel.INotifyPropertyChanged> for notification of changes in `DependencyObject` source property value for data binding operations. For more about how to create properties for use in data binding that can report changes to a data binding target, see [Data binding overview](../data/data-binding-overview.md)
+Dependency properties, or the <xref:System.Windows.DependencyObject> class, don't natively support <xref:System.ComponentModel.INotifyPropertyChanged> for notification of changes in `DependencyObject` source property value for data binding operations. For more about how to create properties for use in data binding that can report changes to a data binding target, see [Data binding overview](../data/index.md)
 
 ### Styles
 
diff --git a/dotnet-desktop-guide/xaml-services/xname-directive.md b/dotnet-desktop-guide/xaml-services/xname-directive.md
@@ -47,7 +47,7 @@ Using.NET XAML Services, the backing logic for XAML namescope support can be def
 
 Under the standard build configuration for a WPF application that uses XAML, partial classes, and code-behind, the specified `x:Name` becomes the name of a field that is created in the underlying code when XAML is processed by a markup compilation build task, and that field holds a reference to the object. By default, the created field is internal. You can change field access by specifying the [x:FieldModifier attribute](xfieldmodifier-directive.md). In WPF and Silverlight, the sequence is that the markup compile defines and names the field in a partial class, but the value is initially empty. Then, a generated method named `InitializeComponent` is called from within the class constructor. `InitializeComponent` consists of `FindName` calls using each of the `x:Name` values that exist in the XAML-defined part of the partial class as input strings. The return values are then assigned to the like-named field reference to fill the field values with objects that were created from XAML parsing. The execution of `InitializeComponent` make it possible to reference the run time object graph using the `x:Name` / field name directly, rather than having to call `FindName` explicitly any time you need a reference to a XAML-defined object.
 
-For a WPF application that uses the Microsoft Visual Basic targets and includes XAML files with `Page` build action, a separate reference property is created during compilation that adds the `WithEvents` keyword to all elements that have an `x:Name`, to support `Handles` syntax for event handler delegates. This property is always public. For more information, see [Visual Basic and WPF Event Handling](../wpf/advanced/visual-basic-and-wpf-event-handling.md).
+For a WPF application that uses the Microsoft Visual Basic targets and includes XAML files with `Page` build action, a separate reference property is created during compilation that adds the `WithEvents` keyword to all elements that have an `x:Name`, to support `Handles` syntax for event handler delegates. This property is always public. For more information, see [Visual Basic and WPF Event Handling](../wpf/events/visual-basic-and-wpf-event-handling.md).
 
 `x:Name` is used by the WPF XAML processor to register a name into a XAML namescope at load time, even for cases where the page is not markup-compiled by build actions (for example, loose XAML of a resource dictionary). One reason for this behavior is because the `x:Name` is potentially needed for <xref:System.Windows.Data.Binding.ElementName%2A> binding. For details, see [Data Binding Overview](../wpf/data/index.md).
 
diff --git a/dotnet-desktop-guide/xaml-services/xnull-markup-extension.md b/dotnet-desktop-guide/xaml-services/xnull-markup-extension.md
diff --git a/markdown-links-verifier-config.json b/markdown-links-verifier-config.json
