Reformat to align with web version: Replace <b> with <strong>

perl -i~ -pe 's{\<(/?)b\>}{<$1strong>}g' security_vulnerability_process.html

Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>

diff --git a/security_vulnerability_process.html b/security_vulnerability_process.html
index c72e2a06dd351a23e785323a92ef9fb12eb70cac..33afb6fd1f9b5ebb3be651de06c7a69b3f8b11fe 100644 (file)
--- a/security_vulnerability_process.html
+++ b/security_vulnerability_process.html
@@ -21,21 +21,21 @@
 <li><p>We will determine which systems/configurations/versions are vulnerable, and what the impact of the vulnerability is. Depending on the nature of the vulnerability this may involve sharing information about the vulnerability (in confidence, if the issue is embargoed) with hardware vendors and/or other software projects.</p></li>
 <li><p>We will write a Xen advisory including information from (b)-(f)</p></li>
 </ol>
-<li><p><b>Advisory pre-release:</b></p>
+<li><p><strong>Advisory pre-release:</strong></p>
 <p>This occurs only if the advisory is embargoed (ie, the problem is not already public):</p>
 <p>As soon as our advisory is available, we will send it, including patches, to members of the Xen security pre-disclosure list. For more information about this list, see below.</p>
 <p>At this stage the advisory will be clearly marked with the embargo date.</p>
 </li>
-<li><p><b>Advisory public release:</b></p>
+<li><p><strong>Advisory public release:</strong></p>
 <p>At the embargo date we will publish the advisory, and push bugfix changesets to public revision control trees.</p>
 <p>Public advisories will be posted to xen-devel, xen-users and xen-annnounce and will be added to the
 <a href="http://wiki.xen.org/wiki/Security_Announcements">Security Announcements wiki page</a>.</p>
 <p>Copies will also be sent to the pre-disclosure list.</p>
 </li>
-<li><p><b>Updates</b></p>
+<li><p><strong>Updates</strong></p>
 <p>If new information or better patches become available, or we discover mistakes, we may issue an amended (revision 2 or later) public advisory.  This will also be sent to the pre-disclosure list.</p>
 </li>
-<li><p><b>Post embargo transparency:</b></p>
+<li><p><strong>Post embargo transparency:</strong></p>
 <p>During an embargo period the Xen.org security response team may be required to make potentially controverial decisions in private, since they cannot confer with the community without breaking the embargo. The security team will attempt to make such decisions following the guidance of this document and where necessary their own best judgement. Following the embargo period any such decisions will be disclosed to the community in the interests of transparency and to help provide guidance should a similar decision be required in the future.</p>
 </li>
 </ol>
@@ -108,9 +108,9 @@
 </ul></p>
 <h2>Change History</h2>
 <ul>
-<li><b>v1.4 Apr 2013:</b> Predisclosure list criteria changes</li>
-<li><b>v1.3 Aug 2012:</b> Various minor updates</li>
-<li><b>v1.2 Apr 2012:</b> Added pre-disclosure list</li>
-<li><b>v1.1 Feb 2012:</b> Added link to Security Announcements wiki page</li>
-<li><b>v1.0 Dec 2011:</b> Intial document published after review</li>
+<li><strong>v1.4 Apr 2013:</strong> Predisclosure list criteria changes</li>
+<li><strong>v1.3 Aug 2012:</strong> Various minor updates</li>
+<li><strong>v1.2 Apr 2012:</strong> Added pre-disclosure list</li>
+<li><strong>v1.1 Feb 2012:</strong> Added link to Security Announcements wiki page</li>
+<li><strong>v1.0 Dec 2011:</strong> Intial document published after review</li>
 </ul>