Fix warnings

Author: buyaa-n

xml/System.Reflection.Emit/AssemblyBuilder.xml

@@ -76,9 +76,13 @@
   </Attributes>
   <Docs>
     <summary>Defines and represents a dynamic assembly.</summary>
-    <remarks>For more information about this API, see <see href="/dotnet/fundamentals/runtime-libraries/system-reflection-emit-assemblybuilder">Supplemental API remarks for AssemblyBuilder</see>.
-      <format type="text/markdown">
-<![CDATA[
+    <remarks>
+      <format type="text/markdown"><![CDATA[
+
+## Remarks
+
+For more information about this API, see <see href="/dotnet/fundamentals/runtime-libraries/system-reflection-emit-assemblybuilder">Supplemental API remarks for AssemblyBuilder</see>.
+
 > [!WARNING]
 > `AssemblyBuilder` APIs require a fully trusted environment with trusted input, similarly as other technologies such as compilers. There are no restrictions other than basic validation for generated IL, for member name, count and associated metadata such as custom attributes, that the AssemblyBuilder can contain. For example untrusted input that directly affects the produced IL written to an assembly that later loaded and executed, such input can do whatever it wishes.
 ]]>

xml/System.Reflection.Emit/ILGenerator.xml

@@ -86,12 +86,10 @@
 
 > [!WARNING]
 > There are no restrictions, other than basic validation for ILGenerator APIs that used for producing method IL. If untrusted input is used for producing IL:
-
 > - IL and metadata can contain secrets provided by the consumer.
 > - IL can be invalid such as not having a balanced push vs. pop opcodes, or invalid operands for a given opcode.
 > - Can contain any code that may, for example, deadlock, have infinite stack recursion, or have an infinite loop.
 > - IL can load and execute code on any other reachable assembly.
-
 > Such code can do whatever it wishes when the method is loaded and executed. To restrict such vulnerabilities `ILGenerator` require a fully trusted environment with trusted input.
  ]]></format>
     </remarks>

xml/System.Reflection.Emit/PersistedAssemblyBuilder.xml

@@ -25,13 +25,16 @@
   </Attributes>
   <Docs>
     <summary>Provides an AssemblyBuilder implementation that can persist assembly to a disk or stream.</summary>
-    <remarks>For more information about this API, see <see href="/dotnet/fundamentals/runtime-libraries/system-reflection-emit-persistedassemblybuilder">Persisted dynamic assemblies in .NET</see>.
-      <format type="text/markdown">
-<![CDATA[
+    <remarks>
+      <format type="text/markdown"><![CDATA[
+
+## Remarks
+
+For more information about this API, see <see href="/dotnet/fundamentals/runtime-libraries/system-reflection-emit-persistedassemblybuilder">Persisted dynamic assemblies in .NET</see>.
+
 > [!WARNING]
 > `PersistedAssemblyBuilder` APIs require a fully trusted environment with trusted input, similarly as other technologies such as compilers. There are no restrictions other than basic validation for generated IL, for member name, count and associated metadata such as custom attributes, that the AssemblyBuilder can contain. For example untrusted input that directly affects the produced IL written to an assembly that later loaded and executed, such input can do whatever it wishes.
-]]>
-      </format>
+]]></format>
     </remarks>
   </Docs>
   <Members>