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.

diff --git a/man/os-release.xml b/man/os-release.xml
index fbcce9bd5a20041737a50a2eb8d26a945a3256be..f2e0f3ecb7b39dbff2a95f94922d6aad36d8f324 100644 (file)
--- 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

diff --git a/man/systemd-portabled.service.xml b/man/systemd-portabled.service.xml
index 6dacea5e9b78bfc373ac93552e33fecff81c65ff..cb8cea6f6ecf893624056f7e06afd621bc27278d 100644 (file)
--- a/man/systemd-portabled.service.xml
+++ b/man/systemd-portabled.service.xml
@@ -35,7 +35,7 @@
     <para>Most of <command>systemd-portabled</command>'s functionality is accessible through the
     <citerefentry><refentrytitle>portablectl</refentrytitle><manvolnum>1</manvolnum></citerefentry> command.</para>
 
-    <para>See the <ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services Documentation</ulink>
+    <para>See the <ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink> page
     for details about the concepts this service implements.</para>
   </refsect1>
 

diff --git a/man/systemd-sysext.xml b/man/systemd-sysext.xml
index fe980be5e7e494a5f6fc2c27d0320d916970429c..76076931d5fd6a8452701178adb21a8b086dcd09 100644 (file)
--- a/man/systemd-sysext.xml
+++ b/man/systemd-sysext.xml
@@ -112,7 +112,7 @@
     suitable for shipping resources that are processed by subsystems running in earliest boot. Specifically,
     OS extension images are not suitable for shipping system services or
     <citerefentry><refentrytitle>systemd-sysusers</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-    definitions. See the <ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services Documentation</ulink>
+    definitions. See the <ulink url="https://systemd.io/PORTABLE_SERVICES">Portable Services</ulink> page
     for a simple mechanism for shipping system services in disk images, in a similar fashion to OS
     extensions. Note the different isolation on these two mechanisms: while system extension directly extend
     the underlying OS image with additional files that appear in a way very similar to as if they were