From 85f44cd2c508d6fa7ca5c6f3622504590c5f9f8b Mon Sep 17 00:00:00 2001 From: Warren Block Date: Mon, 29 Jun 2015 16:41:41 +0000 Subject: Whitespace-only fixes, translators please ignore. --- en_US.ISO8859-1/articles/leap-seconds/article.xml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/en_US.ISO8859-1/articles/leap-seconds/article.xml b/en_US.ISO8859-1/articles/leap-seconds/article.xml index fe72fba11f..a9f1a1b194 100644 --- a/en_US.ISO8859-1/articles/leap-seconds/article.xml +++ b/en_US.ISO8859-1/articles/leap-seconds/article.xml @@ -21,9 +21,9 @@ seconds. As of this writing, the next leap second will occur at - 2015-Jun-30 23:59:60 UTC. This leap second will occur during - a business day for North and South - America and the Asia/Pacific region. + 2015-Jun-30 23:59:60 UTC. This leap second will occur during a + business day for North and South America and the Asia/Pacific + region. Leap seconds are announced by IERS @@ -104,16 +104,16 @@ &prompt.user; ntpq -c 'rv 0 leap' Output that includes leap_add_sec - indicates proper support of the leap second. Before the 24 hours - leading up to the leap second, or after the leap second has - passed, leap_none will be shown. + indicates proper support of the leap second. Before the 24 + hours leading up to the leap second, or after the leap second + has passed, leap_none will be shown. Conclusion - In practice, leap seconds are usually not a problem on &os;. We - hope that this overview helps clarify what to expect and how to - make the leap second event proceed more smoothly. + In practice, leap seconds are usually not a problem on &os;. + We hope that this overview helps clarify what to expect and how + to make the leap second event proceed more smoothly. -- cgit v1.3