Sometimes doesn't work as a non-root, non-lockss user, e.g. when it h…

…as to write a resolv.conf file as lockss; just say "as root" for now.

docs/installing/installer.rst

@@ -4,7 +4,7 @@ Running the LOCKSS Installer
 
 .. note::
 
-   Commands in this section must be run **as a privileged user** who can become ``root`` and ``lockss`` via :program:`sudo` [#fnprivileged]_.
+   Commands in this section are run as ``root``  [#fnroot]_.
 
 The next task is to run the LOCKSS Installer.
 
@@ -32,7 +32,7 @@ After the LOCKSS Installer succeeds, you can also optionally run the K3s Configu
 Invoking the LOCKSS Installer
 -----------------------------
 
-To start the installation process, run this command (relative to the :ref:`lockss-installer-directory`) as a privileged user who can become ``root`` and ``lockss`` via :program:`sudo` [#fnprivileged]_:
+To start the installation process, run this command (relative to the :ref:`lockss-installer-directory`) as ``root``  [#fnroot]_:
 
 .. code-block:: shell
 
@@ -744,9 +744,9 @@ That being said, we still recommend running :program:`k3s check-config` and inte
 
 .. rubric:: Footnotes
 
-.. [#fnprivileged]
+.. [#fnroot]
 
-   See :doc:`/sysadmin/privileged`.
+   See :doc:`/sysadmin/root`.
 
 .. [#fnk3sdatadirnfs]