[pve-devel] [PATCH docs 05/10] Rewrite Timesync

[Aaron Lauterer]

Polished phrasing

Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
---
 system-timesync.adoc | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/system-timesync.adoc b/system-timesync.adoc
index c64455c..b3ffe5b 100644
--- a/system-timesync.adoc
+++ b/system-timesync.adoc
@@ -4,25 +4,25 @@ ifdef::wiki[]
 :pve-toplevel:
 endif::wiki[]
 
-The {pve} cluster stack itself relies heavily on the fact that all
-the nodes have precisely synchronized time. Some other components,
-like Ceph, also refuse to work properly if the local time on nodes is
-not in sync.
+For the {pve} Cluster stack and other components like Ceph it is of
+the utmost importance the the time on all nodes is precisely
+synchronized. The ``Network Time Protocol'' (`NTP`) solves this
+problem.
 
-Time synchronization between nodes can be achieved with the ``Network
-Time Protocol'' (`NTP`). {pve} uses `systemd-timesyncd` as NTP client
-by default, preconfigured to use a set of public servers. This setup
-works out of the box in most cases.
+By default {pve} is using `systemd-timesyncd` as NTP client. A set of
+public time servers is preconfigured. This setup should be working for
+most situations.
 
 
 Using Custom NTP Servers
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
-In some cases, it might be desired to not use the default NTP
-servers. For example, if your {pve} nodes do not have access to the
-public internet (e.g., because of restrictive firewall rules), you
-need to setup local NTP servers and tell `systemd-timesyncd` to use
-them:
+In some situations it can be necessary to configure different NTP
+servers, for example if the {pve} hosts cannot access the public
+internet (e.g. because of strict firewall rules).
+
+To change the NTP servers to other (local) ones the file
+`/etc/systemd/timesyncd.conf` needs to be edited.
 
 .File `/etc/systemd/timesyncd.conf`
 ----
@@ -31,7 +31,7 @@ NTP=ntp1.example.com ntp2.example.com ntp3.example.com ntp4.example.com
 ----
 
 After restarting the synchronization service (`systemctl restart
-systemd-timesyncd`) you should verify that your newly configured NTP
+systemd-timesyncd`) verify that the newly configured NTP
 servers are used by checking the journal (`journalctl --since -1h -u
 systemd-timesyncd`):
 
-- 
2.20.1