Address review comments

Use re-use

Revert back to implementor

Use reenable

Author: volosied

api/client/src/main/java/jakarta/websocket/ClientEndpointConfig.java

@@ -59,7 +59,7 @@ public interface ClientEndpointConfig extends EndpointConfig {
      * Return the SSLContext to be used to establish a WebSocket (wss) connection to the server. The SSLContext will
      * have initialised. For insecure WebSocket (ws) connections, this will be {@code null}. If there is an existing
      * connection to the server that uses the same SSLContext and that connection supports multiplexing WebSocket
-     * connections then the container may choose to reuse that connection rather than creating a new one. Containers
+     * connections then the container may choose to re-use that connection rather than creating a new one. Containers
      * may provide container specific configuration to control this behaviour.
      *
      * @return the SSLContext to use to establish a secure connection to the server or {@code null} if an insecure
@@ -235,7 +235,7 @@ public ClientEndpointConfig.Builder decoders(List<Class<? extends Decoder>> deco
         /**
          * Assign the SSLContext to be used when connection to the WebSocket server. If there is an existing connection
          * to the server that uses the same SSLContext and that connection supports multiplexing WebSocket connections
-         * then the container may choose to reuse that connection rather than creating a new one. Containers may
+         * then the container may choose to re-use that connection rather than creating a new one. Containers may
          * provide container specific configuration to control this behaviour.
          *
          * @param sslContext The SSLContext which must be initialised for secure WebSocket (wss) connections or

api/client/src/main/java/jakarta/websocket/DefaultClientEndpointConfig.java

@@ -94,7 +94,7 @@ public List<Class<? extends Decoder>> getDecoders() {
     /**
      * SSLContext to use to secure WebSocket (wss) connections or {@code null} for insecure Websocket (ws) connections.
      * If there is an existing connection to the server that uses the same SSLContext and that connection supports
-     * multiplexing WebSocket connections then the container may choose to reuse that connection rather than creating a
+     * multiplexing WebSocket connections then the container may choose to re-use that connection rather than creating a
      * new one. Containers may provide container specific configuration to control this behaviour.
      *
      * @since WebSocket 2.1

spec/src/main/asciidoc/WebSocket.adoc

@@ -194,7 +194,7 @@ WebSocket implementation must preserve this session data for later
 access until the completion of the *onClose()* method on the endpoint
 instance [WSC 2.1.2-2]. After that time, the WebSocket implementation
 is permitted to discard the developer data. A WebSocket implementation
-that chooses to pool *Session* instances may at that point reuse the
+that chooses to pool *Session* instances may at that point re-use the
 same *Session* instance to represent a new connection provided it issues
 a new unique *Session* id [WSC 2.1.2-3].
 
@@ -686,7 +686,7 @@ establish a secure WebSocket (wss) connection or an insecure WebSocket (ws)
 connection if the provided `SSLContext` is `null`. If there is an existing
 connection to the server that uses the same SSLContext and that connection
 supports multiplexing WebSocket connections then the container may choose to
-reuse that connection rather than creating a new one. Containers may provide
+re-use that connection rather than creating a new one. Containers may provide
 container specific configuration to control this behaviour.
 
 [[client-configuration-modification]]

spec/src/main/theme/jakartaee-theme.yml

@@ -190,7 +190,7 @@ example:
   border_radius: $base_border_radius
   border_width: 0.75
   background_color: ffffff
-  # FIXME re-enable padding bottom once margin collapsing is implemented
+  # FIXME reenable padding bottom once margin collapsing is implemented
   padding: [$vertical_rhythm, $horizontal_rhythm, 0, $horizontal_rhythm]
 image:
   align: left
@@ -202,7 +202,7 @@ sidebar:
   border_color: e1e1e1
   border_radius: $base_border_radius
   border_width: $base_border_width
-  # FIXME re-enable padding bottom once margin collapsing is implemented
+  # FIXME reenable padding bottom once margin collapsing is implemented
   padding: [$vertical_rhythm, $vertical_rhythm * 1.25, 0, $vertical_rhythm * 1.25]
   title:
     align: center

tck/docs/userguide/src/main/asciidoc/book.adoc

@@ -1,4 +1,4 @@
-= TCK User's Guide for Technology Implementers
+= TCK User's Guide for Technology Implementors
 
 include::title.adoc[]
 

tck/docs/userguide/src/main/asciidoc/intro.adoc

@@ -56,7 +56,7 @@ to deploy them across heterogeneous computing environments without
 porting.
 * Compatibility testing allows application users to obtain applications
 from disparate sources and deploy them with confidence.
-* Conformance testing benefits Jakarta platform implementers by ensuring a
+* Conformance testing benefits Jakarta platform implementors by ensuring a
 level playing field for all Jakarta platform ports.
 
 [[GBFPR]][[tck-compatibility-rules]]

tck/docs/userguide/src/main/asciidoc/rules.adoc

@@ -297,8 +297,8 @@ include::rules.inc[]
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
 Jakarta has a well established process for managing challenges to its
-TCKs. Any implementer may submit a challenge to one or more tests in the
-{TechnologyShortName} TCK as it relates to their implementation.  Implementer
+TCKs. Any implementor may submit a challenge to one or more tests in the
+{TechnologyShortName} TCK as it relates to their implementation.  Implementor
 means the entity as a whole in charge of producing the final certified release.
 *Challenges filed should represent the consensus of that entity*.
 
@@ -358,7 +358,7 @@ A consensus that a test produces invalid results will result in the exclusion of
 4.  Rejected Challenges and Remedy. +
 When a`challenge` issue is rejected, it must be closed with a label of `invalid` to indicate it has been rejected.
 There appeal process for challenges rejected on technical terms is outlined in Escalation Appeal.
-If, however, an implementer feels the TCK challenge process was not followed, an appeal issue should be filed with specification project’s TCK issue tracker using the label `challenge-appeal`.
+If, however, an implementor feels the TCK challenge process was not followed, an appeal issue should be filed with specification project’s TCK issue tracker using the label `challenge-appeal`.
 A project lead should escalate the issue with the Jakarta EE Specification Committee via email ([email protected]).
 The committee will evaluate the matter purely in terms of due process.
 If the appeal is accepted, the original TCK challenge issue will be reopened and a label of `appealed-challenge` added, along with a discussion of the appeal decision, and the `challenge-appeal` issue with be closed.

tck/docs/userguide/src/theme/jakartaee-theme.yml

@@ -190,7 +190,7 @@ example:
   border_radius: $base_border_radius
   border_width: 0.75
   background_color: ffffff
-  # FIXME re-enable padding bottom once margin collapsing is implemented
+  # FIXME reenable padding bottom once margin collapsing is implemented
   padding: [$vertical_rhythm, $horizontal_rhythm, 0, $horizontal_rhythm]
 image:
   align: left
@@ -202,7 +202,7 @@ sidebar:
   border_color: e1e1e1
   border_radius: $base_border_radius
   border_width: $base_border_width
-  # FIXME re-enable padding bottom once margin collapsing is implemented
+  # FIXME reenable padding bottom once margin collapsing is implemented
   padding: [$vertical_rhythm, $vertical_rhythm * 1.25, 0, $vertical_rhythm * 1.25]
   title:
     align: center