diff --git a/nixos/modules/programs/zsh/oh-my-zsh.xml b/nixos/modules/programs/zsh/oh-my-zsh.xml
index 14a7228ad9b0..9917dd022b9f 100644
--- a/nixos/modules/programs/zsh/oh-my-zsh.xml
+++ b/nixos/modules/programs/zsh/oh-my-zsh.xml
@@ -5,7 +5,7 @@
          xml:id="module-programs-zsh-ohmyzsh">
  <title>Oh my ZSH</title>
  <para>
-  <literal><link xlink:href="https://ohmyz.sh/">oh-my-zsh</link></literal> is a
+  <link xlink:href="https://ohmyz.sh/"><literal>oh-my-zsh</literal></link> is a
   framework to manage your <link xlink:href="https://www.zsh.org/">ZSH</link>
   configuration including completion scripts for several CLI tools or custom
   prompt themes.
@@ -113,7 +113,7 @@
      Completion scripts are supposed to be stored at
      <literal>$out/share/zsh/site-functions</literal>. This directory is part
      of the
-     <literal><link xlink:href="http://zsh.sourceforge.net/Doc/Release/Functions.html">fpath</link></literal>
+     <link xlink:href="http://zsh.sourceforge.net/Doc/Release/Functions.html"><literal>fpath</literal></link>
      and the package should be compatible with pure <literal>ZSH</literal>
      setups. The module will automatically link the contents of
      <literal>site-functions</literal> to completions directory in the proper
diff --git a/nixos/modules/security/acme/doc.xml b/nixos/modules/security/acme/doc.xml
index 4c02eae45f92..0905fefd6232 100644
--- a/nixos/modules/security/acme/doc.xml
+++ b/nixos/modules/security/acme/doc.xml
@@ -22,7 +22,7 @@
 
   <para>
    To use the ACME module, you must accept the provider's terms of service
-   by setting <literal><xref linkend="opt-security.acme.acceptTerms" /></literal>
+   by setting <xref linkend="opt-security.acme.acceptTerms" />
    to <literal>true</literal>. The Let's Encrypt ToS can be found
    <link xlink:href="https://letsencrypt.org/repository/">here</link>.
   </para>
@@ -30,18 +30,18 @@
   <para>
    You must also set an email address to be used when creating accounts with
    Let's Encrypt. You can set this for all certs with
-   <literal><xref linkend="opt-security.acme.defaults.email" /></literal>
+   <xref linkend="opt-security.acme.defaults.email" />
    and/or on a per-cert basis with
-   <literal><xref linkend="opt-security.acme.certs._name_.email" /></literal>.
+   <xref linkend="opt-security.acme.certs._name_.email" />.
    This address is only used for registration and renewal reminders,
    and cannot be used to administer the certificates in any way.
   </para>
 
   <para>
    Alternatively, you can use a different ACME server by changing the
-   <literal><xref linkend="opt-security.acme.defaults.server" /></literal> option
+   <xref linkend="opt-security.acme.defaults.server" /> option
    to a provider of your choosing, or just change the server for one cert with
-   <literal><xref linkend="opt-security.acme.certs._name_.server" /></literal>.
+   <xref linkend="opt-security.acme.certs._name_.server" />.
   </para>
 
   <para>
