RFR: 8222329: Readable read(CharBuffer) does not specify that 0 is returned when there is no remaining space in buffer [v6]

[Brian Burkhalter]

> Clarify the behavior of `java.lang.Readable` when the specified `java.nio.CharBuffer` parameter is empty but read-only, and when it is full.

Brian Burkhalter has updated the pull request incrementally with one additional commit since the last revision:

  8222329: Remove redundancy of length vs. remaining in CharBuffer::read doc

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/14616/files
  - new: https://git.openjdk.org/jdk/pull/14616/files/94505a45..7281b482

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=14616&range=05
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=14616&range=04-05

  Stats: 4 lines in 1 file changed: 0 ins; 1 del; 3 mod
  Patch: https://git.openjdk.org/jdk/pull/14616.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/14616/head:pull/14616

PR: https://git.openjdk.org/jdk/pull/14616