remove extra summary text (dotnet#7123)

Author: gewarren

xml/System.Security.Cryptography/DSASignatureFormat.xml

@@ -45,10 +45,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>
-          <para>The signature format from IEEE P1363, which produces a fixed size signature for a given key.</para>
-          <para>This signature format encodes the <c>(r, s)</c> tuple as the concatenation of the big-endian representation of <c>r</c> and the big-endian representation of <c>s</c>. Each of these values is encoded using the number of bytes required to encode the maximum integer value in the key's mathematical field. For example, an ECDSA signature from the curve <c>secp521r1</c> (a 521-bit field) encodes each of <c>r</c> and <c>s</c> as 66 bytes, and produces a signature output of 132 bytes.</para>
-        </summary>
+        <summary>The signature format from IEEE P1363, which produces a fixed-size signature for a given key.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
@@ -83,10 +80,7 @@ This signature format encodes the `(r, s)` tuple as the concatenation of the
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>
-          <para>The signature format from IETF RFC 3279, which produces a variably-sized signature.</para>
-          <para>This signature format encodes the <c>(r, s)</c> tuple as the DER encoding of <c>SEQUENCE(INTEGER(r), INTEGER(s))</c>. Because the length of a DER INTEGER encoding varies according to the value being encoded, this signature format does not produce a consistent signature length. Signatures in this format always start with <c>0x30</c>, and on average are 7 bytes longer than signatures in the <see cref="F:System.Security.Cryptography.DSASignatureFormat.IeeeP1363FixedFieldConcatenation" /> format.</para>
-        </summary>
+        <summary>The signature format from IETF RFC 3279, which produces a variably-sized signature.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 

xml/System.Security.Cryptography/RSAEncryptionPaddingMode.xml

@@ -81,10 +81,7 @@ The `Oaep` mode corresponds to the RSAES-OEAP encryption scheme described in the
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>
-          <para>Optimal Asymmetric Encryption Padding. It is recommended for new applications.</para>
-          <para>This mode corresponds to the RSAES-OEAP encryption scheme described in the PKCS #1 RSA Encryption Standard. It is recommended for new applications.</para>
-        </summary>
+        <summary>Optimal Asymmetric Encryption Padding. It is recommended for new applications.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
@@ -131,10 +128,7 @@ This mode corresponds to the RSAES-OEAP encryption scheme described in the PKCS
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>
-          <para>PKCS #1 v1.5. It is supported for compatibility with existing applications.</para>
-          <para>This mode corresponds to the RSAES-PKCS1-v1_5 encryption scheme described in the PKCS #1 RSA Encryption Standard. It is supported for compatibility with existing applications.</para>
-        </summary>
+        <summary>PKCS #1 v1.5. It is supported for compatibility with existing applications.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 

xml/System.Security.Cryptography/RSASignaturePaddingMode.xml

@@ -83,10 +83,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>
-          <para>PKCS #1 v1.5.</para>
-          <para>This corresponds to the RSASSA-PKCS1-v1.5 signature scheme of the PKCS #1 RSA Encryption Standard. It is supported for compatibility with existing applications.</para>
-        </summary>
+        <summary>PKCS #1 v1.5.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
@@ -133,10 +130,7 @@ This corresponds to the RSASSA-PKCS1-v1.5 signature scheme of the PKCS #1 RSA En
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>
-          <para>Probabilistic Signature Scheme.</para>
-          <para>This corresponds to the Probabilistic Signature Scheme (RSASSA-PSS) of the PKCS #1 RSA Encryption Standard. It is recommended for new applications.</para>
-        </summary>
+        <summary>Probabilistic Signature Scheme.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[