Consistency with Jaybird manual: use "pure Java" instead of "pure-java"

src/docs/asciidoc/release_notes.adoc

@@ -624,8 +624,8 @@ This change was also backported to Jaybird 4.0.8.
 
 Jaybird supports server-side batch updates introduced in Firebird 4.0.
 
-This feature is only available on pure-java connections, and only on prepared statements (but not callable statements).
-Support is only available in pure-java, as the bindings for native and embedded use the legacy fbclient API, and batch updates are not (fully) exposed in the legacy fbclient API.
+This feature is only available on pure Java connections, and only on prepared statements (but not callable statements).
+Support is only available in pure Java, as the bindings for native and embedded use the legacy fbclient API, and batch updates are not (fully) exposed in the legacy fbclient API.
 
 Two new properties have been added for this feature:
 
@@ -649,7 +649,7 @@ Too large buffer sizes will use the server-side maximum (256MB as of Firebird 4.
 
 This support comes with a number of limitations:
 
-* Only supported on the pure-java protocol, not on native or embedded.
+* Only supported on the pure Java protocol, not on native or embedded.
 * Only supported on `PreparedStatement`.
 ** The `Statement` batch behaviour is not supported by server-side batch updates, so Jaybird always emulates batch support for `Statement`.
 ** The `CallableStatement` implementation is more complex than prepared statement, so the decision was made not to reimplement this using server-side batch updates.
@@ -682,8 +682,8 @@ So, if the statement inserts, updates or deletes a significant number of rows, t
 
 Jaybird supports server-side scrollable cursors introduced in Firebird 5.0.
 
-This feature is only available on pure-java connections, and only when explicitly enabled with connection property `scrollableCursor`.
-Support is only available in pure-java, as the bindings for native and embedded use the legacy fbclient API, and scrollable cursors are not exposed in the legacy fbclient API.
+This feature is only available on pure Java connections, and only when explicitly enabled with connection property `scrollableCursor`.
+Support is only available in pure Java, as the bindings for native and embedded use the legacy fbclient API, and scrollable cursors are not exposed in the legacy fbclient API.
 
 The connection property `scrollableCursor` has the following values (case-insensitive):
 
@@ -759,7 +759,7 @@ The solution for not closing the cursor on all code paths -- introduced in Jaybi
 +
 This change was contributed by https://github.com/vasiliy-yashkov[Vasiliy Yashkov].
 * Improvement: add `setForceWrite`/`getForceWrite` to `FBManager` to allow disabling force write on database creation (https://github.com/FirebirdSQL/jaybird/issues/671[#671])
-* Improvement: Attempts to connect without username and password with the pure-java protocol will now result in error `isc_login` ("`Your user name and password are not defined. Ask your database administrator to set up a Firebird login.`") instead of `isc_connect_reject` ("`connection rejected by remote interface`") (https://github.com/FirebirdSQL/jaybird/issues/583[#583])
+* Improvement: Attempts to connect without username and password with the pure Java protocol will now result in error `isc_login` ("`Your user name and password are not defined. Ask your database administrator to set up a Firebird login.`") instead of `isc_connect_reject` ("`connection rejected by remote interface`") (https://github.com/FirebirdSQL/jaybird/issues/583[#583])
 * Improvement: Don't send cursor close to server when closing `ResultSet` in response to `Statement` close (https://github.com/FirebirdSQL/jaybird/issues/669[#669])
 +
 This provides a small performance increase in cases where a result set was not already closed (e.g. no explicit `ResultSet.close()` or result set not fully read) before the statement close.
@@ -806,7 +806,7 @@ This feature was also backported to Jaybird 4.0.7.
 * Improvement: Allow statements longer than 64KB with native and embedded connections (https://github.com/FirebirdSQL/jaybird/issues/713[#713])
 +
 This requires Firebird 3.0 or higher server and a Firebird 3.0 or higher fbclient.
-Long statement texts were already supported for pure-java connections.
+Long statement texts were already supported for pure Java connections.
 * Fixed: `DatabaseMetaData.getIdentifierQuoteString()` should return `" "` (space) for connection dialect 1 (https://github.com/FirebirdSQL/jaybird/issues/714[#714])
 * Improvement: A column `JB_GRANTEE_TYPE` was added to `getColumnPrivileges` and `getTablePrivileges` in `DatabaseMetaData`.
 It returns the object type of the grantee (e.g. `USER`, `ROLE`).
@@ -1184,7 +1184,7 @@ This change can have two potentially breaking effects:
 * Setting a string on a `PreparedStatement`, or updatable `ResultSet`, had a weird boundary check that tried to exploit a benign buffer overflow if the value started and/or ended with "```%```", and was one or two bytes too long.
 This odd boundary check has been removed, and will now throw a `DataTruncation` if the byte length is longer than the declared length (in bytes) of the field.
 Previously, in Jaybird 3.0 and 4.0, this had the following effects:
-** For pure-java, this would throw a "`string truncation error`" on execute
+** For pure Java, this would throw a "`string truncation error`" on execute
 ** For native/embedded, it would be silently accepted with truncation of the value (one byte too long), or throw an `IndexOutOfBoundsException` (two bytes too long)
 
 [#breaking-changes-for-jaybird-6]
@@ -1198,7 +1198,7 @@ With Jaybird 6 the following breaking changes will be introduced.
 Jaybird 6 will drop support for Firebird 2.5 (see also https://github.com/FirebirdSQL/jaybird/tree/master/devdoc/jdp/jdp-2021-03-drop-firebird-2-5-support.md[jdp-2021-03: Drop Firebird 2.5 support^]).
 In general, we expect the driver to remain functional, but chances are certain metadata -- e.g. `DatabaseMetaData` -- will break if we use features introduced in newer versions.
 
-Wire protocol versions for Firebird 2.5 and earlier will be disabled by default to disallow connection for the pure-java protocol.
+Wire protocol versions for Firebird 2.5 and earlier will be disabled by default to disallow connection for the pure Java protocol.
 An option is available to re-enable unsupported wire protocol versions.
 
 [#dropping-support-for-java-8-11]