From 2b8d71694ea8755881bdb8d8fe1fdcc9d4055eac Mon Sep 17 00:00:00 2001
From: gdamore <gdamore@users.noreply.github.com>
Date: Wed, 15 Jan 2025 05:56:53 +0000
Subject: deploy: 575148ac9a274d61e45220fda7d8de6a420f4fe4

---
 ref/api/msg.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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

diff --git a/ref/api/msg.html b/ref/api/msg.html
index 4579ef41..f88303ee 100644
--- a/ref/api/msg.html
+++ b/ref/api/msg.html
@@ -416,7 +416,7 @@ except that they operate the message header rather than the message body.</p>
 <pre><code class="language-c">nng_pipe nng_msg_get_pipe(nng_msg *msg);
 void nng_msg_get_pipe(nng_msg *msg, nng_pipe p);
 </code></pre>
-<p>The <a name="a025"></a><code>nng_msg_set_pipe</code> function sets the <a href="/TODO.html">pipe</a> associated with <em>msg</em> to <em>p</em>.
+<p>The <a name="a025"></a><code>nng_msg_set_pipe</code> function sets the <a href="/api/pipe.html">pipe</a> associated with <em>msg</em> to <em>p</em>.
 This is most often useful when used with protocols that support directing
 a message to a specific peer.
 For example the <a href="/proto/pair.html"><em>PAIR</em></a> version 1 protocol can do
-- 
cgit v1.2.3-70-g09d2