diff --git a/website/website/pages/api/snarky/Snarky__Libsnark/Print_func/index.html b/website/website/pages/api/snarky/Snarky__Libsnark/Print_func/index.html
index cfd641a281..94354163b2 100644
--- a/website/website/pages/api/snarky/Snarky__Libsnark/Print_func/index.html
+++ b/website/website/pages/api/snarky/Snarky__Libsnark/Print_func/index.html
@@ -1,2 +1,2 @@
 <!DOCTYPE html>
-<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Print_func (snarky.Snarky__Libsnark.Print_func)</title><link rel="stylesheet" href="../../../../../snarky/css/odoc.css"/><meta charset="utf-8"/><meta name="viewport" content="width=device-width,initial-scale=1.0"/><script src="../../../../../snarky/js/highlight.pack.js"></script><script>hljs.initHighlightingOnLoad();</script></head><body><div class="content"><header><nav><a href="../index.html">Up</a> – <a href="../../index.html">snarky</a> &#x00BB; <a href="../index.html">Snarky__Libsnark</a> &#x00BB; Print_func</nav><h1>Module <code>Snarky__Libsnark.Print_func</code></h1></header><dl><dt class="spec value" id="val-print"><a href="#val-print" class="anchor"></a><code><span class="keyword">val</span> print : (string <span>&#45;&gt;</span> string) Core.ref</code></dt><dd><p>Internal: The reference to the user-defined function passed to <a href="../index.html#val-set_printing_fun"><code>set_printing_fun</code></a>. OCaml may relocate the function in memory if it is heap-allocated (e.g. using a closure) during its GC cycle, so we store a reference here and call it from the statically-allocated OCaml function <a href="index.html#val-dispatch"><code>dispatch</code></a> below.</p></dd></dl><dl><dt class="spec value" id="val-puts"><a href="#val-puts" class="anchor"></a><code><span class="keyword">val</span> puts : string <span>&#45;&gt;</span> unit</code></dt><dd><p>A reference to the C <code>puts</code> function.</p><p>The OCaml stdlib functions use thread-unsafe primitives that may cause a crash if calls from multiple threads overlap, so we use this to avoid their thread-unsafe blocking behaviour.</p></dd></dl><dl><dt class="spec value" id="val-dispatch"><a href="#val-dispatch" class="anchor"></a><code><span class="keyword">val</span> dispatch : string <span>&#45;&gt;</span> unit</code></dt><dd><p>The dispatcher passed to the C++ interface in <a href="../index.html#val-set_printing_fun"><code>set_printing_fun</code></a>. We cannot pass the user-provided function directly to the C++ side in case of GC relocation, so this provides a statically-allocated wrapper.</p><p>The call to <a href="index.html#val-puts"><code>puts</code></a> is made from here instead of the C++ side so that OCaml's GC behaviour is mitigated by the the Ctypes API.</p></dd></dl></div></body></html>
\ No newline at end of file
+<html xmlns="http://www.w3.org/1999/xhtml"><head><title>Print_func (snarky.Snarky__Libsnark.Print_func)</title><link rel="stylesheet" href="../../../../../snarky/css/odoc.css"/><meta charset="utf-8"/><meta name="viewport" content="width=device-width,initial-scale=1.0"/><script src="../../../../../snarky/js/highlight.pack.js"></script><script>hljs.initHighlightingOnLoad();</script></head><body><div class="content"><header><nav><a href="../index.html">Up</a> – <a href="../../index.html">snarky</a> &#x00BB; <a href="../index.html">Snarky__Libsnark</a> &#x00BB; Print_func</nav><h1>Module <code>Snarky__Libsnark.Print_func</code></h1></header><dl><dt class="spec value" id="val-print"><a href="#val-print" class="anchor"></a><code><span class="keyword">val</span> print : (string <span>&#45;&gt;</span> string) Core.ref</code></dt><dd><p>Internal: The reference to the user-defined function passed to <a href="../index.html#val-set_printing_fun"><code>set_printing_fun</code></a>. OCaml may relocate the function in memory if it is heap-allocated (e.g. using a closure) during its GC cycle, so we store a reference here and call it from the statically-allocated OCaml function <a href="index.html#val-dispatch"><code>dispatch</code></a> below.</p></dd></dl><dl><dt class="spec value" id="val-puts"><a href="#val-puts" class="anchor"></a><code><span class="keyword">val</span> puts : string <span>&#45;&gt;</span> unit</code></dt><dd><p>A reference to the C <code>puts</code> function.</p><p>The OCaml stdlib functions use thread-unsafe primitives that may cause a crash if calls from multiple threads overlap, so we use this to avoid their thread-unsafe blocking behaviour.</p></dd></dl><dl><dt class="spec value" id="val-dispatch"><a href="#val-dispatch" class="anchor"></a><code><span class="keyword">val</span> dispatch : string <span>&#45;&gt;</span> unit</code></dt><dd><p>The dispatcher passed to the C++ interface in <a href="../index.html#val-set_printing_fun"><code>set_printing_fun</code></a>. We cannot pass the user-provided function directly to the C++ side in case of GC relocation, so this provides a statically-allocated wrapper.</p><p>The call to <a href="index.html#val-puts"><code>puts</code></a> is made from here instead of the C++ side so that OCaml's GC behaviour is mitigated by the Ctypes API.</p></dd></dl></div></body></html>
