DOCS-809: Updates example configuration files for TPC comments (#964)

Import of #26271

**Original PR description:**

<!--
Contributing to Hazelcast and looking for a challenge? Why don't you
check out our open positions?

https://hazelcast.pinpointhq.com/
-->

Updates example configuration files for TPC comments

Checklist:
- [ ] Labels (`Team:`, `Type:`, `Source:`, `Module:`) and Milestone set
- [ ] Add `Add to Release Notes` label if changes should be mentioned in
release notes or `Not Release Notes content` if changes are not relevant
for release notes
- [x] Request reviewers if possible
- [ ] New public APIs have `@Nonnull/@Nullable` annotations
- [ ] New public APIs have `@since` tags in Javadoc
- [ ] Send backports/forwardports if fix needs to be applied to
past/future releases

Imported changes:

- 000adfc DOCS-809: Updates example
configuration files for TPC com...
- 709f825 Update
hazelcast/src/main/resources/hazelcast-full-exampl...

Closes #26271

Co-authored-by: Oliver Howell <oliver.howell@hazelcast.com>
GitOrigin-RevId: fdf36b0aa683917fe0193032cf4eafa9f2b91fcd

hazelcast/src/main/resources/hazelcast-client-full-example.xml

@@ -1025,15 +1025,10 @@
     <!--
     ===== HAZELCAST TPC CONFIGURATION =====
 
-    Configures the client for TPC, which is the next generation Hazelcast that
-    uses thread-per-core model. TPC-aware clients will maintain connections to
-    all cores of all cluster members. The client will route partition-specific
-    invocations to the correct core of the correct member in the best effort
-    basis. Configuration element's name is <tpc>.
-
-    It has the following attributes:
+    Configures the client for thread-per-core (TPC) model using the <tpc> configuration element.
+    TPC will only be used if both client and server have <tpc> enabled.
       - enabled:
-          Enables or disables the TPC-aware mode.
+          Enables or disables TPC-aware mode.
     -->
     <tpc enabled="true"/>
 </hazelcast-client>

hazelcast/src/main/resources/hazelcast-client-full-example.yaml

@@ -974,14 +974,9 @@ hazelcast-client:
   #     Sets the resubmission mode for failing queries. By default, it is set to NEVER.
   sql:
     resubmission-mode: RETRY_SELECTS
-  # Configures the client for TPC, which is the next generation Hazelcast that
-  # uses thread-per-core model. TPC-aware clients will maintain connections to
-  # all cores of all cluster members. The client will route partition-specific
-  # invocations to the correct core of the correct member in the best effort
-  # basis. Configuration element's name is "tpc".
-  #
-  # It has the following sub-elements:
+  # Configures the client for thread-per-core (TPC) model using the <tpc> configuration
+  # element. TPC will only be used if both client and server have <tpc> enabled.
   # * "enabled":
-  #     Enables or disables the TPC-aware mode.
+  #     Enables or disables TPC-aware mode.
   tpc:
     enabled: true

hazelcast/src/main/resources/hazelcast-full-example.xml

@@ -4112,11 +4112,12 @@
     <!--
     ===== HAZELCAST TPC CONFIGURATION =====
 
-    Hazelcast TPC is the next generation of Hazelcast built with thread per core architecture.
-    It's still being developed and everything is subject to change. TPC is disabled by default.
+    Configures the member for thread-per-core (TPC) model using the <tpc> configuration element.
+    TPC will only be used if both client and server have <tpc> enabled.
     -->
+    <!-- Enables or disables TPC-aware mode. -->
     <tpc enabled="true">
-        <!-- Configures the number of eventloops. It's equal to available processor count by default. -->
+        <!-- Configures the number of eventloops. This defaults to available processor count. -->
         <eventloop-count>12</eventloop-count>
     </tpc>
 

hazelcast/src/main/resources/hazelcast-full-example.yaml

@@ -3998,9 +3998,10 @@ hazelcast:
 
   #    ===== HAZELCAST TPC CONFIGURATION =====
   #
-  #    Hazelcast TPC is the next generation of Hazelcast built with thread per core architecture.
-  #    It's still being developed and everything is subject to change. TPC is disabled by default.
+  #    Configures the member for thread-per-core (TPC) model using the <tpc> configuration element.
+  #    TPC will only be used if both client and server have <tpc> enabled.
   tpc:
+    #  Enables or disables TPC-aware mode.
     enabled: true
     # Configures the number of eventloops. It's equal to available processor count by default.
     eventloop-count: 12