svn commit: r49580 - head/en_US.ISO8859-1/htdocs/security

[Glen Barber]

Author: gjb
Date: Tue Oct 25 16:44:27 2016
New Revision: 49580
URL: https://svnweb.freebsd.org/changeset/doc/49580

Log:
  Make igor(1) less unhappy about security.xml.
  Translators can ignore, this is whitespace-only.
  
  Sponsored by:	The FreeBSD Foundation

Modified:
  head/en_US.ISO8859-1/htdocs/security/security.xml

Modified: head/en_US.ISO8859-1/htdocs/security/security.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/security/security.xml	Tue Oct 25 16:38:42 2016	(r49579)
+++ head/en_US.ISO8859-1/htdocs/security/security.xml	Tue Oct 25 16:44:27 2016	(r49580)
@@ -89,19 +89,19 @@
     which is primarily oriented towards &os; developers.)</p>
 
   <ul>
-    <li><p>The -STABLE branch tags have
-	names like <tt>stable/10</tt>.  The corresponding builds have
-      names like <tt>FreeBSD 10.1-STABLE</tt>.</p></li>
+    <li><p>The -STABLE branch tags have names like <tt>stable/10</tt>.
+      The corresponding builds have names like <tt>FreeBSD
+      10.1-STABLE</tt>.</p></li>
 
     <li><p>Each FreeBSD Release has an associated Security Branch.
-	The Security Branch tags have names like <tt>releng/10.1</tt>.
+      The Security Branch tags have names like <tt>releng/10.1</tt>.
       The corresponding builds have names like <tt>FreeBSD
       10.1-RELEASE-p4</tt>.</p></li>
   </ul>
 
-  <p>Issues affecting the FreeBSD Ports Collection are covered separately in <a
-      href="http://vuxml.FreeBSD.org/">the FreeBSD VuXML
-      document</a>.</p>
+  <p>Issues affecting the FreeBSD Ports Collection are covered
+    separately in <a href="http://vuxml.FreeBSD.org/">the FreeBSD
+      VuXML document</a>.</p>
 
   <a name="how"></a>
   <h2>How to update your system</h2>
@@ -210,8 +210,8 @@
     </tr>
   </table>
 
-  <p>In the run-up to a release, a number of -BETA
-    and -RC releases may be published for testing purposes.  These releases are only
+  <p>In the run-up to a release, a number of -BETA and -RC releases
+    may be published for testing purposes.  These releases are only
     supported for a few weeks, as resources permit, and will not be
     listed as supported on this page.  Users are strongly discouraged
     from running these releases on production systems.</p>
@@ -229,9 +229,9 @@
     release.</p>
 
   <p>The details and rationale behind this change can be found in the
-      <a
-	href="https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624.html">official
-	announcement</a> sent in February 2015.</p>
+    <a
+      href="https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624.html">official
+      announcement</a> sent in February 2015.</p>
 
   <p>Previously, branches were designated as either <em>Normal</em> or
     <em>Extended</em>.  The designation was used as a guideline for
@@ -240,18 +240,18 @@
   <dl>
     <dt>Normal</dt>
     <dd>Releases which are published from a -STABLE branch were
-      supported by the Security Officer for a minimum of 12 months after the
-      release, and for sufficient additional time (if needed) to ensure
-      that there is a newer release for at least 3 months before the
-      older Normal release expires.
+      supported by the Security Officer for a minimum of 12 months
+      after the release, and for sufficient additional time (if
+      needed) to ensure that there is a newer release for at least
+      3 months before the older Normal release expires.
     </dd>
     <dt>Extended</dt>
     <dd>Selected releases (normally every second release plus the last
-      release from each -STABLE branch) were supported by the
-      Security Officer for a minimum of 24 months after the release,
-      and for sufficient additional time (if needed) to ensure that
-      there is a newer Extended release for at least 3 months before the
-      older Extended release expires.
+      release from each -STABLE branch) were supported by the Security
+      Officer for a minimum of 24 months after the release, and for
+      sufficient additional time (if needed) to ensure that there is
+      a newer Extended release for at least 3 months before the older
+      Extended release expires.
     </dd>
   </dl>
 </body>