Small updates to make it look better

Author: buyaa-n

xml/System.Reflection.Emit/AssemblyBuilder.xml

@@ -84,7 +84,7 @@
 For more information about this API, see [Supplemental API remarks for AssemblyBuilder](/dotnet/fundamentals/runtime-libraries/system-reflection-emit-assemblybuilder).
 
 > [!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.
+> `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.
 ]]>
       </format>
     </remarks>

xml/System.Reflection.Emit/ILGenerator.xml

@@ -90,6 +90,7 @@
 > - 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

@@ -33,7 +33,7 @@
 For more information about this API, see [Persisted dynamic assemblies in .NET](/dotnet/fundamentals/runtime-libraries/system-reflection-emit-persistedassemblybuilder).
 
 > [!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.
+> `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.
 ]]></format>
     </remarks>
   </Docs>