Polish README, docs, and Javadocs wording across Chronicle Bytes

[peter-lawrey]

Polishes wording across the README, supporting AsciiDoc files, public API Javadocs, internal comments, and a small number of text strings.

This PR is primarily a documentation and terminology cleanup. It standardises wording such as on-heap, memory-mapped, stop-bit, floating-point, thread-safe, single-threaded, read-only, best-effort, and low-level, and fixes a few minor typos and phrasing issues.

This is an extension to #709

What changed

• Updated README.adoc examples and narrative wording for consistency and readability.

• Polished supporting AsciiDoc docs, including:

  • FAQ.adoc
  • decimal-rendering.adoc
  • project-requirements.adoc

• Cleaned up Javadocs and comments across the Bytes API and mapped-bytes classes.

• Standardised terminology across the codebase, including:

  • on heap → on-heap
  • memory mapped → memory-mapped
  • stop bit → stop-bit
  • floating point → floating-point
  • thread safe / single threaded → thread-safe / single-threaded
  • read only → read-only
  • best effort → best-effort
  • low level → low-level

• Fixed a few small wording/typo issues, including:

  • “set up” wording in the README
  • I.e → I.e.
  • “pre-pended” → “prepended”
  • removal of the duplicated article in the commercial-feature message ("This is a a commercial feature" → "This is a commercial feature").

Impact

• No intended functional or behavioural change.
• Improves consistency between README, docs, and generated Javadocs.
• Makes API wording more precise and easier to scan.
• The only externally visible text change in production code is the corrected commercial-feature message wording.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
2.0% Duplication on New Code

See analysis details on SonarQube Cloud