diff --git a/docs/guide/connections/pooling.md b/docs/guide/connections/pooling.md
index cd3d02318..6af4fab2e 100644
--- a/docs/guide/connections/pooling.md
+++ b/docs/guide/connections/pooling.md
@@ -108,7 +108,7 @@ Prunes connections from the pool based on how long they have been idle. This is
 Name | Default Value | Description
 prunePeriod | PT5M | period at which pool should be pruned
 idleTime | PT10M | time at which a connection should be considered idle and become a candidate for removal from the pool
-ageTime | PT0 | time at which a connection has aged out and should be removed from the pool. Zero means no age is enforced.
+ageTime | PT0S | time at which a connection has aged out and should be removed from the pool. Zero means no age is enforced.
 prunePriority | -1 | for prioritized connections, these should be pruned using the age time. -1 means no prune priority is enforced.
 
 Only available connections can be pruned from a pool, if a pool is under heavy load the prune strategy will not attempt to alter the pool size. Idle connections will be removed until the minimum pool size is reached. This may produce undesirable results if you're using a connection strategy that will connect to standby servers and you want to reduce the time that those specific connections stay in the pool. If you are using an `ActivePassiveConnectionStrategy` or a `DnsSrvConnectionStrategy` the prunePriority can be used to prioritize the removal of less desirable connections. For instance, by setting prunePriority=1 and ageTime=PT30M with an `ActivePassiveConnectionStrategy`, you can guarantee that connections with a priority >= 1 are removed from the pool after 30 minutes (if load allows). Priority is zero based, so the first connection created by the strategy will have a priority of zero. Setting an ageTime may prune the pool below its minimum size, but it will attempt to grow back to its minimum at the end of the prune process.