CBOR and platform check API updates (#4992)

Author: gewarren

xml/System.Formats.Cbor/CborContentException.xml

@@ -20,7 +20,7 @@
     </Attribute>
   </Attributes>
   <Docs>
-    <summary>To be added.</summary>
+    <summary>The exception that's thrown when CBOR data is invalid.</summary>
     <remarks>To be added.</remarks>
   </Docs>
   <Members>

xml/System.Formats.Cbor/CborReader.xml

@@ -14,7 +14,7 @@
   </Base>
   <Interfaces />
   <Docs>
-    <summary>A stateful, forward-only reader for CBOR encoded data.</summary>
+    <summary>A stateful, forward-only reader for Concise Binary Object Representation (CBOR) encoded data.</summary>
     <remarks>To be added.</remarks>
   </Docs>
   <Members>
@@ -428,7 +428,7 @@ The next value uses a CBOR encoding that is not valid under the current conforma
 
 The next date item does not have the correct semantic tag.</exception>
         <exception cref="T:System.OverflowException">Decoded decimal fraction is either too large or too small for a <see cref="T:System.Decimal" /> value.</exception>
-        <exception cref="T:System.Formats.Cbor.CborContentException">The next value has an invalid CBOR encoding. 
+        <exception cref="T:System.Formats.Cbor.CborContentException">The next value has an invalid CBOR encoding.
 
 -or-
 
@@ -505,7 +505,7 @@ The next value uses a CBOR encoding that is not valid under the current conforma
 
 The data item is an indefinite-length text string.</exception>
         <exception cref="T:System.Formats.Cbor.CborContentException">The next value has an invalid CBOR encoding.
-        
+
 -or-
 
 There was an unexpected end of CBOR encoding data.

xml/System.Formats.Cbor/CborWriter.xml

@@ -14,7 +14,7 @@
   </Base>
   <Interfaces />
   <Docs>
-    <summary>A writer for CBOR encoded data.</summary>
+    <summary>A writer for Concise Binary Object Representation (CBOR) encoded data.</summary>
     <remarks>To be added.</remarks>
   </Docs>
   <Members>
@@ -901,7 +901,7 @@ The written data is not accepted under the current conformance mode.</exception>
       <Docs>
         <summary>Writes the start of a definite or indefinite-length array (major type 4).</summary>
         <param name="definiteLength">The length of the definite-length array, or <see langword="null" /> for an indefinite-length array.</param>
-        
+
         <remarks>
           <format type="text/markdown"><![CDATA[
 
@@ -1022,22 +1022,22 @@ The written data is not accepted under the current conformance mode.</exception>
       <Docs>
         <summary>Writes the start of a definite or indefinite-length map (major type 5).</summary>
         <param name="definiteLength">The length of the definite-length map, or <see langword="null" /> for an indefinite-length map.</param>
-        
+
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
  In canonical conformance modes, the writer will reject indefinite-length writes unless the <xref:System.Formats.Cbor.CborWriter.ConvertIndefiniteLengthEncodings> flag is enabled.
-              
+
 
  Map contents are written as if arrays twice the length of the map's declared size.
                 For instance, a map of size `1` containing a key of type int with a value of type string must be written by successive calls to <xref:System.Formats.Cbor.CborWriter.WriteInt32(System.Int32)> and <xref:System.Formats.Cbor.CborWriter.WriteTextString(System.ReadOnlySpan{System.Char})>.
                 It is up to the caller to keep track of whether the next call is a key or a value.
-              
+
 
  Fundamentally, this is a technical restriction stemming from the fact that CBOR allows keys of any type, for instance a map can contain keys that are maps themselves.
-              
+