Revised "asynchronous programming with async and await (C#)" page (#4489

) * Minor revision of async in C# * Dance of commas * Added missing the
dotnet · BillWagner · Feb 21, 2018 · Feb 21, 2018 · Feb 21, 2018 · Feb 21, 2018
commit e80cf4f9ea06d2ae17d8c75c089c76ec6dddf03b
diff --git a/docs/csharp/async.md b/docs/csharp/async.md
@@ -265,4 +265,5 @@ A recommended goal is to achieve complete or near-complete [Referential Transpar
 ## Other Resources

 * [Async in-depth](../standard/async-in-depth.md) provides more information about how Tasks work.
+* [Asynchronous programming with async and await (C#)](../csharp/programming-guide/concepts/async/index.md)
 * Lucian Wischik's [Six Essential Tips for Async](https://channel9.msdn.com/Series/Three-Essential-Tips-for-Async) are a wonderful resource for async programming
diff --git a/docs/csharp/programming-guide/concepts/async/index.md b/docs/csharp/programming-guide/concepts/async/index.md
@@ -36,7 +36,7 @@ Asynchrony proves especially valuable for applications that access the UI thread
  The async-based approach adds the equivalent of an automatic transmission to the list of options that you can choose from when designing asynchronous operations. That is, you get all the benefits of traditional asynchronous programming but with much less effort from the developer.  
 
 ##  <a name="BKMK_HowtoWriteanAsyncMethod"></a> Async methods are easier to write  
- The [async](../../../../csharp/language-reference/keywords/async.md) and [await](../../../../csharp/language-reference/keywords/await.md) keywords in C# are the heart of async programming. By using those two keywords, you can use resources in the .NET Framework, .NET Core, or the Windows Runtime to create an asynchronous method almost as easily as you create a synchronous method. Asynchronous methods that you define by using `async` and `await` are referred to as *async methods*.  
+ The [async](../../../../csharp/language-reference/keywords/async.md) and [await](../../../../csharp/language-reference/keywords/await.md) keywords in C# are the heart of async programming. By using those two keywords, you can use resources in the .NET Framework, .NET Core, or the Windows Runtime to create an asynchronous method almost as easily as you create a synchronous method. Asynchronous methods that you define by using the `async` keyword are referred to as *async methods*.  
 
  The following example shows an async method. Almost everything in the code should look completely familiar to you. The comments call out the features that you add to create the asynchrony.  
 
@@ -87,21 +87,21 @@ The following characteristics summarize what makes the previous example an async
 
 -   The return type is one of the following types:  
 
-    -   <xref:System.Threading.Tasks.Task%601> if your method has a return statement in which the operand has type TResult.  
+    -   <xref:System.Threading.Tasks.Task%601> if your method has a return statement in which the operand has type `TResult`.  
 
     -   <xref:System.Threading.Tasks.Task> if your method has no return statement or has a return statement with no operand.  
 
-    -   `Void` if you're writing an async event handler.  
+    -   `void` if you're writing an async event handler.  
 
     -   Any other type that has a `GetAwaiter` method (starting with C# 7).
 
-     For more information, see "Return Types and Parameters" later in this topic.  
+     For more information, see the [Return Types and Parameters](#BKMK_ReturnTypesandParameters) section.  
 
 -   The method usually includes at least one await expression, which marks a point where the method can't continue until the awaited asynchronous operation is complete. In the meantime, the method is suspended, and control returns to the method's caller. The next section of this topic illustrates what happens at the suspension point.  
 
  In async methods, you use the provided keywords and types to indicate what you want to do, and the compiler does the rest, including keeping track of what must happen when control returns to an await point in a suspended method. Some routine processes, such as loops and exception handling, can be difficult to handle in traditional asynchronous code. In an async method, you write these elements much as you would in a synchronous solution, and the problem is solved.  
 
- For more information about asynchrony in previous versions of the .NET Framework, see [TPL and Traditional .NET Framework Asynchronous Programming](http://msdn.microsoft.com/library/e7b31170-a156-433f-9f26-b1fc7cd1776f).  
+ For more information about asynchrony in previous versions of the .NET Framework, see [TPL and Traditional .NET Framework Asynchronous Programming](../../../../standard/parallel-programming/tpl-and-traditional-async-programming.md).  
 
 ##  <a name="BKMK_WhatHappensUnderstandinganAsyncMethod"></a> What happens in an async method  
  The most important thing to understand in asynchronous programming is how the control flow moves from method to method. The following diagram leads you through the process.  
@@ -127,7 +127,7 @@ The following characteristics summarize what makes the previous example an async
      Therefore, `AccessTheWebAsync` uses an await operator to suspend its progress and to yield control to the method that called `AccessTheWebAsync`. `AccessTheWebAsync` returns a `Task<int>` to the caller. The task represents a promise to produce an integer result that's the length of the downloaded string.  
 
     > [!NOTE]
-    >  If `GetStringAsync` (and therefore `getStringTask`) is complete before `AccessTheWebAsync` awaits it, control remains in `AccessTheWebAsync`. The expense of suspending and then returning to `AccessTheWebAsync` would be wasted if the called asynchronous process (`getStringTask`) has already completed and AccessTheWebSync doesn't have to wait for the final result.  
+    >  If `GetStringAsync` (and therefore `getStringTask`) is complete before `AccessTheWebAsync` awaits it, control remains in `AccessTheWebAsync`. The expense of suspending and then returning to `AccessTheWebAsync` would be wasted if the called asynchronous process (`getStringTask`) has already completed and `AccessTheWebSync` doesn't have to wait for the final result.  
 
      Inside the caller (the event handler in this example), the processing pattern continues. The caller might do other work that doesn't depend on the result from `AccessTheWebAsync` before awaiting that result, or the caller might await immediately.   The event handler is waiting for `AccessTheWebAsync`, and `AccessTheWebAsync` is waiting for `GetStringAsync`.  
 
@@ -141,7 +141,7 @@ For more information about control flow, see [Control Flow in Async Programs (C#
 ##  <a name="BKMK_APIAsyncMethods"></a> API async methods  
  You might be wondering where to find methods such as `GetStringAsync` that support async programming. The  .NET Framework 4.5 or higher and .NET Core contain many members that work with `async` and `await`. You can recognize them by the "Async" suffix that’s appended to the member name, and by their return type of <xref:System.Threading.Tasks.Task> or <xref:System.Threading.Tasks.Task%601>. For example, the `System.IO.Stream` class contains methods such as <xref:System.IO.Stream.CopyToAsync%2A>, <xref:System.IO.Stream.ReadAsync%2A>, and <xref:System.IO.Stream.WriteAsync%2A> alongside the synchronous methods <xref:System.IO.Stream.CopyTo%2A>, <xref:System.IO.Stream.Read%2A>, and <xref:System.IO.Stream.Write%2A>.  
 
- The Windows Runtime also contains many methods that you can use with `async` and `await` in Windows apps. For more information and example methods, see [Quickstart: using the await operator for asynchronous programming](/previous-versions/windows/apps/hh452713(v=win.10)), [Asynchronous programming (Windows Store apps)](/previous-versions/windows/apps/hh464924(v=win.10)), and [WhenAny: Bridging between the .NET Framework and the Windows Runtime](https://msdn.microsoft.com/library/jj635140(v=vs.120).aspx).  
+ The Windows Runtime also contains many methods that you can use with `async` and `await` in Windows apps. For more information, see [Threading and async programming](/windows/uwp/threading-async/) for UWP development, and [Asynchronous programming (Windows Store apps)](/previous-versions/windows/apps/hh464924(v=win.10)) and [Quickstart: using the await operator for asynchronous programming](/previous-versions/windows/apps/hh452713(v=win.10)) if you use earlier versions of the Windows Runtime.  
 
 ##  <a name="BKMK_Threads"></a> Threads  
 Async methods are intended to be non-blocking operations. An `await` expression in an async method doesn’t block the current thread while the awaited task is running. Instead, the expression signs up the rest of the method as a continuation and returns control to the caller of the async method.  
@@ -153,7 +153,7 @@ The async-based approach to asynchronous programming is preferable to existing a
 ##  <a name="BKMK_AsyncandAwait"></a> async and await  
  If you specify that a method is an async method by using the [async](../../../../csharp/language-reference/keywords/async.md) modifier, you enable the following two capabilities.  
 
--   The marked async method can use [await](../../../../csharp/language-reference/keywords/await.md) to designate suspension points. The await operator tells the compiler that the async method can't continue past that point until the awaited asynchronous process is complete. In the meantime, control returns to the caller of the async method.  
+-   The marked async method can use [await](../../../../csharp/language-reference/keywords/await.md) to designate suspension points. The `await` operator tells the compiler that the async method can't continue past that point until the awaited asynchronous process is complete. In the meantime, control returns to the caller of the async method.  
 
      The suspension of an async method at an `await` expression doesn't constitute an exit from the method, and `finally` blocks don’t run.  
 
@@ -227,8 +227,7 @@ Asynchronous APIs in Windows Runtime programming have one of the following retur
 -   <xref:Windows.Foundation.IAsyncActionWithProgress%601>  
 
 -   <xref:Windows.Foundation.IAsyncOperationWithProgress%602>  
-
- For more information and an example, see [Quickstart: using the await operator for asynchronous programming](/previous-versions/windows/apps/hh452713(v=win.10)).  
+
 
 ##  <a name="BKMK_NamingConvention"></a> Naming convention  
  By convention, you append "Async" to the names of methods that have an `async` modifier.  
@@ -335,6 +334,8 @@ namespace AsyncFirstExample
 // Length of the downloaded string: 41564.  
 ```  
 
-## See Also  
+## See also  
  [async](../../../../csharp/language-reference/keywords/async.md)  
- [await](../../../../csharp/language-reference/keywords/await.md)
+ [await](../../../../csharp/language-reference/keywords/await.md)  
+ [Asynchronous programming](../../../../csharp/async.md)  
+ [Async overview](../../../../standard/async.md)  
diff --git a/docs/standard/async-in-depth.md b/docs/standard/async-in-depth.md
@@ -149,5 +149,6 @@ Once `await` is encountered, the execution of `CalculateResult()` is yielded to
 ## See also
 
 [Asynchronous programming in C#](~/docs/csharp/async.md)   
+[Asynchronous programming with async and await (C#)](../csharp/programming-guide/concepts/async/index.md)  
 [Async Programming in F#](~/docs/fsharp/tutorials/asynchronous-and-concurrent-programming/async.md)   
 [Asynchronous Programming with Async and Await (Visual Basic)](~/docs/visual-basic/programming-guide/concepts/async/index.md)