Revert changes from merge conflict

Author: GumpacG

docs/src/upgrade/release-3.7.x.asciidoc

@@ -158,13 +158,13 @@ opens a session, submits one or more `addV()` operations, commits, and closes th
 The benchmark varies the following parameters:
 
 * *Concurrent clients* (`threads`): The number of threads issuing transactions simultaneously. A value of 1 means
-transactions are executed sequentially by a single client. Higher values simulate multiple application threads or
-service instances issuing transactions concurrently against the same server.
+  transactions are executed sequentially by a single client. Higher values simulate multiple application threads or
+  service instances issuing transactions concurrently against the same server.
 * *Connection pool size* (`pool`): The number of WebSocket connections maintained in the pool when
-`reuseConnectionsForSessions` is enabled. When reuse is disabled, each session creates its own dedicated connection
-and this parameter does not apply (shown as `n/a`).
+  `reuseConnectionsForSessions` is enabled. When reuse is disabled, each session creates its own dedicated connection
+  and this parameter does not apply (shown as `n/a`).
 * *Transaction weight* (`weight`): "light" transactions perform a single `addV()` plus commit. "heavy" transactions
-perform ten `addV()` operations plus commit, simulating a more substantial unit of work per transaction.
+  perform ten `addV()` operations plus commit, simulating a more substantial unit of work per transaction.
 
 Tests were conducted both locally (client and server on the same machine) and remotely (client on the US west coast,
 server on the US east coast) to isolate the effect of network latency on connection setup overhead. Each scenario