Bug ID: JDK-8235836 Cleanup memory access API javadoc

Versions (Unresolved/Resolved/Fixed)

The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.

Other
repo-panamaFixed

The CSR review outline the following issues in the memory access API javadoc:

* Typo in MemoryLayout "for a finite sequence layout S whose element layout is E and size is L" "L" is not italicized.

* typo in MemoryAddress.equals Returns true if and only if the specified object is also a address, and it is equal to this address.

* If MemoryAddress are equal if their offsets and segments are equal, that should be stated explicitly.

* Is it the case that there is a memory leak one of the threads that has acquired a memory segment dies without freeing it? Better document this condition in MemorySegment::acquire

* MemoryLayout.byteAlignment() should have an @implSpec tag describing its default implementation.

* For MemoryLayout.equals, what aspects are compared? In particular, would a GroupLayout with and without a name be considered equal?