fix CDATA section (dotnet#2987)

Author: mairaw

xml/System.Diagnostics/DiagnosticListener.xml

@@ -28,8 +28,7 @@
   <Docs>
     <summary>Provides an implementation of the abstract <see cref="T:System.Diagnostics.DiagnosticSource" /> class that represents a named place to which a source sends its information (events).</summary>
     <remarks>
-      <format type="text/markdown">
-  <![CDATA[
+      <format type="text/markdown"><![CDATA[
 
 ## Remarks
 

xml/System.IO/WindowsRuntimeStorageExtensions.xml

@@ -60,17 +60,15 @@ The next example shows the XAML code that is associated with the previous exampl
       <Docs>
         <summary>Creates and returns a reference to a safe file handle for the IStorage instance that is being extended.</summary>
         <remarks>
-          <format type="text/markdown">
-            <![CDATA[
+          <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
 With the Windows 10 Anniversary Update, new interfaces were added to <xref:Windows.Storage.IStorageFolder> and <xref:Windows.Storage.IStorageFile> that allow creating a standard Win32 file handle: `IStorageFolderHandleAccess` and `IStorageItemHandleAccess`. The `CreateSafeFileHandle` group of extension methods take advantage of the `Create` methods of these interfaces.
 
 The key benefit of the API is access to a brokered `SafeFileHandle`. This is critically important if you want to create a <xref:System.IO.FileStream> around an <xref:Windows.Storage.IStorageItem> or <xref:Windows.Storage.IStorageFolder> when you are running in an [AppContainer](https://docs.microsoft.com/en-us/windows/win32/secauthz/appcontainer-isolation). When running in an AppContainer, the application has very limited file access rights. Things like picture and document folders require the native file handle to be proxied via `RuntimeBroker.exe`, as the application process itself doesn't have rights to most files. This API gets the proxied handle. If accessing user data folders or using a file picker, this API should always be used to create <xref:System.IO.FileStream>. Using a path will often throw <xref:System.AccessViolationException> in these cases.
 
-          ]]>
-          </format>
+          ]]></format>
         </remarks>
       </Docs>
     </MemberGroup>

xml/System.Numerics/Complex.xml

@@ -1639,8 +1639,7 @@ The addition of a complex number (a + bi) and a real number (which can be regard
       <Docs>
         <summary>Multiplies a specified number by another specified number, where at least one of them is a complex number, and the other could be a double-precision real number.</summary>
         <remarks>
-          <format type="text/markdown">
-  <![CDATA[
+          <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
@@ -1935,8 +1934,7 @@ ac + bci
       <Docs>
         <summary>Adds a specified number to another specified number, where at least one of them is a complex number, and the other could be a double-precision real number.</summary>
         <remarks>
-          <format type="text/markdown">
-  <![CDATA[
+          <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
@@ -2110,8 +2108,7 @@ Languages that do not support custom operators can call the <xref:System.Numeric
       <Docs>
         <summary>Divides a specified number by another specified number, where at least one of them is a complex number, and the other could be a double-precision real number.</summary>
         <remarks>
-          <format type="text/markdown">
-  <![CDATA[
+          <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
@@ -3041,8 +3038,7 @@ This API is not CLS-compliant.</summary>
       <Docs>
         <summary>Multiplies a specified number by another specified number, where at least one of them is a complex number, and the other could be a double-precision real number.</summary>
         <remarks>
-          <format type="text/markdown">
-  <![CDATA[
+          <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
@@ -3210,8 +3206,7 @@ Languages that do not support custom operators can call the <xref:System.Numeric
       <Docs>
         <summary>Subtracts a specified number from another specified number, where at least one of them is a complex number, and the other could be a double-precision real number.</summary>
         <remarks>
-          <format type="text/markdown">
-  <![CDATA[
+          <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
@@ -3851,8 +3846,7 @@ Languages that do not support custom operators can call the <xref:System.Numeric
       <Docs>
         <summary>Subtracts a specified number from another specified number, where at least one of them is a complex number, and the other could be a double-precision real number, and returns the result.</summary>
         <remarks>
-          <format type="text/markdown">
-  <![CDATA[
+          <format type="text/markdown"><![CDATA[
 
 ## Remarks
 

xml/System.Reflection/MetadataAssemblyResolver.xml

@@ -59,8 +59,7 @@
         <summary>Returns an assembly from a given assembly name.</summary>
         <returns>The assembly for the provided <paramref name="assemblyName" />.</returns>
         <remarks>
-          <format type="text/markdown">
-  <![CDATA[
+          <format type="text/markdown"><![CDATA[
 
 ## Remarks
 

xml/System.Reflection/PathAssemblyResolver.xml

@@ -16,8 +16,7 @@
   <Docs>
     <summary>Represents a metadata assembly resolver that uses paths to every assembly that may be loaded.</summary>
     <remarks>
-      <format type="text/markdown">
-  <![CDATA[
+      <format type="text/markdown"><![CDATA[
 
 ## Remarks
 
@@ -85,7 +84,7 @@ In order for an <xref:System.Reflection.AssemblyName> to match a loaded assembly
 
 ## Remarks
 
-See the <xref:System.Reflection.MetadataAssemblyResolver> remarks for more information.
+For more information, see the <xref:System.Reflection.MetadataAssemblyResolver> remarks.
 
           ]]></format>
         </remarks>