Apply suggestions from code review

Co-authored-by: Genevieve Warren <[email protected]>

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.
+> `AssemblyBuilder` APIs require a fully trusted environment with trusted input, similar to other technologies such as compilers. There are no restrictions other than basic validation for generated IL that the `AssemblyBuilder` can contain. That includes validation for member name, count, and associated metadata, such as custom attributes.
 ]]>
       </format>
     </remarks>

xml/System.Reflection.Emit/ILGenerator.xml

@@ -85,13 +85,14 @@
  MSIL is used as input to a just-in-time (JIT) compiler.
 
 > [!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:
+> There are no restrictions, other than basic validation, for ILGenerator APIs that produce 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 be invalid, such as not having balanced push versus pop opcodes, or invalid operands for a given opcode.
+> - IL can contain any code that might, 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.
+> Such code can do whatever it wishes when the method is loaded and executed. To protect against such vulnerabilities, `ILGenerator` requires a fully trusted environment with trusted input.
  ]]></format>
     </remarks>
   </Docs>

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.
+> `PersistedAssemblyBuilder` APIs require a fully trusted environment with trusted input, similar to other technologies such as compilers. There are no restrictions other than basic validation for generated IL that the `AssemblyBuilder` can contain. That includes validation for member name, count, and associated metadata, such as custom attributes.
 ]]></format>
     </remarks>
   </Docs>