From b2ecf3bbe00be0345ad1cbd1dcdfce1a4eea9275 Mon Sep 17 00:00:00 2001
From: Ron Petrusha <ronpet@microsoft.com>
Date: Fri, 20 Oct 2017 15:30:41 -0700
Subject: [PATCH] Duplicating changes made in dotnet/docs PR #3464 (#532)

---
 ...e-overloads-could-result-in-different-behavior.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/Documentation/compatibility/new-(ambiguous)-dispatcher_invoke-overloads-could-result-in-different-behavior.md b/Documentation/compatibility/new-(ambiguous)-dispatcher_invoke-overloads-could-result-in-different-behavior.md
index 362a1b8..de97bd5 100644
--- a/Documentation/compatibility/new-(ambiguous)-dispatcher_invoke-overloads-could-result-in-different-behavior.md
+++ b/Documentation/compatibility/new-(ambiguous)-dispatcher_invoke-overloads-could-result-in-different-behavior.md
@@ -11,13 +11,13 @@ Available
 
 ### Change Description
 
-The .NET Framework 4.5 adds new overloads to Dispatcher.Invoke that include a
-parameter of type @System.Action. When existing code is recompiled, compilers
-may resolve calls to Dispatcher.Invoke methods that have a @System.Delegate
-parameter as calls to Dispatcher.Invoke methods with an @System.Action
-parameter. If a call to a Dispatcher.Invoke overload with a @System.Delegate
+The .NET Framework 4.5 adds new overloads to <xref:System.Windows.Threading.Dispatcher.Invoke%2A?displayProperty=nameWithType> that include a
+parameter of type <xref:System.Action>. When existing code is recompiled, compilers
+may resolve calls to Dispatcher.Invoke methods that have a <xref:System.Delegate>
+parameter as calls to Dispatcher.Invoke methods with an <xref:System.Action>
+parameter. If a call to a Dispatcher.Invoke overload with a  <xref:System.Delegate>
 parameter is resolved as a call to a Dispatcher.Invoke overload with an
-@System.Action parameter, the following differences in behavior may occur:
+<xref:System.Action> parameter, the following differences in behavior may occur:
 
 - If an exception occurs, the <xref:System.Windows.Threading.Dispatcher.UnhandledExceptionFilter> and <xref:System.Windows.Threading.Dispatcher.UnhandledException> events are not raised. Instead, exceptions are handled by the <xref:System.Threading.Tasks.TaskScheduler.UnobservedTaskException?displayProperty=name> event.
 - Calls to some members, such as <xref:System.Windows.Threading.DispatcherOperation.Result>, block until the operation has completed.