Merge pull request #3321 from dotnet/master

Update live with current master

Author: mairaw

xml/System.Diagnostics.Tracing/EventAttribute.xml

@@ -369,7 +369,7 @@
  You can use standard .NET Framework substitution operators (for example, {1}) in the string). They will be replaced with the string representation of the corresponding part of the event payload.  
   
 ```csharp  
-[Event(1, Message = "Application Falure: {0}", Level = EventLevel.Error, Keywords = Keywords.Diagnostic)]  
+[Event(1, Message = "Application Failure: {0}", Level = EventLevel.Error, Keywords = Keywords.Diagnostic)]  
         public void Failure(string message) { WriteEvent(1, message); }  
   
 ```  

xml/System.Net.Http/HttpRequestMessage.xml

@@ -461,8 +461,29 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the HTTP message version.</summary>
-        <value>The HTTP message version. The default in the .NET Framework and earlier versions of .NET Core is 1.1. In .NET Core 2.1 and later, it is 2.0.</value>
-        <remarks>Starting with .NET  Core 2.1, the default value of the `Version` property changed from 1.1 to 2.0.</remarks>
+        <value>The HTTP message version. The default value is <c>1.1</c>, unless you're targeting .NET Core 2.1 or 2.2. In that case, the default value is <c>2.0</c>.</value>
+        <remarks>
+          <format type="text/markdown"><![CDATA[  
+          
+## Remarks
+
+In .NET Core, the default message version differs based on the version you're using. .NET Core 2.1 changed the default value from `1.1` to `2.0`. In .NET Core 3.0, the default value was reverted back to `1.1`.
+
+### .NET Framework
+
+The default message version is `1.1`.
+
+### .NET Core
+
+The following table lists the default message version based on the version of .NET Core:
+
+| .NET Core version           | HTTP request version |
+| --------------------------- | -------------------- |
+| 2.1<br/>2.2                 | `2.0`                |
+| Any other .NET Core version | `1.1`                |
+
+ ]]></format>
+        </remarks>
       </Docs>
     </Member>
   </Members>

xml/System.Reflection.Metadata.Ecma335/SignatureDecoder`2.xml

@@ -29,8 +29,7 @@
     <typeparam name="TGenericContext">To be added.</typeparam>
     <summary>Decodes signature blobs.</summary>
     <remarks>
-      <format type="text/markdown">
-  <![CDATA[
+      <format type="text/markdown"><![CDATA[
 
 ## Remarks
 

xml/System.Runtime.InteropServices/SEHException.xml

@@ -92,7 +92,7 @@ catch(…)
     </remarks>
     <altmember cref="T:System.Exception" />
     <related type="Article" href="~/docs/standard/exceptions/index.md">Handling and throwing exceptions in .NET</related>
-    <related type="Article" href="https://msdn.microsoft.com/library/610b364b-2761-429d-9c4a-afbc3e66f1b9">How to: Map HRESULTs and Exceptions</related>
+    <related type="Article" href="~/docs/framework/interop/how-to-map-hresults-and-exceptions.md">How to: Map HRESULTs and Exceptions</related>
   </Docs>
   <Members>
     <MemberGroup MemberName=".ctor">

xml/System.Runtime.Serialization.Json/DataContractJsonSerializer.xml

@@ -40,8 +40,10 @@
     <remarks>
       <format type="text/markdown"><![CDATA[  
   
-## Remarks  
- Use the <xref:System.Runtime.Serialization.Json.DataContractJsonSerializer> class to serialize instances of a type into a JSON document and to deserialize a JSON document into an instance of a type. For example, you can create a type named `Person` with properties that contain essential data, such as a name and address. You can then create and manipulate an instance of the `Person` class and write all of its property values in a JSON document for later retrieval. This JSON document can later be deserialized into the `Person` class or another class with an equivalent data contract.  
+## Remarks 
+ For most scenarios that involve serializing to JSON and deserializing from JSON, we recommend the [tools in the System.Text.Json namespace](/dotnet/standard/serialization/system-text-json-overview). 
+ 
+ If your scenario requires the <xref:System.Runtime.Serialization.Json.DataContractJsonSerializer> class, you can use it to serialize instances of a type into a JSON document and to deserialize a JSON document into an instance of a type. For example, you can create a type named `Person` with properties that contain essential data, such as a name and address. You can then create and manipulate an instance of the `Person` class and write all of its property values in a JSON document for later retrieval. This JSON document can later be deserialized into the `Person` class or another class with an equivalent data contract.  
   
  If an error occurs during the serialization of an outgoing reply on the server or the reply operation throws an exception for some other reason, it may not get returned to the client as a fault.  
   

xml/System.Threading/ThreadLocal`1.xml

@@ -524,7 +524,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If this instance was not previously initialized for the current thread, accessing <xref:System.Threading.ThreadLocal%601.Value%2A> will attempt to initialize it. If an initialization function was supplied during the construction, that initialization will happen by invoking the function to retrieve the initial value for <xref:System.Threading.ThreadLocal%601.Value%2A>. Otherwise, the default value of will be used. If an exception is thrown, that exception is cached and thrown on each subsequent access of the property.  
+ If this instance was not previously initialized for the current thread, accessing <xref:System.Threading.ThreadLocal%601.Value%2A> will attempt to initialize it. If an initialization function was supplied during the construction, that initialization will happen by invoking the function to retrieve the initial value for <xref:System.Threading.ThreadLocal%601.Value%2A>. Otherwise, the default value of `T` will be used.  
   
  ]]></format>
         </remarks>

xml/ns-Microsoft.VisualC.StlClr.Generic.xml

@@ -1,6 +1,6 @@
 <Namespace Name="Microsoft.VisualC.StlClr.Generic">
   <Docs>
-    <summary>Contains the classes, interfaces, and iterators that are used to implement the generic interface to the . By using this generic interface, other .NET languages, such as C# and Visual Basic, can call code that is written using STL/CLR.</summary>
+    <summary>Contains the classes, interfaces, and iterators that are used to implement the generic interface to the <see href="https://docs.microsoft.com/cpp/dotnet/stl-clr-library-reference">STL/CLR Library</see>. By using this generic interface, other .NET languages, such as C# and Visual Basic, can call code that is written using STL/CLR.</summary>
     <remarks>To be added.</remarks>
   </Docs>
-</Namespace>
+</Namespace>

xml/ns-System.Text.Json.xml

@@ -1,6 +1,12 @@
 <Namespace Name="System.Text.Json">
   <Docs>
     <summary>The System.Text.Json namespace provides high-performance, low-allocating, and standards-compliant capabilities to process JavaScript Object Notation (JSON), which includes serializing objects to JSON text and deserializing JSON text to objects, with UTF-8 support built-in. It also provides types to read and write JSON text encoded as UTF-8, and to create an in-memory document object model (DOM) for random access of the JSON elements within a structured view of the data.</summary>
-    <remarks>To be added.</remarks>
+    <remarks>
+          <format type="text/markdown"><![CDATA[
+## Remarks
+
+For more information, see the [System.Text.Json overview](/dotnet/standard/serialization/system-text-json-overview).
+          ]]></format>
+      </remarks>
   </Docs>
 </Namespace>