Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks
See info in area-owners.md if you want to be subscribed.

Docs Build status updates of commit db6c6b8:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

I suggested this note here as so far we've had two or three reports of it breaking folks.

The technical content LGTM, withholding a checkmark to make sure that voice and style get the OK.

It feels a little redundant to me, since that's what the general contract for streams is (though the zero length buffer thing is an inconsistent edge case)... but I agree that it has come up enough that people were clearly depending on CryptoStream behaving this way and might not realize that it was in the minority for having done so.

I wonder whether we might want to word this instead as just documentation behavior eg

### Remarks 
...
When `Stream.Read` or `Stream.ReadAsync` is called with a buffer of length `N`, the operation completes when:

> - At least one byte has been read from the stream, or
> - The underlying stream they wrap returns 0 from a call to read, indicating no more data is available.
> Also, when `Stream.Read` or `Stream.ReadAsync` is called with a buffer of length 0, the operation succeeds once a call with a non-zero buffer would succeed.

This follows the standard contract for streams. 

Previous to .NET 6.0, `Stream.Read` and `Stream.ReadAsync` would not return until `N` bytes had been read from the stream, or the underlying stream returned 0 from a call to read. Code that assumed they would not return until all `N` bytes were read could fail to read all the content. See (this document)[https://docs.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/6.0/partial-byte-reads-in-streams] for more information.

or something like that. Basically, favor the future rather than the past!

How's this? We should add to DeflateStream and GZipStream as well

Docs Build status updates of commit a67645f:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Thanks. Good to merge?

Docs Build status updates of commit 22fb7b5:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit 0411e2d:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

All CLA requirements met.

Docs Build status updates of commit f6adf51:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

Docs Build status updates of commit f6adf51:

✅ Validation status: passed

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel