man: Fix reference to timer-sync.target instead of time-sync.target (#5764)

Also fix an erroneous reference to it in the NEWS file, for posterity.

Signed-off-by: Philip Withnall <withnall@endlessm.com>

diff --git a/NEWS b/NEWS
index f177ca31e6497c3c05bc08e071a1d6d3c3989ddb..73ee35f53c86acaea8d55a13185ebe4fbcd8585a 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -3318,7 +3318,7 @@ CHANGES WITH 216:
           like Cockpit which register web clients as PAM sessions.
 
         * timer units with at least one OnCalendar= setting will now
-          be started only after timer-sync.target has been
+          be started only after time-sync.target has been
           reached. This way they will not elapse before the system
           clock has been corrected by a local NTP client or
           similar. This is particular useful on RTC-less embedded

diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml
index 4fe140e4bc3c0aa7cf2db574ab8880469386ac1e..7102d626e1b0ffbe015e5fc25d02463e757d2d02 100644 (file)
--- a/man/systemd.timer.xml
+++ b/man/systemd.timer.xml
@@ -93,7 +93,7 @@
     on <filename>timers.target</filename>, as well as <varname>Conflicts=</varname> and <varname>Before=</varname> on
     <filename>shutdown.target</filename> to ensure that they are stopped cleanly prior to system shutdown.  Timer units
     with at least one <varname>OnCalendar=</varname> directive will have an additional <varname>After=</varname>
-    dependency on <filename>timer-sync.target</filename> to avoid being started before the system clock has been
+    dependency on <filename>time-sync.target</filename> to avoid being started before the system clock has been
     correctly set. Only timer units involved with early boot or late system shutdown should disable the
     <varname>DefaultDependencies=</varname> option.</para>
   </refsect1>