fix paramrefs for System.IO

Author: gewarren

xml/System.IO.Compression/ZipFileExtensions.xml

@@ -385,24 +385,24 @@ This method creates the directory specified by `destinationDirectoryName`. The m
           ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentException">
-          <paramref name="destinationArchiveFileName" /> is a zero-length string, contains only whitespace,
+          <paramref name="destinationDirectoryName" /> is a zero-length string, contains only whitespace,
             or contains one or more invalid characters as defined by <see cref="F:System.IO.Path.InvalidPathChars" />.</exception>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="destinationArchiveFileName" /> is <see langword="null" />.</exception>
+          <paramref name="destinationDirectoryName" /> is <see langword="null" />.</exception>
         <exception cref="T:System.IO.PathTooLongException">The specified path, file name, or both exceed the system-defined maximum length. </exception>
         <exception cref="T:System.IO.DirectoryNotFoundException">The specified path is invalid (for example, it is on an unmapped drive).</exception>
         <exception cref="T:System.IO.IOException">The name of a <see cref="T:System.IO.Compression.ZipArchiveEntry" /> is zero-length, contains only whitespace, or contains one or more invalid characters as defined by <see cref="F:System.IO.Path.InvalidPathChars" />.
 
 -or-
 
-Extracting a <see cref="T:System.IO.Compression.ZipArchiveEntry" /> would have resulted in a destination file that is outside <paramref name="destinationArchiveFileName" /> (for example, if the entry name contains parent directory accessors).
+Extracting a <see cref="T:System.IO.Compression.ZipArchiveEntry" /> would have resulted in a destination file that is outside <paramref name="destinationDirectoryName" /> (for example, if the entry name contains parent directory accessors).
 
 -or-
 
 A <see cref="T:System.IO.Compression.ZipArchiveEntry" /> has the same name as an already extracted entry from the same archive.</exception>
         <exception cref="T:System.UnauthorizedAccessException">The caller does not have the required permission.</exception>
         <exception cref="T:System.NotSupportedException">
-          <paramref name="destinationArchiveFileName" /> is in an invalid format. </exception>
+          <paramref name="destinationDirectoryName" /> is in an invalid format.</exception>
         <exception cref="T:System.IO.InvalidDataException">A <see cref="T:System.IO.Compression.ZipArchiveEntry" /> was not found or was corrupt.
 
 -or-

xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml

@@ -1949,7 +1949,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.Security.SecurityException">Sufficient isolated storage permissions have not been granted.</exception>
-        <exception cref="T:System.ArgumentNullException">The   <paramref name="applicationEvidence" /> identity has not been passed in.</exception>
+        <exception cref="T:System.ArgumentNullException">The <paramref name="applicationEvidenceType" /> identity has not been passed in.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="scope" /> is invalid.</exception>
         <exception cref="T:System.IO.IsolatedStorage.IsolatedStorageException">An isolated storage location cannot be initialized.
 
@@ -2804,9 +2804,9 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentException">
-          <paramref name="sourceFileName" /> or <paramref name="destinationFileName" /> is a zero-length string, contains only white space, or contains one or more invalid characters defined by the <see cref="M:System.IO.Path.GetInvalidPathChars" /> method.</exception>
+          <paramref name="sourceDirectoryName" /> or <paramref name="destinationDirectoryName" /> is a zero-length string, contains only white space, or contains one or more invalid characters defined by the <see cref="M:System.IO.Path.GetInvalidPathChars" /> method.</exception>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="sourceFileName" /> or <paramref name="destinationFileName" /> is <see langword="null" />.</exception>
+          <paramref name="sourceDirectoryName" /> or <paramref name="destinationDirectoryName" /> is <see langword="null" />.</exception>
         <exception cref="T:System.InvalidOperationException">The isolated store has been closed.</exception>
         <exception cref="T:System.ObjectDisposedException">The isolated store has been disposed.</exception>
         <exception cref="T:System.IO.DirectoryNotFoundException">

xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml

@@ -480,7 +480,7 @@
         <param name="access">A bitwise combination of the <see cref="T:System.IO.FileAccess" /> values.</param>
         <param name="share">A bitwise combination of the <see cref="T:System.IO.FileShare" /> values.</param>
         <param name="bufferSize">The <see cref="T:System.IO.FileStream" /> buffer size.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.IO.IsolatedStorage.IsolatedStorageFileStream" /> class giving access to the file designated by <paramref name="path" />, in the specified <paramref name="mode" />, with the specified file <paramref name="access" />, using the file sharing mode specified by <paramref name="share" />, with the <paramref name="buffersize" /> specified.</summary>
+        <summary>Initializes a new instance of the <see cref="T:System.IO.IsolatedStorage.IsolatedStorageFileStream" /> class giving access to the file designated by <paramref name="path" />, in the specified <paramref name="mode" />, with the specified file <paramref name="access" />, using the file sharing mode specified by <paramref name="share" />, with the <paramref name="bufferSize" /> specified.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
@@ -640,17 +640,15 @@
         <param name="share">A bitwise combination of the <see cref="T:System.IO.FileShare" /> values.</param>
         <param name="bufferSize">The <see cref="T:System.IO.FileStream" /> buffer size.</param>
         <param name="isf">The <see cref="T:System.IO.IsolatedStorage.IsolatedStorageFile" /> in which to open the <see cref="T:System.IO.IsolatedStorage.IsolatedStorageFileStream" />.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.IO.IsolatedStorage.IsolatedStorageFileStream" /> class giving access to the file designated by <paramref name="path" />, in the specified <paramref name="mode" />, with the specified file <paramref name="access" />, using the file sharing mode specified by <paramref name="share" />, with the <paramref name="buffersize" /> specified, and in the context of the <see cref="T:System.IO.IsolatedStorage.IsolatedStorageFile" /> specified by <paramref name="isf" />.</summary>
+        <summary>Initializes a new instance of the <see cref="T:System.IO.IsolatedStorage.IsolatedStorageFileStream" /> class giving access to the file designated by <paramref name="path" />, in the specified <paramref name="mode" />, with the specified file <paramref name="access" />, using the file sharing mode specified by <paramref name="share" />, with the <paramref name="bufferSize" /> specified, and in the context of the <see cref="T:System.IO.IsolatedStorage.IsolatedStorageFile" /> specified by <paramref name="isf" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
  The `mode` parameter indicates whether a new file should be created or an existing one used. The `access` parameter includes read-only, read/write, and write-only.
 
 > [!CAUTION]
->  When you compile a set of characters with a particular cultural setting and retrieve those same characters with a different cultural setting, the characters might not be interpretable, and can cause an exception to be thrown.
-
-
+> When you compile a set of characters with a particular cultural setting and retrieve those same characters with a different cultural setting, the characters might not be interpretable, and can cause an exception to be thrown.
 
 ## Examples
  The following code example demonstrates the use of this constructor. For the complete context of this example, see the <xref:System.IO.IsolatedStorage.IsolatedStorageFileStream> overview.

xml/System.IO.Packaging/PackUriHelper.xml

@@ -1024,7 +1024,7 @@ This method does not inspect the part contents; it is based solely on the name.
         <param name="sourcePartUri">The URI of the source part, or "/" to designate the <see cref="T:System.IO.Packaging.Package" /> root.</param>
         <param name="targetUri">The relative URI to the target part.</param>
         <summary>Returns a part URI given a source part URI and a URI with a relative path to a target part.</summary>
