From bb67a9767078bd98add53ead0e0e2f1390cfb539 Mon Sep 17 00:00:00 2001
From: gdamore <gdamore@users.noreply.github.com>
Date: Thu, 2 Jan 2025 03:17:48 +0000
Subject: deploy: f7bf24f429cbc488b861ab1b1e4cf1983af56295

---
 ref/api/memory.html | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

(limited to 'ref/api/memory.html')

diff --git a/ref/api/memory.html b/ref/api/memory.html
index 9fa8b5bd..32319564 100644
--- a/ref/api/memory.html
+++ b/ref/api/memory.html
@@ -234,9 +234,7 @@ The memory will be 64-bit aligned.
 Note that the memory may have random data in it, just like with <code>malloc</code>.</p>
 <p>If memory cannot be allocated for any reason, then <code>NULL</code> will be returned.
 Applications that experience this should treat this like <a href="/api/errors.html#NNG_ENOMEM"><code>NNG_ENOMEM</code></a>.</p>
-<p>Memory returned by <code>nng_alloc</code> can be used to hold message buffers, in which
-case it can be directly passed to <a href="/api/sock.html#nng_send"><code>nng_send</code></a> using the flag <code>NNG_FLAG_ALLOC</code>.
-Alternatively, it can be freed when no longer needed using <a href="/api/memory.html#deallocate-memory"><code>nng_free</code></a>.</p>
+<p>Memory returned by <code>nng_alloc</code> should be freed when no longer needed using <a href="/api/memory.html#deallocate-memory"><code>nng_free</code></a>.</p>
 <div class="mdbook-alerts mdbook-alerts-important">
 <p class="mdbook-alerts-title">
   <span class="mdbook-alerts-icon"></span>
-- 
cgit v1.2.3-70-g09d2