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.</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>