docs: normalize uppercasing of titles of network doc

diff --git a/docs/NETWORK_ONLINE.md b/docs/NETWORK_ONLINE.md
index fce4db9c84fb687cf30cc13a47cdc8cf29aee7b8..641c5e9129807bb87eeb32bf1421f426e80b6038 100644 (file)
--- a/docs/NETWORK_ONLINE.md
+++ b/docs/NETWORK_ONLINE.md
@@ -5,7 +5,7 @@ layout: default
 SPDX-License-Identifier: LGPL-2.1-or-later
 ---
 
-# Network configuration synchronization points
+# Network Configuration Synchronization Points
 
 systemd provides three target units related to network configuration:
 

diff --git a/man/systemd.special.xml b/man/systemd.special.xml
index 6616448e90513129e9284e3ce30f37265e251042..1e3e6d8c3e3a624904e542bb387ba78a90a23e52 100644 (file)
--- a/man/systemd.special.xml
+++ b/man/systemd.special.xml
@@ -500,21 +500,15 @@
             sufficiently set up. What precisely this requires is left to
             the implementation of the network managing service.</para>
 
-            <para>Note the distinction between this unit and
-            <filename>network.target</filename>. This unit is an active
-            unit (i.e. pulled in by the consumer rather than the
-            provider of this functionality) and pulls in a service which
-            possibly adds substantial delays to further execution. In
-            contrast, <filename>network.target</filename> is a passive
-            unit (i.e. pulled in by the provider of the functionality,
-            rather than the consumer) that usually does not delay
-            execution much. Usually, <filename>network.target</filename>
-            is part of the boot of most systems, while
-            <filename>network-online.target</filename> is not, except
-            when at least one unit requires it. Also see <ulink
-            url="https://systemd.io/NETWORK_ONLINE">Running
-            Services After the Network is up</ulink> for more
-            information.</para>
+            <para>Note the distinction between this unit and <filename>network.target</filename>. This unit
+            is an active unit (i.e. pulled in by the consumer rather than the provider of this functionality)
+            and pulls in a service which possibly adds substantial delays to further execution. In contrast,
+            <filename>network.target</filename> is a passive unit (i.e. pulled in by the provider of the
+            functionality, rather than the consumer) that usually does not delay execution much. Usually,
+            <filename>network.target</filename> is part of the boot of most systems, while
+            <filename>network-online.target</filename> is not, except when at least one unit requires
+            it. Also see <ulink url="https://systemd.io/NETWORK_ONLINE">Running Services After the Network Is
+            Up</ulink> for more information.</para>
 
             <para>All mount units for remote network file systems automatically pull in this unit, and order
             themselves after it. Note that networking daemons that simply <emphasis>provide</emphasis>
@@ -991,8 +985,8 @@
               will be stopped before the network — to whatever level it might be set up by then — is shut
               down. It is hence useful when writing service files that require network access on shutdown,
               which should order themselves after this target, but not pull it in. Also see <ulink
-              url="https://systemd.io/NETWORK_ONLINE">Running Services After
-              the Network is up</ulink> for more information.</para></listitem>
+              url="https://systemd.io/NETWORK_ONLINE">Running Services After the Network Is Up</ulink> for
+              more information.</para></listitem>
             </itemizedlist>
 
             <para>It must emphasized that at start-up there's no guarantee that hardware-based devices have
@@ -1003,11 +997,11 @@
         <varlistentry>
           <term><filename>network-pre.target</filename></term>
           <listitem>
-            <para>This passive target unit may be pulled in by services
-            that want to run before any network is set up, for example
-            for the purpose of setting up a firewall. All network
-            management software orders itself after this target, but
-            does not pull it in.</para>
+            <para>This passive target unit may be pulled in by services that want to run before any network
+            is set up, for example for the purpose of setting up a firewall. All network management software
+            orders itself after this target, but does not pull it in. Also see <ulink
+            url="https://systemd.io/NETWORK_ONLINE">Running Services After the Network Is Up</ulink> for more
+            information.</para>
           </listitem>
         </varlistentry>
         <varlistentry>