commit d66287db33e3a19a6d7146f4575bdda5c561a1a3
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Wed Jul 30 23:29:27 2014 +0200
Putting a space between RFC and the number {for consistency}
en-US/Configuring_NTP_Using_the_chrony_Suite.xml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
b/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
index 1068221..53eaaa6 100644
--- a/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
+++ b/en-US/Configuring_NTP_Using_the_chrony_Suite.xml
@@ -82,7 +82,7 @@ Things <systemitem
class="daemon">ntpd</systemitem> can do that <systemitem clas
<itemizedlist>
<listitem>
<para>
- <systemitem class="daemon">ntpd</systemitem> fully supports
<systemitem class="protocol">NTP</systemitem> version 4
(<citetitle pubwork="webpage">RFC5905</citetitle>), including
broadcast, multicast, manycast clients and servers, and the orphan mode. It also supports
extra authentication schemes based on public-key cryptography (<citetitle
pubwork="webpage">RFC5906</citetitle>). <systemitem
class="daemon">chronyd</systemitem> uses <systemitem
class="protocol">NTP</systemitem> version 3 (<citetitle
pubwork="webpage">RFC1305</citetitle>), which is compatible with
version 4.
+ <systemitem class="daemon">ntpd</systemitem> fully supports
<systemitem class="protocol">NTP</systemitem> version 4
(<citetitle pubwork="webpage">RFC 5905</citetitle>), including
broadcast, multicast, manycast clients and servers, and the orphan mode. It also supports
extra authentication schemes based on public-key cryptography (<citetitle
pubwork="webpage">RFC 5906</citetitle>). <systemitem
class="daemon">chronyd</systemitem> uses <systemitem
class="protocol">NTP</systemitem> version 3 (<citetitle
pubwork="webpage">RFC 1305</citetitle>), which is compatible with
version 4.
</para>
</listitem>
<listitem>