docs/Writerside/topics/allocator.h.md

changeset 1424
563033aa998c
parent 1420
c6f55a2b3495
--- a/docs/Writerside/topics/allocator.h.md	Sat Oct 11 15:42:48 2025 +0200
+++ b/docs/Writerside/topics/allocator.h.md	Sun Oct 12 20:21:56 2025 +0200
@@ -1,7 +1,7 @@
 # Allocator
 
 The allocator interface provides a mechanism to implement own custom allocators 
-that can also be used in many other function in UCX.
+that can also be used in many other functions in UCX.
 
 A default allocator implementation using the stdlib functions is
 available via the global symbol `cxStdlibAllocator`,
@@ -11,8 +11,8 @@
 
 ## Default Allocator
 
-The global default allocator which is used by UCX,
-when no specific allocator is specified,
+The global default allocator which is used by UCX
+when no specific allocator is specified
 can be configured via the `cxDefaultAllocator`.
 It is by default set to the `cxStdlibAllocator`.
 
@@ -156,7 +156,7 @@
 The only difference is that you can pass additional custom `data` to an advanced destructor function.
 
 Destructor functions play a vital role in deep deallocations.
-Another scenarios, besides destroying elements in a collection, are the deallocation of objects
+Another scenario, besides destroying elements in a collection, is the deallocation of objects
 stored in a [memory pool](mempool.h.md) or deallocations of deeply nested [JSON](json.h.md) objects.
 
 > Destructor functions are not to be confused with `free()`-like functions.

mercurial