@@ -280,7 +280,7 @@ systemd.services.dns-rfc2136-conf = {
   <para>
    It is possible to use DNS-01 validation with all certificates,
    including those automatically configured via the Nginx/Apache
-   <literal><link linkend="opt-services.nginx.virtualHosts._name_.enableACME">enableACME</link></literal>
+   <link linkend="opt-services.nginx.virtualHosts._name_.enableACME"><literal>enableACME</literal></link>
    option. This configuration pattern is fully
    supported and part of the module's test suite for Nginx + Apache.
   </para>
diff --git a/nixos/modules/services/misc/weechat.xml b/nixos/modules/services/misc/weechat.xml
index b17f9a871ff9..ceabd67060cb 100644
--- a/nixos/modules/services/misc/weechat.xml
+++ b/nixos/modules/services/misc/weechat.xml
@@ -13,9 +13,9 @@
 
   <para>
    By default, the module creates a
-   <literal><link xlink:href="https://www.freedesktop.org/wiki/Software/systemd/">systemd</link></literal>
+   <link xlink:href="https://www.freedesktop.org/wiki/Software/systemd/"><literal>systemd</literal></link>
    unit which runs the chat client in a detached
-   <literal><link xlink:href="https://www.gnu.org/software/screen/">screen</link></literal>
+   <link xlink:href="https://www.gnu.org/software/screen/"><literal>screen</literal></link>
    session.
   </para>
 
diff --git a/nixos/modules/services/web-apps/matomo-doc.xml b/nixos/modules/services/web-apps/matomo-doc.xml
index 69d1170e4523..78cd6dd4d434 100644
--- a/nixos/modules/services/web-apps/matomo-doc.xml
+++ b/nixos/modules/services/web-apps/matomo-doc.xml
@@ -99,7 +99,7 @@ GRANT ALL PRIVILEGES ON matomo.* TO 'matomo'@'localhost';
   <para>
    You can use other web servers by forwarding calls for
    <filename>index.php</filename> and <filename>piwik.php</filename> to the
-   <literal><link linkend="opt-services.phpfpm.pools._name_.socket">services.phpfpm.pools.&lt;name&gt;.socket</link></literal> fastcgi unix socket. You can use
+   <link linkend="opt-services.phpfpm.pools._name_.socket"><literal>services.phpfpm.pools.&lt;name&gt;.socket</literal></link> fastcgi unix socket. You can use
    the nginx configuration in the module code as a reference to what else
    should be configured.
   </para>
diff --git a/nixos/modules/services/web-apps/nextcloud.xml b/nixos/modules/services/web-apps/nextcloud.xml
index 533f34f7fcce..02d7595ff179 100644
--- a/nixos/modules/services/web-apps/nextcloud.xml
+++ b/nixos/modules/services/web-apps/nextcloud.xml
@@ -19,11 +19,11 @@
 
   <para>
    Nextcloud is a PHP-based application which requires an HTTP server
-   (<literal><link linkend="opt-services.nextcloud.enable">services.nextcloud</link></literal>
+   (<link linkend="opt-services.nextcloud.enable"><literal>services.nextcloud</literal></link>
    optionally supports
-   <literal><link linkend="opt-services.nginx.enable">services.nginx</link></literal>)
+   <link linkend="opt-services.nginx.enable"><literal>services.nginx</literal></link>)
    and a database (it's recommended to use
-   <literal><link linkend="opt-services.postgresql.enable">services.postgresql</link></literal>).
+   <link linkend="opt-services.postgresql.enable"><literal>services.postgresql</literal></link>).
   </para>
 
   <para>
@@ -65,7 +65,7 @@
 
   <para>
    The <literal>hostName</literal> option is used internally to configure an HTTP
-   server using <literal><link xlink:href="https://php-fpm.org/">PHP-FPM</link></literal>
+   server using <link xlink:href="https://php-fpm.org/"><literal>PHP-FPM</literal></link>
    and <literal>nginx</literal>. The <literal>config</literal> attribute set is
    used by the imperative installer and all values are written to an additional file
    to ensure that changes can be applied by changing the module's options.
@@ -73,14 +73,14 @@
 
   <para>
    In case the application serves multiple domains (those are checked with
-   <literal><link xlink:href="http://php.net/manual/en/reserved.variables.server.php">$_SERVER['HTTP_HOST']</link></literal>)
+   <link xlink:href="http://php.net/manual/en/reserved.variables.server.php"><literal>$_SERVER['HTTP_HOST']</literal></link>)
    it's needed to add them to
-   <literal><link linkend="opt-services.nextcloud.config.extraTrustedDomains">services.nextcloud.config.extraTrustedDomains</link></literal>.
+   <link linkend="opt-services.nextcloud.config.extraTrustedDomains"><literal>services.nextcloud.config.extraTrustedDomains</literal></link>.
   </para>
 
   <para>
    Auto updates for Nextcloud apps can be enabled using
-   <literal><link linkend="opt-services.nextcloud.autoUpdateApps.enable">services.nextcloud.autoUpdateApps</link></literal>.
+   <link linkend="opt-services.nextcloud.autoUpdateApps.enable"><literal>services.nextcloud.autoUpdateApps</literal></link>.
 </para>
 
  </section>