Update src/content/docs/hyperdrive/configuration/how-hyperdrive-works.mdx

Author: thomasgauvin

src/content/docs/hyperdrive/configuration/how-hyperdrive-works.mdx

@@ -33,7 +33,7 @@ Hyperdrive automatically manages the connection pool properties for you, includi
 
 ## Pooling mode
 
-The Hyperdrive connection pooler operates in transaction mode, where the client that executes the query communicates through a single connection for the duration of a transaction. When that transaction has completed, the connection is returned to the pool. As a result, a Worker invocation may obtain various database connections over the course of its execution.
+The Hyperdrive connection pooler operates in transaction mode, where the client that executes the query communicates through a single connection for the duration of a transaction. When that transaction has completed, the connection is returned to the pool.
 
 
 Hyperdrive supports [`SET` statements](https://www.postgresql.org/docs/current/sql-set.html) for the duration of a transaction or a query. For instance, if you manually create a transaction with `BEGIN`/`COMMIT`, `SET` statements within the transaction will take effect. Moreover, a query that includes a `SET` command (`SET X; SELECT foo FROM bar;`) will also apply the `SET` command. When a connection is returned to the pool, the connection is `RESET` such that the `SET` commands will not take effect on subsequent commands.