doc: update links to chrony website

README

@@ -47,7 +47,7 @@ Frequently Asked Questions (FAQ).
 The documentation is also available on the chrony web pages, accessible
 through the URL 
 
-    https://chrony.tuxfamily.org/
+    https://chrony-project.org/
 
 License
 =======

doc/chrony.conf.adoc

@@ -3137,7 +3137,7 @@ dumpdir @CHRONYRUNDIR@
 == BUGS
 
 For instructions on how to report bugs, please visit
-https://chrony.tuxfamily.org/.
+https://chrony-project.org/.
 
 == AUTHORS
 

doc/chronyc.adoc

@@ -1548,7 +1548,7 @@ The *help* command displays a summary of the commands and their arguments.
 == BUGS
 
 For instructions on how to report bugs, please visit
-https://chrony.tuxfamily.org/.
+https://chrony-project.org/.
 
 == AUTHORS
 

doc/chronyd.adoc

@@ -217,7 +217,7 @@ _@SYSCONFDIR@/chrony.conf_
 == BUGS
 
 For instructions on how to report bugs, please visit
-https://chrony.tuxfamily.org/.
+https://chrony-project.org/.
 
 == AUTHORS
 

doc/faq.adoc

@@ -40,7 +40,7 @@ on an isolated network with no hardware reference clocks in sight, `chrony`
 will probably work better for you.
 
 For a more detailed comparison of features and performance, see the
-https://chrony.tuxfamily.org/comparison.html[comparison page] on the `chrony`
+https://chrony-project.org/comparison.html[comparison page] on the `chrony`
 website.
 
 === Should I prefer `chrony` over `timesyncd` if I do not need to run a server?
@@ -50,7 +50,7 @@ Generally, yes.
 `systemd-timesyncd` is a very simple NTP client included in the `systemd`
 suite. It lacks almost all features of `chrony` and other advanced client
 implementations listed on the
-https://chrony.tuxfamily.org/comparison.html[comparison page]. One of its main
+https://chrony-project.org/comparison.html[comparison page]. One of its main
 limitations is that it cannot poll multiple servers at the same time and detect
 servers having incorrect time (falsetickers in the NTP terminology). It should
 be used only with trusted reliable servers, ideally in local network.