1 files changed, 5 insertions, 7 deletions
diff --git a/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml b/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml
index 68dc45f3f88..8b01b8f896a 100644
--- a/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml
+++ b/nixos/doc/manual/from_md/administration/service-mgmt.chapter.xml
@@ -109,13 +109,11 @@ systemd.packages = [ pkgs.packagekit ];
       <emphasis>User</emphasis> systemd services on the other hand,
       should be treated differently. Given a package that has a systemd
       unit file at <literal>#pkg-out#/lib/systemd/user/</literal>, using
-      <link xlink:href="options.html#opt-systemd.packages"><literal>systemd.packages</literal></link>
-      will make you able to start the service via
-      <literal>systemctl --user start</literal>, but it won't start
-      automatically on login. However, You can imperatively enable it by
-      adding the package's attribute to
-      <link xlink:href="options.html#opt-systemd.packages"><literal>systemd.packages</literal></link>
-      and then do this (e.g):
+      <xref linkend="opt-systemd.packages" /> will make you able to
+      start the service via <literal>systemctl --user start</literal>,
+      but it won't start automatically on login. However, You can
+      imperatively enable it by adding the package's attribute to
+      <xref linkend="opt-systemd.packages" /> and then do this (e.g):
     </para>
     <programlisting>
 $ mkdir -p ~/.config/systemd/user/default.target.wants