-        <returns>The URI of the target part resolved between the specified <paramref name="SourcePartUri" /> and the <paramref name="targetUri" /> parameters.</returns>
+        <returns>The URI of the target part resolved between the specified <paramref name="sourcePartUri" /> and the <paramref name="targetUri" /> parameters.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[
 

xml/System.IO.Packaging/PackagePart.xml

@@ -487,9 +487,8 @@
 ## Remarks
  A part-level relationship defines an association between this part and a target part or resource.  A part-level relationship can be one of two forms.
 
--   Between a source <xref:System.IO.Packaging.PackagePart> to a target <xref:System.IO.Packaging.PackagePart> inside the <xref:System.IO.Packaging.Package>.
-
--   Between a source <xref:System.IO.Packaging.PackagePart> to a target resource outside the package.
+- Between a source <xref:System.IO.Packaging.PackagePart> to a target <xref:System.IO.Packaging.PackagePart> inside the <xref:System.IO.Packaging.Package>.
+- Between a source <xref:System.IO.Packaging.PackagePart> to a target resource outside the package.
 
  In a part-relationship the source part is considered the "owner" of the relationship.  When the source part is deleted, all the relationships owned by the part are also deleted.  The process of creating or deleting the relationship does not physically alter the target part or resource in any way.
 
@@ -503,16 +502,16 @@
 
  `relationshipType` must be a URI that is formed according to the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  Different package types can define different part-level relationship types.  The following table shows the part-level `relationshipType` URIs defined for documents that conform to the *Open XML Paper Specification (XPS)*.
 
-|XPS Document Part-Level Relationship|Relationship Type URI|
-|-------------------------------------------|---------------------------|
-|Digital Signature Definitions|`http://schemas.microsoft.com/xps/2005/06/signature-definitions`|
-|DiscardControl|`http://schemas.microsoft.com/xps/2005/06/discard-control`|
-|DocumentStructure|`http://schemas.microsoft.com/xps/2005/06/documentstructure`|
-|PrintTicket|`http://schemas.microsoft.com/xps/2005/06/printticket`|
-|Required Resource|`http://schemas.microsoft.com/xps/2005/06/required-resource`|
-|Restricted Font|`http://schemas.microsoft.com/xps/2005/06/restricted-font`|
-|StartPart|`http://schemas.microsoft.com/xps/2005/06/fixedrepresentation`|
-|StoryFragments|`http://schemas.microsoft.com/xps/2005/06/storyfragments`|
+| XPS Document Part-Level Relationship | Relationship Type URI                                            |
+|--------------------------------------|------------------------------------------------------------------|
+| Digital Signature Definitions        | `http://schemas.microsoft.com/xps/2005/06/signature-definitions` |
+| DiscardControl                       | `http://schemas.microsoft.com/xps/2005/06/discard-control`       |
+| DocumentStructure                    | `http://schemas.microsoft.com/xps/2005/06/documentstructure`     |
+| PrintTicket                          | `http://schemas.microsoft.com/xps/2005/06/printticket`           |
+| Required Resource                    | `http://schemas.microsoft.com/xps/2005/06/required-resource`     |
+| Restricted Font                      | `http://schemas.microsoft.com/xps/2005/06/restricted-font`       |
+| StartPart                            | `http://schemas.microsoft.com/xps/2005/06/fixedrepresentation`   |
+| StoryFragments                       | `http://schemas.microsoft.com/xps/2005/06/storyfragments`        |
 
  For more information about package relationships see section 1.3 of the *Open Packaging Conventions (OPC)* specification available for download at <https://www.ecma-international.org/publications-and-standards/standards/ecma-376/>.
 
@@ -596,9 +595,8 @@
 ## Remarks
  A part-level relationship defines an association between this part and a target part or resource.  A part-level relationship can be one of two forms.
 
--   Between a source <xref:System.IO.Packaging.PackagePart> to a target <xref:System.IO.Packaging.PackagePart> inside the <xref:System.IO.Packaging.Package>.
-
--   Between a source <xref:System.IO.Packaging.PackagePart> to a target resource outside the package.
+- Between a source <xref:System.IO.Packaging.PackagePart> to a target <xref:System.IO.Packaging.PackagePart> inside the <xref:System.IO.Packaging.Package>.
+- Between a source <xref:System.IO.Packaging.PackagePart> to a target resource outside the package.
 
  In a part-relationship the source part is considered the "owner" of the relationship.  When the source part is deleted, all the relationships owned by the part are also deleted.  The process of creating or deleting the relationship does not physically alter the target part or resource in any way.
 
@@ -614,16 +612,16 @@
 
  `relationshipType` must be a URI that is formed according to the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification.  Different package types can define different part-level relationship types.  The following table shows the part-level `relationshipType` URIs defined for documents that conform to the *Open XML Paper Specification (XPS)*.
 
-|XPS Document Part-Level Relationship|Relationship Type URI|
-|-------------------------------------------|---------------------------|
-|Digital Signature Definitions|http://schemas.microsoft.com/xps/2005/06/signature-definitions|
-|DiscardControl|http://schemas.microsoft.com/xps/2005/06/discard-control|
-|DocumentStructure|http://schemas.microsoft.com/xps/2005/06/documentstructure|
-|PrintTicket|http://schemas.microsoft.com/xps/2005/06/printticket|
-|Required Resource|http://schemas.microsoft.com/xps/2005/06/required-resource|
-|Restricted Font|http://schemas.microsoft.com/xps/2005/06/restricted-font|
-|StartPart|http://schemas.microsoft.com/xps/2005/06/fixedrepresentation|
-|StoryFragments|http://schemas.microsoft.com/xps/2005/06/storyfragments|
+| XPS Document Part-Level Relationship | Relationship Type URI                                          |
+|--------------------------------------|----------------------------------------------------------------|
+| Digital Signature Definitions        | http://schemas.microsoft.com/xps/2005/06/signature-definitions |
+| DiscardControl                       | http://schemas.microsoft.com/xps/2005/06/discard-control       |
+| DocumentStructure                    | http://schemas.microsoft.com/xps/2005/06/documentstructure     |
+| PrintTicket                          | http://schemas.microsoft.com/xps/2005/06/printticket           |
+| Required Resource                    | http://schemas.microsoft.com/xps/2005/06/required-resource     |
+| Restricted Font                      | http://schemas.microsoft.com/xps/2005/06/restricted-font       |
+| StartPart                            | http://schemas.microsoft.com/xps/2005/06/fixedrepresentation   |
+| StoryFragments                       | http://schemas.microsoft.com/xps/2005/06/storyfragments        |
 
  For more information about package relationships see section 1.3 of the *Open Packaging Conventions (OPC)* specification available for download at <https://www.ecma-international.org/publications-and-standards/standards/ecma-376/>.
 
@@ -803,7 +801,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- `id` must be a valid XML identifier.  The `id` type is xsd:ID and must follow the naming conventions prescribed in the *XML Schema Part 2: Datatypes* specification (see [https://www.w3.org/TR/xmlschema-2/#ID](https://www.w3.org/TR/xmlschema-2/#ID)).
+ `id` must be a valid XML identifier. The `id` type is xsd:ID and must follow the naming conventions prescribed in the *XML Schema Part 2: Datatypes* specification (see [https://www.w3.org/TR/xmlschema-2/#ID](https://www.w3.org/TR/xmlschema-2/#ID)).
 
  You can use the <xref:System.IO.Packaging.PackagePart.RelationshipExists%2A> method to determine if a relationship with a specified <xref:System.IO.Packaging.PackageRelationship.Id%2A> is owned by this part.
 
@@ -813,8 +811,6 @@
           <paramref name="id" /> is <see langword="null" />.</exception>
         <exception cref="T:System.Xml.XmlException">
           <paramref name="id" /> is not a valid XML identifier.</exception>
-        <exception cref="T:System.ArgumentException">
-          <paramref name="relationshipType" /> is an empty string.</exception>
         <exception cref="T:System.InvalidOperationException">The part has been deleted.
 
  -or-