fix mismatched paramrefs (#11146)

Author: gewarren

xml/System.Numerics/BigInteger.xml

@@ -11708,7 +11708,7 @@ The integer value `33022` can be exported in four different arrays:
         <param name="destination">The span of characters into which this instance will be written.</param>
         <param name="charsWritten">When the method returns, contains the length of the span in number of characters.</param>
         <param name="format">A read-only span of characters that specifies the format for the formatting operation.</param>
-        <param name="provider">An object that supplies culture-specific formatting information about <paramref name="value" />.</param>
+        <param name="provider">An object that supplies culture-specific formatting information.</param>
         <summary>Formats this big integer instance into a span of characters.</summary>
         <returns>
           <see langword="true" /> if the formatting operation succeeds; <see langword="false" /> otherwise.</returns>

xml/System.Numerics/Vector`1.xml

@@ -3383,11 +3383,6 @@ The following code example shows how to define and use a dynamic assembly. The e
 > [!NOTE]
 >  <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> cannot be used to set declarative security attributes. Use one of the overloads of <xref:System.AppDomain.DefineDynamicAssembly%2A> that takes required, optional, and refused permissions.
 
-> [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.
-
-
-
 ## Examples
  The following code sample illustrates the use of `SetCustomAttribute` within <xref:System.Reflection.Emit.AssemblyBuilder>, using a <xref:System.Reflection.Emit.CustomAttributeBuilder>.
 
@@ -3398,7 +3393,7 @@ The following code example shows how to define and use a dynamic assembly. The e
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="con" /> is <see langword="null" />.</exception>
+          <paramref name="customBuilder" /> is <see langword="null" />.</exception>
         <exception cref="T:System.Security.SecurityException">The caller does not have the required permission.</exception>
       </Docs>
     </Member>

xml/System.Reflection.Emit/AssemblyBuilder.xml

@@ -1988,11 +1988,6 @@ The following code example creates a dynamic method that takes two parameters. T
 
  This method does not demand permissions directly, but invoking the dynamic method can result in security demands, depending on the method. For example, no demands are made for anonymously hosted dynamic methods that are created with the `restrictedSkipVisibility` parameter set to `false`. On the other hand, if you create a method with `restrictedSkipVisibility` set to `true` so it can access a hidden member of a target assembly, the method will cause a demand for the permissions of the target assembly plus <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag.
 
-> [!NOTE]
->  Prior to .NET Framework 2.0, this method required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess> flag.
-
-
-
 ## Examples
  The following code example invokes a dynamic method with exact binding, using the US-English culture. This code example is part of a larger example provided for the <xref:System.Reflection.Emit.DynamicMethod> class.
 

xml/System.Reflection.Emit/DynamicILInfo.xml

@@ -3739,7 +3739,7 @@ The following code sample demonstrates the use of the `AssemblyQualifiedName` pr
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="con" /> is <see langword="null" />.</exception>
+          <paramref name="customBuilder" /> is <see langword="null" />.</exception>
       </Docs>
     </Member>
     <Member MemberName="SetCustomAttribute">

xml/System.Reflection.Emit/DynamicMethod.xml

@@ -367,7 +367,7 @@
         <summary>Sets a custom attribute using a custom attribute builder.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="con" /> is <see langword="null" />.</exception>
+          <paramref name="customBuilder" /> is <see langword="null" />.</exception>
         <exception cref="T:System.InvalidOperationException">
           <see cref="M:System.Reflection.Emit.TypeBuilder.CreateType" /> has been called on the enclosing type.</exception>
       </Docs>

xml/System.Reflection.Emit/EnumBuilder.xml

@@ -902,7 +902,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="con" /> is <see langword="null" />.</exception>
+          <paramref name="customBuilder" /> is <see langword="null" />.</exception>
         <exception cref="T:System.InvalidOperationException">The parent type of this field is complete.</exception>
       </Docs>
     </Member>

xml/System.Reflection.Emit/EventBuilder.xml

@@ -1174,7 +1174,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="con" /> is <see langword="null" />. This exception is new in the .NET Framework 4.</exception>
+          <paramref name="con" /> is <see langword="null" />.</exception>
       </Docs>
     </Member>
     <Member MemberName="Emit">
@@ -1302,8 +1302,6 @@
 
  Labels are created using <xref:System.Reflection.Emit.ILGenerator.DefineLabel%2A> and their location within the stream is fixed by using <xref:System.Reflection.Emit.ILGenerator.MarkLabel%2A>. If a single-byte instruction is used, the label can represent a jump of at most 127 bytes along the stream. `opcode` must represent a branch instruction. Because branches are relative instructions, `label` will be replaced with the correct offset to branch during the fixup process.
 
-
-
 ## Examples
  The code sample below illustrates the creation of a dynamic method with a jump table. The jump table is built using an array of <xref:System.Reflection.Emit.Label>.
 
@@ -1313,8 +1311,6 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.ArgumentNullException">
-          <paramref name="con" /> is <see langword="null" />. This exception is new in the .NET Framework 4.</exception>
       </Docs>
     </Member>
     <Member MemberName="Emit">

xml/System.Reflection.Emit/FieldBuilder.xml

@@ -3229,7 +3229,6 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.ArgumentNullException">The <paramref name="name" /> parameter is <see langword="null" />.</exception>
       </Docs>
     </Member>
     <Member MemberName="GetFieldToken">
@@ -5438,13 +5437,8 @@
 ## Remarks
  This method does nothing.
 
-> [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.
-
  ]]></format>
         </remarks>
-        <exception cref="T:System.ArgumentNullException">
-          <paramref name="url" /> is <see langword="null" />.</exception>
       </Docs>
     </Member>
     <Member MemberName="SetUserEntryPoint">