man: "Documentation" is not part of the title

<ulinks> contents are used to generate a SEE ALSO section at the
bottom of a man page, so we need to include the title, without additional
words, in the content.

1 files changed, 2 insertions, 2 deletions

diff --git a/man/os-release.xml b/man/os-release.xml
index fbcce9bd5a..f2e0f3ecb7 100644
--- a/man/os-release.xml
+++ b/man/os-release.xml
@@ -104,7 +104,7 @@
       <para><filename>/usr/lib/extension-release.d/extension-release.<replaceable>IMAGE</replaceable></filename>
       plays the same role for extension images as <filename>os-release</filename> for the main system, and
       follows the syntax and rules as described in the <ulink
-      url="https://systemd.io/PORTABLE_SERVICES">Portable Services Documentation</ulink>. The purpose of this
+      url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink> page. The purpose of this
       file is to identify the extension and to allow the operating system to verify that the extension image
       matches the base OS. This is typically implemented by checking that the <varname>ID=</varname> options
       match, and either <varname>SYSEXT_LEVEL=</varname> exists and matches too, or if it is not present,
@@ -534,7 +534,7 @@
         <varlistentry>
           <term><varname>PORTABLE_PREFIXES=</varname></term>
           <listitem><para>Takes a space-separated list of one or more valid prefix match strings for the
-          <ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services Documentation</ulink> logic.
+          <ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink> logic.
           This field serves two purposes: it is informational, identifying portable service images as such
           (and thus allowing them to be distinguished from other OS images, such as bootable system images).
           It is also used when a portable service image is attached: the specified or implied portable