Handle some relative links

Author: adegeo

dotnet-desktop-guide/wpf/events/visual-basic-and-wpf-event-handling.md

@@ -65,4 +65,4 @@ The [Handles](/dotnet/visual-basic/language-reference/statements/handles-clause)
 - [Marking routed events as handled, and class handling](marking-routed-events-as-handled-and-class-handling.md)
 - [Routed events overview](routed-events-overview.md)
 - [Attached events overview](attached-events-overview.md)
-- [XAML in WPF](/dotnet/desktop/wpf/xaml)
+- [XAML overview](../xaml/index.md)

dotnet-desktop-guide/wpf/overview/index.md

@@ -27,7 +27,7 @@ There are two implementations of WPF:
 
     The .NET Framework implementation of WPF that's supported by Visual Studio 2019 and Visual Studio 2017.
 
-    .NET Framework 4 is a Windows-only version of .NET and is considered a Windows Operating System component. This version of WPF is distributed with .NET Framework. For more information about the .NET Framework version of WPF, see [Introduction to WPF for .NET Framework](../introduction-to-wpf.md?view=netframeworkdesktop-4.8&preserve-view=true).
+    .NET Framework 4 is a Windows-only version of .NET and is considered a Windows Operating System component. This version of WPF is distributed with .NET Framework.
 
 This overview is intended for newcomers and covers the key capabilities and concepts of WPF. To learn how to create a WPF app, see [Tutorial: Create a new WPF app](../get-started/create-app-visual-studio.md).
 

dotnet-desktop-guide/wpf/properties/dependency-properties-overview.md

@@ -166,7 +166,7 @@ The following example animates the <xref:System.Windows.Controls.Control.Backgro
 
 :::code language="xaml" source="./snippets/dependency-properties-overview/csharp/MainWindow.xaml" id="Animate":::
 
-For more about animating properties, see [Animation overview](../graphics-multimedia/animation-overview?view=netframeworkdesktop-4.8&preserve-view=true) and [Storyboards overview](/dotnet/desktop/wpf/graphics-multimedia/storyboards-overview.md)
+For more about animating properties, see [Animation overview](../graphics-multimedia/animation-overview) and [Storyboards overview](../graphics-multimedia/storyboards-overview.md)
 
 ### Metadata overrides
 

dotnet-desktop-guide/wpf/properties/framework-property-metadata.md

@@ -31,7 +31,7 @@ The article assumes a basic knowledge of dependency properties, and that you've
   > [!NOTE]
   > The term "inherits" in the context of property values is specific to dependency properties, and doesn't directly relate to managed code types and member inheritance through derived types. In the context of dependency properties, it means that child elements can inherit dependency property values from parent elements.
 
-- Data binding metadata, specifically the <xref:System.Windows.FrameworkPropertyMetadata.BindsTwoWayByDefault%2A> and <xref:System.Windows.FrameworkPropertyMetadata.IsNotDataBindable%2A> metadata flags. By default, dependency properties in the WPF framework support one-way binding. Consider setting two-way binding as the default for properties that report state *and* are modifiable by user action, for example <xref:System.Windows.Controls.Primitives.Selector.IsSelected>. Also, consider setting two-way binding as the default when users of a control expect a property to implement it, for example [TextBox.Text](<xref:System.Windows.Controls.TextBox.Text>). `BindsTwoWayByDefault` only affects the default binding mode. To edit the data flow direction of a binding, set [Binding.Mode](<xref:System.Windows.Data.Binding.Mode>). You can use `IsNotDataBindable` to disable data binding when there's no use case for it. For more information on data bindings, see [Data binding overview](/dotnet/desktop/wpf/data).
+- Data binding metadata, specifically the <xref:System.Windows.FrameworkPropertyMetadata.BindsTwoWayByDefault%2A> and <xref:System.Windows.FrameworkPropertyMetadata.IsNotDataBindable%2A> metadata flags. By default, dependency properties in the WPF framework support one-way binding. Consider setting two-way binding as the default for properties that report state *and* are modifiable by user action, for example <xref:System.Windows.Controls.Primitives.Selector.IsSelected>. Also, consider setting two-way binding as the default when users of a control expect a property to implement it, for example [TextBox.Text](<xref:System.Windows.Controls.TextBox.Text>). `BindsTwoWayByDefault` only affects the default binding mode. To edit the data flow direction of a binding, set [Binding.Mode](<xref:System.Windows.Data.Binding.Mode>). You can use `IsNotDataBindable` to disable data binding when there's no use case for it. For more information on data bindings, see [Data binding overview](../data/index.md).
 
 - Journaling metadata, specifically the <xref:System.Windows.FrameworkPropertyMetadata.Journal%2A> metadata flag. The default value of the `Journal` flag is only `true` for a some dependency properties, such as <xref:System.Windows.Controls.Primitives.Selector.SelectedIndex>. User input controls should set the `Journal` flag for properties whose values hold user selections that need to be stored. The `Journal` flag is read by applications or services that support journaling, including WPF journaling services. For information on storing navigation steps, see [Navigation overview](../app-development/navigation-overview.md)
 

