Update v4.5.x docs

static/docs/v4.5.x/_sources/contents/security.rst.txt

@@ -42,10 +42,13 @@ do have to make some configuration changes.
    for the provisioning file system. That change is made like: ``$
    sudo wwctl profile set --root tmpfs default``.
 
-#. That is all you have to do to ensure that Warewulf will probably
+#. That is all you have to do to ensure that Warewulf will
    support SELinux. Once that is done, you just need to enable SELinux
    in ``/etc/sysconfig/selinux`` and install the appropriate profiles
-   into the container.
+   into the container. `An example`_ of such a container is in the
+   warewulf-node-images repository.
+
+.. _An example: https://github.com/warewulf/warewulf-node-images/tree/main/examples/rockylinux-9-selinux
 
 Provisioning Security
 =====================

static/docs/v4.5.x/_sources/contributing/documentation.rst.txt

@@ -9,9 +9,9 @@ reason for this: we want to share the love so nobody feels left out!
 
 You can contribute to the documentation by `raising an issue to
 suggest an improvement
-<https://github.com/warewulf/warewulf-web/issues/new>`_ or by sending a
-`pull request <https://github.com/warewulf/warewulf-web/compare>`_ on
-`our repository <https://github.com/warewulf/warewulf-web>`_.
+<https://github.com/warewulf/warewulf/issues/new>`_ or by sending a
+`pull request <https://github.com/warewulf/warewulf/compare>`_ on
+`our repository <https://github.com/warewulf/warewulf>`_.
 
 The current documentation is generated with `Sphinx
 <https://www.sphinx-doc.org/>`_.

static/docs/v4.5.x/contents/security.html

@@ -152,10 +152,11 @@ <h2>SELinux<a class="headerlink" href="#selinux" title="Link to this heading">
 for SELinux. Instead you must configure Warewulf to use <code class="docutils literal notranslate"><span class="pre">tmpfs</span></code>
 for the provisioning file system. That change is made like: <code class="docutils literal notranslate"><span class="pre">$</span>
 <span class="pre">sudo</span> <span class="pre">wwctl</span> <span class="pre">profile</span> <span class="pre">set</span> <span class="pre">--root</span> <span class="pre">tmpfs</span> <span class="pre">default</span></code>.</p></li>
-<li><p>That is all you have to do to ensure that Warewulf will probably
+<li><p>That is all you have to do to ensure that Warewulf will
 support SELinux. Once that is done, you just need to enable SELinux
 in <code class="docutils literal notranslate"><span class="pre">/etc/sysconfig/selinux</span></code> and install the appropriate profiles
-into the container.</p></li>
+into the container. <a class="reference external" href="https://github.com/warewulf/warewulf-node-images/tree/main/examples/rockylinux-9-selinux">An example</a> of such a container is in the
+warewulf-node-images repository.</p></li>
 </ol>
 </section>
 <section id="provisioning-security">

static/docs/v4.5.x/contributing/documentation.html

@@ -117,10 +117,10 @@ <h1>Documentation<a class="headerlink" href="#documentation" title="Link to this
 documentation dilemma… We tend to focus on the code features and
 functionality before working on documentation. And there is very good
 reason for this: we want to share the love so nobody feels left out!</p>
-<p>You can contribute to the documentation by <a class="reference external" href="https://github.com/warewulf/warewulf-web/issues/new">raising an issue to
+<p>You can contribute to the documentation by <a class="reference external" href="https://github.com/warewulf/warewulf/issues/new">raising an issue to
 suggest an improvement</a> or by sending a
-<a class="reference external" href="https://github.com/warewulf/warewulf-web/compare">pull request</a> on
-<a class="reference external" href="https://github.com/warewulf/warewulf-web">our repository</a>.</p>
+<a class="reference external" href="https://github.com/warewulf/warewulf/compare">pull request</a> on
+<a class="reference external" href="https://github.com/warewulf/warewulf">our repository</a>.</p>
 <p>The current documentation is generated with <a class="reference external" href="https://www.sphinx-doc.org/">Sphinx</a>.</p>
 <p>For more information on using Git and GitHub to create a pull request
 suggesting additions and edits to the docs, see the <a class="reference external" href="contributing">section on