From owner-svn-doc-all@freebsd.org  Mon Jun 29 16:41:42 2015
Return-Path: <owner-svn-doc-all@freebsd.org>
Delivered-To: svn-doc-all@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12BF19900B8;
 Mon, 29 Jun 2015 16:41:42 +0000 (UTC)
 (envelope-from wblock@FreeBSD.org)
Received: from svn.freebsd.org (svn.freebsd.org
 [IPv6:2001:1900:2254:2068::e6a:0])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D9751282F;
 Mon, 29 Jun 2015 16:41:41 +0000 (UTC)
 (envelope-from wblock@FreeBSD.org)
Received: from svn.freebsd.org ([127.0.1.70])
 by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t5TGffuA031212;
 Mon, 29 Jun 2015 16:41:41 GMT (envelope-from wblock@FreeBSD.org)
Received: (from wblock@localhost)
 by svn.freebsd.org (8.14.9/8.14.9/Submit) id t5TGff93031211;
 Mon, 29 Jun 2015 16:41:41 GMT (envelope-from wblock@FreeBSD.org)
Message-Id: <201506291641.t5TGff93031211@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: wblock set sender to
 wblock@FreeBSD.org using -f
From: Warren Block <wblock@FreeBSD.org>
Date: Mon, 29 Jun 2015 16:41:41 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
 svn-doc-head@freebsd.org
Subject: svn commit: r46895 - head/en_US.ISO8859-1/articles/leap-seconds
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-all@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "SVN commit messages for the entire doc trees \(except for &quot;
 user&quot; , &quot; projects&quot; , and &quot; translations&quot;
 \)" <svn-doc-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>,
 <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all/>
List-Post: <mailto:svn-doc-all@freebsd.org>
List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>,
 <mailto:svn-doc-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2015 16:41:42 -0000

Author: wblock
Date: Mon Jun 29 16:41:41 2015
New Revision: 46895
URL: https://svnweb.freebsd.org/changeset/doc/46895

Log:
  Whitespace-only fixes, translators please ignore.

Modified:
  head/en_US.ISO8859-1/articles/leap-seconds/article.xml

Modified: head/en_US.ISO8859-1/articles/leap-seconds/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/leap-seconds/article.xml	Mon Jun 29 15:32:11 2015	(r46894)
+++ head/en_US.ISO8859-1/articles/leap-seconds/article.xml	Mon Jun 29 16:41:41 2015	(r46895)
@@ -21,9 +21,9 @@
       seconds.</para>
 
     <para>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.</para>
+      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.</para>
 
     <para>Leap seconds are announced by <link
 	xlink:href="http://datacenter.iers.org/"><acronym>IERS</acronym></link>
@@ -104,16 +104,16 @@
     <screen>&prompt.user; <userinput>ntpq -c 'rv 0 leap'</userinput></screen>
 
     <para>Output that includes <literal>leap_add_sec</literal>
-      indicates proper support of the leap second.  Before the 24 hours
-      leading up to the leap second, or after the leap second has
-      passed, <literal>leap_none</literal> will be shown.</para>
+      indicates proper support of the leap second.  Before the 24
+      hours leading up to the leap second, or after the leap second
+      has passed, <literal>leap_none</literal> will be shown.</para>
   </sect1>
 
   <sect1 xml:id="leapseconds-conclusion">
     <title>Conclusion</title>
 
-    <para>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.</para>
+    <para>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.</para>
   </sect1>
 </article>