ReadBlockAsync docs unclear on difference to ReadAsync

[ZoeyR]

The docs for ReadBlockAsync are almost identical to the docs for ReadAsync but their behavior is quite different. ReadBlockAsync appears to try and fill the buffer with count characters before returning, only returning early if the stream ended. ReadAsync on the other hand appears to fill a maximum of count characters, but will return early if there is no more data ready for reading.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3988e630-dd5b-611e-7767-4c5aec0622ae
• Version Independent ID: 9169e86f-d936-61f7-243e-a3d2816fb170
• Content: StreamReader.ReadBlockAsync Method (System.IO)
• Content Source: xml/System.IO/StreamReader.xml
• Product: dotnet-api
• GitHub Login: @dotnet-bot
• Microsoft Alias: dotnetcontent

[rpetrusha]

See the comment in #2930. The ReadAsync documentation should be aligned with Read, and the ReadBlockAsync documentation should be aligned with ReadBlock.