fix link text

Author: gewarren

xml/System.Threading.Tasks/Parallel.xml

@@ -52,8 +52,6 @@
 ## Remarks
  The <xref:System.Threading.Tasks.Parallel> class provides library-based data parallel replacements for common operations such as for loops, for each loops, and execution of a set of statements.
 
-
-
 ## Examples
  This example demonstrates several approaches to implementing a parallel loop using multiple language constructs.
 
@@ -64,7 +62,7 @@
     </remarks>
     <threadsafe>All public and protected members of <see cref="T:System.Threading.Tasks.Parallel" /> are thread-safe and may be used concurrently from multiple threads.</threadsafe>
     <related type="Article" href="/dotnet/standard/parallel-programming/data-parallelism-task-parallel-library">Data Parallelism (Task Parallel Library)</related>
-    <related type="ExternalDocumentation" href="https://aka.ms/dotnet-parallel-samples">Samples for Parallel Programming with the .NET Core and .NET Standard</related>
+    <related type="ExternalDocumentation" href="https://aka.ms/dotnet-parallel-samples">Samples for parallel programming with .NET</related>
   </Docs>
   <Members>
     <MemberGroup MemberName="For">

xml/System.Threading.Tasks/Task.xml

@@ -86,7 +86,7 @@
     <related type="Article" href="/dotnet/standard/parallel-programming/task-parallel-library-tpl">Task Parallel Library (TPL)</related>
     <related type="Article" href="/dotnet/standard/asynchronous-programming-patterns/task-based-asynchronous-pattern-tap">Task-based asynchronous pattern (TAP) in .NET: Introduction and overview</related>
     <related type="Article" href="/dotnet/standard/parallel-programming/task-based-asynchronous-programming">Task-based Asynchronous Programming</related>
-    <related type="ExternalDocumentation" href="https://aka.ms/dotnet-parallel-samples">Samples for Parallel Programming with the .NET Core and .NET Standard</related>
+    <related type="ExternalDocumentation" href="https://aka.ms/dotnet-parallel-samples">Samples for parallel programming with .NET</related>
   </Docs>
   <Members>
     <MemberGroup MemberName=".ctor">
@@ -2948,7 +2948,7 @@ Task t Status: RanToCompletion, Result: 42
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Threading.Tasks.Task> class implements the <xref:System.IDisposable> interface because internally it uses resources that also implement <xref:System.IDisposable>. However, particularly if your app targets the .NET Framework 4.5 or later, there is no need to call <xref:System.Threading.Tasks.Task.Dispose%2A> unless performance or scalability testing indicates that, based on your usage patterns, your app's performance would be improved by disposing of tasks. For more information, see [Do I need to dispose of Tasks?](https://devblogs.microsoft.com/pfxteam/do-i-need-to-dispose-of-tasks/) in the Parallel Programming with .NET blog.
+ The <xref:System.Threading.Tasks.Task> class implements the <xref:System.IDisposable> interface because internally it uses resources that also implement <xref:System.IDisposable>. However, particularly if your app targets .NET Framework 4.5 or later, there is no need to call <xref:System.Threading.Tasks.Task.Dispose%2A> unless performance or scalability testing indicates that, based on your usage patterns, your app's performance would be improved by disposing of tasks. For more information, see [Do I need to dispose of Tasks?](https://devblogs.microsoft.com/pfxteam/do-i-need-to-dispose-of-tasks/) in the Parallel Programming with .NET blog.
 
  ]]></format>
         </remarks>
@@ -3000,7 +3000,7 @@ Task t Status: RanToCompletion, Result: 42
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Threading.Tasks.Task> class implements the <xref:System.IDisposable> interface because internally it uses resources that also implement <xref:System.IDisposable>. However, particularly if your app targets the .NET Framework 4.5 or later, there is no need to call <xref:System.Threading.Tasks.Task.Dispose%2A> unless performance or scalability testing indicates that, based on your usage patterns, your app's performance would be improved by disposing of tasks. For more information, see [Do I need to dispose of Tasks?](https://devblogs.microsoft.com/pfxteam/do-i-need-to-dispose-of-tasks/) in the Parallel Programming with .NET blog.
+ The <xref:System.Threading.Tasks.Task> class implements the <xref:System.IDisposable> interface because internally it uses resources that also implement <xref:System.IDisposable>. However, particularly if your app targets .NET Framework 4.5 or later, there is no need to call <xref:System.Threading.Tasks.Task.Dispose%2A> unless performance or scalability testing indicates that, based on your usage patterns, your app's performance would be improved by disposing of tasks. For more information, see [Do I need to dispose of Tasks?](https://devblogs.microsoft.com/pfxteam/do-i-need-to-dispose-of-tasks/) in the Parallel Programming with .NET blog.
 
  ]]></format>
         </remarks>
