Update live with current master (dotnet#1895)

* Update extensibility.md

* reviewed topic

fixed typo

changed description

* Responding to PR feedback

* Migrated VB6 lifetime support document

* Added metadata

* Addressed comments.

* Update unit-testing-with-dotnet-test.md

[TestClass] attribute does not exist in xunit framework

* fixing what's new title on the breadcrumb (dotnet#1864)

* restoring well formatted sections in what's new (dotnet#1868)

* restoring well formatted sections

* fixed more links

* react to feedback

* a few more fixes

* Remove rhel minor versions (dotnet#1863)

RHEL minor versions are binary compatible. The rhel major should be used for publishing.

* Add redirects for base-types, garbage-collection and thread-safe. (dotnet#1869)

* Update 301 links (dotnet#1825)

* Initial commit

* Updates

* React to feedback

* React to feedback

* React to feedback

* Revert docset_name

* Revert package links

* React to feedback

* docs update to dotnet/docs

* React to feedback

* exception docs migration and standard toc (dotnet#1866)

* cleanup migration (dotnet#1872)

* Base-types folder migration cleanup (dotnet#1867)

* base-types folder migration cleanup

* .net framework to .net

* take care of nit :)

* A minor change to the output comments in Example-1 of C# Properties guide (dotnet#1873)

* a minor update to the output comments

Changed the output from John Doe --> Wayne Withow

* updated the output,firstname and lastname in Example-1 of C# Properties guide

As per the chanages proposed by @guardrex , 
I have updated the code on line 21 in the main method from--  new Person("Wayne", "Withrow") --> new Person("Isabelle", "Butts") 
and updated the output comment from  Wayne Withrow --> Isabelle Butts

* fixed broken links to visualstudio/data-tools (dotnet#1816)

* fixed broken links

fixed broken links to visualstudio/data-tools topics

* removed en-us from links

* Initial commit (dotnet#1874)

* Migration update: datetime group (dotnet#1870)

* Initial commit

* React to feedback

* React to feedback

* Update vb6-support.md

* Added missing language IDs to C# code snippets. (dotnet#1801)

* Added missing language IDs to C# code snippets.

* Corrected Anchor tags per review comments.

* Added closing tags for all anchors in the topic.

* Update vb6-support.md

* fixed `dotnet sln add` blobs (dotnet#1834)

* fixed blobs in readme

Under bash 4.3.42(1) `dotnet sln add` fails when the wildcard blob does not include a file extension qualifier (e.g., .csproj)

`dotnet sln <FILE.sln> add **/*`

The CLI terminates when it comes across a sub directory that does not contain a project file. E.g., wwwroot/.
Adding a qualifier to the blob, (`.{csproj,fsproj}) seems to be the correct way to use blobs with `dotnet sln add`.

This does not apply to `dotnet sln remove` which can use unqualified wildcard blobs.

* Update dotnet-sln.md

change ms.date to now
replace specific globs with place holders in synopsis
removed 'add a new solution to the current directory' this is covered by dotnet-new documentation
provide examples for:
  adding / removing individual solutions
  adding / removing multiple solutions
  adding / remove multiple solutions using globbing patterns

* Update dotnet-sln.md

Remove specific globbing pattern from the remove command and explain that it 'Removes'.
Add globbing pattern place-holders to command descriptions
Fix globbing patterns in the examples

* fix typo

"remove to" should be "remove from"

* Update extensibility.md

* Update index.md

* Two fixes for example WriteEventCore

1) EventProvider.EventData should be EventSource.EventData. EventSource can be omitted, so it is simplified to just EventData. 
2) The (IntPtr) cast is incorrect. The third parameter of WriteEventCore is EventData* and dataDesc is already that type so no cast is needed.

* Metadata updates (dotnet#1871)

* Migrated VB6 lifetime support document

* Added metadata

* Addressed comments.

* Add redirects for base-types, garbage-collection and thread-safe.

* Update metadata for migrated content.

* exception docs migration and standard toc (dotnet#1866)

* cleanup migration (dotnet#1872)

* Base-types folder migration cleanup (dotnet#1867)

* base-types folder migration cleanup

* .net framework to .net

* take care of nit :)

* A minor change to the output comments in Example-1 of C# Properties guide (dotnet#1873)

* a minor update to the output comments

Changed the output from John Doe --> Wayne Withow

* updated the output,firstname and lastname in Example-1 of C# Properties guide

As per the chanages proposed by @guardrex , 
I have updated the code on line 21 in the main method from--  new Person("Wayne", "Withrow") --> new Person("Isabelle", "Butts") 
and updated the output comment from  Wayne Withrow --> Isabelle Butts

* fixed broken links to visualstudio/data-tools (dotnet#1816)

* fixed broken links

fixed broken links to visualstudio/data-tools topics

* removed en-us from links

* Initial commit (dotnet#1874)

* Migration update: datetime group (dotnet#1870)

* Initial commit

* React to feedback

* React to feedback

* Update vb6-support.md

* Added missing language IDs to C# code snippets. (dotnet#1801)

* Added missing language IDs to C# code snippets.

* Corrected Anchor tags per review comments.

* Added closing tags for all anchors in the topic.

* Update vb6-support.md

* fixed `dotnet sln add` blobs (dotnet#1834)

* fixed blobs in readme

Under bash 4.3.42(1) `dotnet sln add` fails when the wildcard blob does not include a file extension qualifier (e.g., .csproj)

`dotnet sln <FILE.sln> add **/*`

The CLI terminates when it comes across a sub directory that does not contain a project file. E.g., wwwroot/.
Adding a qualifier to the blob, (`.{csproj,fsproj}) seems to be the correct way to use blobs with `dotnet sln add`.

This does not apply to `dotnet sln remove` which can use unqualified wildcard blobs.

* Update dotnet-sln.md

change ms.date to now
replace specific globs with place holders in synopsis
removed 'add a new solution to the current directory' this is covered by dotnet-new documentation
provide examples for:
  adding / removing individual solutions
  adding / removing multiple solutions
  adding / remove multiple solutions using globbing patterns

* Update dotnet-sln.md

Remove specific globbing pattern from the remove command and explain that it 'Removes'.
Add globbing pattern place-holders to command descriptions
Fix globbing patterns in the examples

* fix typo

"remove to" should be "remove from"

* Update metadata for migrated content.

* Fixed thread safety for the ValueTask example (dotnet#1883)

* Fixed thread safety for the ValueTask example

The ```cache = true``` line should be after the ```cacheResult = 100``` line, otherwise it is not thread safe.
Also fixed method's name casing.

* Changed call side of LoadCache

* Update index.md

* Instructions on how to download samples (dotnet#1832)

* Initial commit

* Updates

* Initial commit

* Updates

* Minor update

* Update links

* Make Samples and tutorials repo agnostic

* Updates

* Updates

* React to feedback

* Update section title to 'and'

* Update netcore-hosting.md

* Update indexers.md

* Update console-teleprompter.md

* Update console-webapiclient.md

* Update index.md

* React to feedback

* Update extensibility.md

* Restoring PDF functionality.

* Delete redirected files and update redirection.json

* Addressed issue dotnet#1888: bad return value for StreamReader async reads

* Update toc.md (dotnet#1881)

* Restoring PDF functionality. (dotnet#1892)

* Migration: docs/framework/deployment/index updates (dotnet#1884)

* Update index.md

* Update index.md

* Updated title

* Migration: Update docs/framework/install/guide-for-developers (dotnet#1882)

* Update guide-for-developers.md

* Update guide-for-developers.md

* Removed extra space

* Fixed link and list formatting (dotnet#1893)

* Update index.md

* Migration: docs/standard group link updates (dotnet#1879)

* Update application-essentials.md

* Update common-i-o-tasks.md

* Update asynchronous-file-i-o.md

* Update how-to-compress-and-extract-files.md

* Update how-to-copy-directories.md

* Update how-to-enumerate-directories-and-files.md

* Update how-to-open-and-append-to-a-log-file.md

* Update how-to-read-and-write-to-a-newly-created-data-file.md

* Update how-to-read-and-write-to-files-in-isolated-storage.md

* Update how-to-read-characters-from-a-string.md

* Update how-to-read-text-from-a-file.md

* Update how-to-write-characters-to-a-string.md

* Update how-to-write-text-to-a-file.md

* Update isolated-storage.md

* Update memory-mapped-files.md

* Update pipe-operations.md

* Update toc.md

* Update backreference-constructs-in-regular-expressions.md

* Update regular-expression-language-quick-reference.md

* Update regular-expression-language-quick-reference.md

* Update cross-platform-development-with-the-portable-class-library.md

* Update save-time-zones-to-an-embedded-resource.md

* Update use-time-zones-in-arithmetic.md

* Update working-with-calendars.md

* Update working-with-calendars.md

* Update managed-execution-process.md

* Update index.md

* Update toc.md

* Update common-i-o-tasks.md

* Update index.md

* Create substitutions-in-regular-expressions.md

* Update regular-expression-language-quick-reference.md

* Update use-time-zones-in-arithmetic.md

* Update delegates-for-manipulating-arrays-and-lists.md

* Update .openpublishing.redirection.json

* Update regular-expression-language-quick-reference.md

* Update index.md

* moved table to an include file (dotnet#1724)

* moved table to an include file

* addressed feedback

* addressed feedback/removed library

* small fixes

* fixing toc

* more feedback

* respond to feedback.

* update per feedback.

* Fix typo in WebExceptionStatus

Change "piplined" to "pipelined"

* Fix links

Author: BillWagner

xml/System.Diagnostics.Tracing/EventSource.xml

@@ -2477,7 +2477,7 @@ class AnotherEventSource : EventSource {
   
         fixed (char* arg1Ptr = arg1)  
         {  
-            EventData* dataDesc = stackalloc EventProvider.EventData[4];  
+            EventData* dataDesc = stackalloc EventData[4];  
   
             dataDesc[0].DataPointer = (IntPtr)arg1Ptr;  
             dataDesc[0].Size = (arg1.Length + 1) * 2; // Size in bytes, including a null terminator.   
@@ -2488,7 +2488,7 @@ class AnotherEventSource : EventSource {
             dataDesc[3].DataPointer = (IntPtr)(&arg4);  
             dataDesc[3].Size = 4;  
   
-            WriteEventCore(eventId, 4, (IntPtr)dataDesc);  
+            WriteEventCore(eventId, 4, dataDesc);  
         }  
     }  
 }  
@@ -2675,4 +2675,4 @@ public void Info1(string arg1)
       </Docs>
     </MemberGroup>
   </Members>
-</Type>
+</Type>

xml/System.IO/StreamReader.xml

@@ -1230,7 +1230,7 @@
         <param name="index">The position in <c>buffer</c> at which to begin writing.</param>
         <param name="count">The maximum number of characters to read. If the end of the stream is reached before the specified number of characters is written into the buffer, the current method returns.</param>
         <summary>Reads a specified maximum number of characters from the current stream asynchronously and writes the data to a buffer, beginning at the specified index.</summary>
-        <returns>A task that represents the asynchronous read operation. The value of the <paramref name="TResult" /> parameter contains the total number of bytes read into the buffer. The result value can be less than the number of bytes requested if the number of bytes currently available is less than the requested number, or it can be 0 (zero) if the end of the stream has been reached.</returns>
+        <returns>A task that represents the asynchronous read operation. The value of the <paramref name="TResult" /> parameter contains the total number of characters read into the buffer. The result value can be less than the number of characters requested if the number of characters currently available is less than the requested number, or it can be 0 (zero) if the end of the stream has been reached.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1347,7 +1347,7 @@
         <param name="index">The position in <c>buffer</c> at which to begin writing.</param>
         <param name="count">The maximum number of characters to read. If the end of the stream is reached before the specified number of characters is written into the buffer, the method returns.</param>
         <summary>Reads a specified maximum number of characters from the current stream asynchronously and writes the data to a buffer, beginning at the specified index.</summary>
-        <returns>A task that represents the asynchronous read operation. The value of the <paramref name="TResult" /> parameter contains the total number of bytes read into the buffer. The result value can be less than the number of bytes requested if the number of bytes currently available is less than the requested number, or it can be 0 (zero) if the end of the stream has been reached.</returns>
+        <returns>A task that represents the asynchronous read operation. The value of the <paramref name="TResult" /> parameter contains the total number of characters read into the buffer. The result value can be less than the number of characters requested if the number of characters currently available is less than the requested number, or it can be 0 (zero) if the end of the stream has been reached.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

xml/System.Net/WebExceptionStatus.xml

@@ -227,7 +227,7 @@
         <ReturnType>System.Net.WebExceptionStatus</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The request was a piplined request and the connection was closed before the response was received.</summary>
+        <summary>The request was a pipelined request and the connection was closed before the response was received.</summary>
       </Docs>
     </Member>
     <Member MemberName="ProtocolError">
@@ -556,4 +556,4 @@
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>

xml/System/ValueTuple.xml

@@ -37,17 +37,17 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A tuple is a data structure that has a specific number and sequence of elements. An example of a tuple is a data structure with three elements (known as a 3-tuple or triple) that is used to store an identifier such as a person's name in the first element, a year in the second element, and the person's income for that year in the third element.  
+A tuple is a data structure that has a specific number and sequence of elements. An example of a tuple is a data structure with three elements (known as a 3-tuple or triple) that is used to store an identifier such as a person's name in the first element, a year in the second element, and the person's income for that year in the third element.  
   
- Value tuples are tuple types introduced in the [!INCLUDE[net_v463](~/includes/net-v463-md.md)] to provide the runtime implementation of tuples in C# and struct tuples in F#. They differ from the tuple classes, such as  <xref:System.Tuple%601>, <xref:System.Tuple%601>, etc., as follows:  
+Value tuples are tuple types introduced in the [!INCLUDE[net_v463](~/includes/net-v463-md.md)] to provide the runtime implementation of tuples in C# and struct tuples in F#. They differ from the tuple classes, such as  <xref:System.Tuple%601>, <xref:System.Tuple%602>, etc., as follows:  
   
 -   They are structures (value types) rather than classes (reference types).  
   
 -   They are mutable rather than read-only. That is, the value of tuple components can change.  
   
 -   Their data members, such as `Item1`, `Item2`, etc., are fields rather than properties.  
   
- The <xref:System.ValueTuple> structure itself does not represent a value tuple. Instead, it provides static methods for creating instances of value tuple types. It provides helper methods that you can call to instantiate value tuples without having to explicitly specify the type of each value tuple component. By calling its static `Create` methods, you can create value tuples that have from zero to eight components. For value tuples with more than eight components, you must call the <xref:System.ValueTuple%608.%23ctor%2A> constructor.  
+The <xref:System.ValueTuple> structure itself does not represent a value tuple. Instead, it provides static methods for creating instances of value tuple types. It provides helper methods that you can call to instantiate value tuples without having to explicitly specify the type of each value tuple component. By calling its static `Create` methods, you can create value tuples that have from zero to eight components. For value tuples with more than eight components, you must call the <xref:System.ValueTuple%608.%23ctor%2A> constructor.  
   
  ]]></format>
     </remarks>
@@ -753,4 +753,4 @@
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>