dotnet-desktop-guide/xaml-services/xdata-intrinsic-xaml-type.md

@@ -44,12 +44,12 @@ Programmatic access to XML data and the `x:XData` intrinsic XAML type is possibl
 
 The `x:XData` object is primarily used as a child object of an <xref:System.Windows.Data.XmlDataProvider>, or alternatively, as the child object of the <xref:System.Windows.Data.XmlDataProvider.XmlSerializer%2A?displayProperty=nameWithType> property (in XAML, this is typically expressed in property element syntax).
 
-The data should typically redefine the base XML namespace within the data island to be a new default XML namespace (set to an empty string). This is easiest for simple data islands because the <xref:System.Windows.Data.Binding.XPath%2A> expressions that are used to reference and bind to the data can avoid inclusion of prefixes. More complex data islands might define multiple prefixes for the data and use a specific prefix for the XML namespace at the root. In this case, all <xref:System.Windows.Data.Binding.XPath%2A> expression references should include the appropriate namespace-mapped prefix. For more information, see [Data Binding Overview](../wpf/data/index.md?view=netdesktop-5.0&preserve-view=true).
+The data should typically redefine the base XML namespace within the data island to be a new default XML namespace (set to an empty string). This is easiest for simple data islands because the <xref:System.Windows.Data.Binding.XPath%2A> expressions that are used to reference and bind to the data can avoid inclusion of prefixes. More complex data islands might define multiple prefixes for the data and use a specific prefix for the XML namespace at the root. In this case, all <xref:System.Windows.Data.Binding.XPath%2A> expression references should include the appropriate namespace-mapped prefix. For more information, see [Data Binding Overview](../wpf/data/index.md).
 
 Technically, `x:XData` can be used as the content of any property of type <xref:System.Xml.Serialization.IXmlSerializable>. However, <xref:System.Windows.Data.XmlDataProvider.XmlSerializer%2A?displayProperty=nameWithType> is the only prominent implementation.
 
 ## See also
 
 - <xref:System.Windows.Data.XmlDataProvider>
-- [Data Binding Overview](../wpf/data/index.md?view=netdesktop-5.0&preserve-view=true)
+- [Data Binding Overview](../wpf/data/index.md)
 - [Binding Markup Extension](../wpf/advanced/binding-markup-extension.md)

dotnet-desktop-guide/xaml-services/xname-directive.md

@@ -49,7 +49,7 @@ Under the standard build configuration for a WPF application that uses XAML, par
 
 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).
 
-`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?view=netdesktop-5.0&preserve-view=true).
+`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).
 
 As mentioned previously, `x:Name` (or `Name`) should not be applied in situations that also use `x:Key`. The WPF <xref:System.Windows.ResourceDictionary> has a special behavior of defining itself as a XAML namescope but returning Not Implemented or null values for <xref:System.Windows.Markup.INameScope> APIs as a way to enforce this behavior. If the WPF XAML parser encounters `Name` or `x:Name` in a XAML-defined <xref:System.Windows.ResourceDictionary>, the name is not added to any XAML namescope. Attempting to find that name from any XAML namescope and the `FindName` methods will not return valid results.