@@ -3121,7 +3121,7 @@ Task t Status: RanToCompletion, Result: 42
  The most common use of this property is to create and start a new task in a single call to the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method.
 
 > [!NOTE]
->  Starting with the .NET Framework 4.5, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a <xref:System.Threading.Tasks.Task> object with default configuration values.
+>  Starting with .NET Framework 4.5, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a <xref:System.Threading.Tasks.Task> object with default configuration values.
 
  The following example uses the static <xref:System.Threading.Tasks.Task.Factory%2A> property to make two calls to the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method. The first populates an array with the names of files in the user's MyDocuments directory, while the second populates an array with the names of subdirectories of the user's MyDocuments directory. It then calls the <xref:System.Threading.Tasks.TaskFactory.ContinueWhenAll%28System.Threading.Tasks.Task%5B%5D%2CSystem.Action%7BSystem.Threading.Tasks.Task%5B%5D%7D%29?displayProperty=nameWithType> method, which displays information about the number of files and directories in the two arrays after the first two tasks have completed execution.
 

xml/System.Threading.Tasks/TaskCreationOptions.xml

@@ -69,19 +69,19 @@
 ## Remarks
  The <xref:System.Threading.Tasks.TaskCreationOptions> enumeration is used with the following methods:
 
--   The <xref:System.Threading.Tasks.TaskFactory.%23ctor%2A> and <xref:System.Threading.Tasks.TaskFactory%601.%23ctor%2A> constructors with a `creationOptions` parameter, to specify the default options for tasks created by the task factory.
+- The <xref:System.Threading.Tasks.TaskFactory.%23ctor%2A> and <xref:System.Threading.Tasks.TaskFactory%601.%23ctor%2A> constructors with a `creationOptions` parameter, to specify the default options for tasks created by the task factory.
 
--   The <xref:System.Threading.Tasks.Task.%23ctor%2A> and <xref:System.Threading.Tasks.Task%601.%23ctor%2A> constructors with a `creationOptions` parameter, to specify the options used to customize the task's behavior.
+- The <xref:System.Threading.Tasks.Task.%23ctor%2A> and <xref:System.Threading.Tasks.Task%601.%23ctor%2A> constructors with a `creationOptions` parameter, to specify the options used to customize the task's behavior.
 
--   The <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> and <xref:System.Threading.Tasks.TaskFactory%601.StartNew%2A> methods with a `creationOptions` parameter, to specify the options used to customize the task's behavior.
+- The <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> and <xref:System.Threading.Tasks.TaskFactory%601.StartNew%2A> methods with a `creationOptions` parameter, to specify the options used to customize the task's behavior.
 
--   The <xref:System.Threading.Tasks.TaskFactory.FromAsync%2A> and <xref:System.Threading.Tasks.TaskFactory%601.FromAsync%2A> methods with a `creationOptions` parameter, to specify the options used to customize the behavior of the task that executes an end method when a specified <xref:System.IAsyncResult> completes.
+- The <xref:System.Threading.Tasks.TaskFactory.FromAsync%2A> and <xref:System.Threading.Tasks.TaskFactory%601.FromAsync%2A> methods with a `creationOptions` parameter, to specify the options used to customize the behavior of the task that executes an end method when a specified <xref:System.IAsyncResult> completes.
 
--   The <xref:System.Threading.Tasks.TaskCompletionSource%601.%23ctor%2A> constructors with a `creationOptions` parameter, to specify the options used to customize the behavior of the underlying task.
+- The <xref:System.Threading.Tasks.TaskCompletionSource%601.%23ctor%2A> constructors with a `creationOptions` parameter, to specify the options used to customize the behavior of the underlying task.
 
  ]]></format>
     </remarks>
-    <related type="ExternalDocumentation" href="https://aka.ms/dotnet-parallel-samples">Samples for Parallel Programming with the .NET Core and .NET Standard</related>
+    <related type="ExternalDocumentation" href="https://aka.ms/dotnet-parallel-samples">Samples for parallel programming with .NET</related>
   </Docs>
   <Members>
     <Member MemberName="AttachedToParent">