doc

Author: sgreben

README.md

@@ -13,7 +13,7 @@ Goroutine-safe Copy-on-Write with `sync.Pool`. Wraps a `sync.Pool` with referenc
 
 ## Why?
 
-Read-mostly shared resources that need periodic updates present a tradeoff:
+Read-mostly shared resources that need periodic updates present a "synchronization or allocation" tradeoff:
 
 - **In-place update under lock (e.g. `sync.RWMutex`)**: Zero-alloc - but blocks all readers during updates
 - **Pointer swap + Copy-on-Write (e.g. `atomic.Pointer` or `sync.RWMutex`)**: Fast and non-blocking - but forces you to allocate a new object on each update, causing GC pressure