From 3db63c95b3b5cc8853fa6a3a19afe34a8ba20dd2 Mon Sep 17 00:00:00 2001
From: gdamore <gdamore@users.noreply.github.com>
Date: Thu, 9 Oct 2025 00:01:13 +0000
Subject: deploy: d006acfdd44af4210e39f571fa32314bcd36bb40

---
 ref/api/thread.html | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

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

diff --git a/ref/api/thread.html b/ref/api/thread.html
index b191bb9a..9c5104e6 100644
--- a/ref/api/thread.html
+++ b/ref/api/thread.html
@@ -279,7 +279,7 @@ Blocking <em>NNG</em> library calls can however be made safely from <em>NNG</em>
 <p>The system may impose limits on the number of threads that can be created.
 Typically applications should not create more than a dozen of these.
 If greater concurrency or scalability is needed, consider instead using
-an asynchronous model using <a href="/api/aio.html#asynchronous-io-handle"><code>nng_aio</code></a> structures.</p>
+an asynchronous model using <a href="../../api/aio.html#asynchronous-io-handle"><code>nng_aio</code></a> structures.</p>
 </div>
 <h2 id="thread-structure"><a class="header" href="#thread-structure">Thread Structure</a></h2>
 <pre><code class="language-c">typedef struct nng_thread nng_thread;
@@ -287,7 +287,7 @@ an asynchronous model using <a href="/api/aio.html#asynchronous-io-handle"><code
 <p>The <a name="a004"></a><code>nng_thread</code> structure represents a thread, which is a single execution context.
 A given thread will have its own stack, and CPU registers. However global state, as well
 as values allocated on the heap, will be shared and accessible to all threads in the system
-(See the <a href="/api/synch.html">Synchronization</a> chapter for functions to help with data sharing between different threads.)</p>
+(See the <a href="../../api/synch.html">Synchronization</a> chapter for functions to help with data sharing between different threads.)</p>
 <p>Multiple threads can be thought of as running concurrently, even though
 they might not actually do so.</p>
 <p>I/O operations that block (i.e. wait for completion) will block the
@@ -314,11 +314,16 @@ It also has the effect of blocking execution in the caller until <em>thr</em> ha
 to provide a name for the thread. This may change how the thread is represented
 in debuggers. Not all platforms support setting the thread name.</p>
 <h2 id="see-also"><a class="header" href="#see-also">See Also</a></h2>
-<p><a href="/api/synch.html">Synchronization</a>,
-<a href="/api/aio.html">Asynchronous Operations</a></p>
+<p><a href="../../api/synch.html">Synchronization</a>,
+<a href="../../api/aio.html">Asynchronous Operations</a></p>
+<!-- NOTE: This assumes that any page referencing this is located
+     in a directory two levels down.  Meaning ./api/somefile.md or
+     similar.  mdbook cannot accommodate links that are called from
+     different levels in the hierarchy. -->
 <!-- Symbol cross reference -->
 <!-- HTTP -->
 <!-- HTTP Status -->
+<!-- TLS -->
 <!-- Macros -->
 <!-- Protocols -->
 <!-- Transports -->
-- 
cgit v1.2.3-70-g09d2