docs/Writerside/topics/mempool.h.md

changeset 1694
a2757c6427cc
parent 1654
5ab3fe0b7859
child 1696
976e629ce990
--- a/docs/Writerside/topics/mempool.h.md	Wed Dec 31 15:25:30 2025 +0100
+++ b/docs/Writerside/topics/mempool.h.md	Wed Dec 31 16:01:08 2025 +0100
@@ -118,7 +118,7 @@
 
 The function `cxMempoolTransfer()` transfers all memory managed and/or registered with the `source` pool to the `dest` pool.
 It also registers its allocator with the `dest` pool and creates a new allocator for the `source` pool.
-That means, that all references to the allocator of the `source` pool remain valid and continue to work with the `dest` pool.
+That means that all references to the allocator of the `source` pool remain valid and continue to work with the `dest` pool.
 The transferred allocator will be destroyed when the `dest` pool gets destroyed.
 
 The function `cxMempoolTransferObject()` transfers a _single_ object managed by the `source` pool to the `dest` pool.
@@ -131,7 +131,7 @@
 - the pools have a different type (simple, advanced, pure)
 - the pools have different base allocators (i.e. `cxDefaultAllocator` changed between creation of the pools)
 
-In case of an error, no memory is transferred and both pools remain unchanged and are in a valid state.
+In case of an error, no memory is transferred, and both pools remain unchanged and are in a valid state.
 
 
 ## Example

mercurial