Updated docs

docs/manual/_sources/brandolinis.rst.txt

@@ -1079,7 +1079,7 @@ Purpose & Scope
 
 This section provides a concrete example, which future evaluations can use as a template. Its purpose is not to be the last word on this particular subject, but to be an example of how the ideas in this chapter can be applied, and to make the next such examination easier.
 
-The subject of this case study is **Prns**\ , a project published at the repository ``github.com/KenAKAFrosty/Prns``\ , presented as a "ground-up implementation of Reticulum, written in Rust", marketed as faster, safer, and more strictly tested than the reference, and widely promoted with the claim of "up to 89× the throughput" of the reference implementation. The record described below is the project's own, and sourced from its GitHub repository, analyzed locally.
+The subject of this case study is **Prns**, a project published at the repository ``github.com/KenAKAFrosty/Prns``, presented as a "ground-up implementation of Reticulum, written in Rust", marketed as faster, safer, and more strictly tested than the reference, widely promoted with the claim of "up to 89× the throughput" of the reference implementation, and an "author" actively engaged in the tactics described in :ref:`A Movement Of A Dozen<brandolinis-recycled-wine>` on online platforms. The record described below is the project's own, and sourced from its GitHub repository, analyzed locally.
 
 .. _brandolinis-project-in-brief:
 

docs/manual/brandolinis.html

@@ -1047,7 +1047,7 @@ defended.</p></li>
 <section id="purpose-scope">
 <span id="brandolinis-purpose-and-scope"></span><h3>Purpose &amp; Scope<a class="headerlink" href="#purpose-scope" title="Link to this heading">¶</a></h3>
 <p>This section provides a concrete example, which future evaluations can use as a template. Its purpose is not to be the last word on this particular subject, but to be an example of how the ideas in this chapter can be applied, and to make the next such examination easier.</p>
-<p>The subject of this case study is <strong>Prns</strong>, a project published at the repository <code class="docutils literal notranslate"><span class="pre">github.com/KenAKAFrosty/Prns</span></code>, presented as a “ground-up implementation of Reticulum, written in Rust”, marketed as faster, safer, and more strictly tested than the reference, and widely promoted with the claim of “up to 89× the throughput” of the reference implementation. The record described below is the project’s own, and sourced from its GitHub repository, analyzed locally.</p>
+<p>The subject of this case study is <strong>Prns</strong>, a project published at the repository <code class="docutils literal notranslate"><span class="pre">github.com/KenAKAFrosty/Prns</span></code>, presented as a “ground-up implementation of Reticulum, written in Rust”, marketed as faster, safer, and more strictly tested than the reference, widely promoted with the claim of “up to 89× the throughput” of the reference implementation, and an “author” actively engaged in the tactics described in <a class="reference internal" href="#brandolinis-recycled-wine"><span class="std std-ref">A Movement Of A Dozen</span></a> on online platforms. The record described below is the project’s own, and sourced from its GitHub repository, analyzed locally.</p>
 </section>
 <section id="the-project-in-brief">
 <span id="brandolinis-project-in-brief"></span><h3>The Project In Brief<a class="headerlink" href="#the-project-in-brief" title="Link to this heading">¶</a></h3>

docs/markdown/brandolinis.md

@@ -917,7 +917,7 @@ They are valuable, free, and very hard to shut down. The response is not to beco
 
 This section provides a concrete example, which future evaluations can use as a template. Its purpose is not to be the last word on this particular subject, but to be an example of how the ideas in this chapter can be applied, and to make the next such examination easier.
 
-The subject of this case study is **Prns**, a project published at the repository `github.com/KenAKAFrosty/Prns`, presented as a “ground-up implementation of Reticulum, written in Rust”, marketed as faster, safer, and more strictly tested than the reference, and widely promoted with the claim of “up to 89× the throughput” of the reference implementation. The record described below is the project’s own, and sourced from its GitHub repository, analyzed locally.
+The subject of this case study is **Prns**, a project published at the repository `github.com/KenAKAFrosty/Prns`, presented as a “ground-up implementation of Reticulum, written in Rust”, marketed as faster, safer, and more strictly tested than the reference, widely promoted with the claim of “up to 89× the throughput” of the reference implementation, and an “author” actively engaged in the tactics described in [A Movement Of A Dozen](#brandolinis-recycled-wine) on online platforms. The record described below is the project’s own, and sourced from its GitHub repository, analyzed locally.
 
 ### The Project In Brief