From a35e8745f354e5569a4416869e755934fff717b4 Mon Sep 17 00:00:00 2001
From: gdamore <gdamore@users.noreply.github.com>
Date: Thu, 9 Oct 2025 02:03:21 +0000
Subject: deploy: bdf85dd692d803b7b2fc793f1c7723f9874bfcdb

---
 ref/tran/inproc.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'ref/tran/inproc.html')

diff --git a/ref/tran/inproc.html b/ref/tran/inproc.html
index a17835a4..180182cf 100644
--- a/ref/tran/inproc.html
+++ b/ref/tran/inproc.html
@@ -266,15 +266,15 @@ They will however be unable to communicate with each other using that URL.</p>
   <span class="mdbook-alerts-icon"></span>
   note
 </p>
-<p>While <em>inproc</em> accepts the option <code>NNG_OPT_RECVMAXSZ</code> for
+<p>While <em>inproc</em> accepts the option <a href="../api/sock.html#NNG_OPT_RECVMAXSZ"><code>NNG_OPT_RECVMAXSZ</code></a> for
 compatibility, the value of the option is ignored with no enforcement.
 As <em>inproc</em> peers are in the same address space, they are implicitly
 trusted, so the protection afforded by <code>NNG_OPT_RECVMAXSZ</code> is unnecessary.</p>
 </div>
 <h2 id="mixing-implementations"><a class="header" href="#mixing-implementations">Mixing Implementations</a></h2>
 <p>When mixing the <em>NNG</em> library with other implementations of these
-protocols in the same process (such as the <em>mangos</em>
-or <em>libnanomsg</em> implementations), it will not be possible to utilize
+protocols in the same process (such as the <a href="https://github.com/nanomsg/mangos">mangos</a>
+or <a href="https://github.com/nanomsg/nanomsg">libnanomsg</a> implementations), it will not be possible to utilize
 the <em>inproc</em> transport to communicate across this boundary.</p>
 <p>This limitation also extends to using different instances of the <em>NNG</em>
 library within the same process.</p>
-- 
cgit v1.2.3-70-g09d2