Fix other </a> and spell out IRC network

Author: edunham

security.html

@@ -5,9 +5,9 @@
 
 <h2>Reporting a Bug</h2>
 
-<p>Safety is one of the core principles of Rust, and to that end, we would like to
-ensure that Rust has a secure implementation. Thank you for taking the time to
-responsibly disclose any issues you find.</p>
+<p>Safety is one of the core principles of Rust, and to that end, we would
+like to ensure that Rust has a secure implementation. Thank you for taking the
+time to responsibly disclose any issues you find.</p>
 
 <p>All security bugs in the Rust distribution should be reported by email to
 <a href="mailto:[email protected]">[email protected]</a>. This list
@@ -32,9 +32,13 @@ <h2>Reporting a Bug</h2>
 can take:</p>
 
 <ul>
-        <li>Contact the current security coordinator (<a href="mailto:[email protected]">Steve Klabnik</a> (<a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0xDAE717EFE9424541">public key</a>)) directly.</li>
-        <li>Contact the back-up contact (<a href="mailto:[email protected]">Brian Anderson</a> (<a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0x16457A6368CFF26F">public key</a>)) directly.</li>
-        <li>Post on the <a href="https://internals.rust-lang.org/">internals forums</a> or ask in the #rust-internals IRC room on MozNet.</li>
+    <li>Contact the current security coordinator (<a href="mailto:[email protected]">
+         Steve Klabnik</a> (<a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0xDAE717EFE9424541">
+         public key</a>)) directly.</li>
+    <li>Contact the back-up contact (<a href="mailto:[email protected]">Brian Anderson</a> 
+        (<a href="https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0x16457A6368CFF26F">public key</a>)) directly.</li>
+    <li>Post on the <a href="https://internals.rust-lang.org/">internals forums</a> 
+    or ask in the #rust-internals IRC room on irc.mozilla.org.</li>
 </ul>
 
 <p>Please note that the discussion forums and #rust-internals IRC channel are
@@ -54,7 +58,9 @@ <h2>Disclosure Policy</h2>
 
 <li>Code is audited to find any potential similar problems.</li>
 
-<li>Fixes are prepared for all releases which are still under maintenance. These fixes are not committed to the public repository but rather held locally pending the announcement.</li>
+<li>Fixes are prepared for all releases which are still under maintenance.
+These fixes are not committed to the public repository but rather held locally
+pending the announcement.</li>
 
 <li>On the embargo date, the <a href="https://groups.google.com/forum/#!forum/rustlang-security-announcements">
 Rust security mailing list</a> is sent a copy of the announcement. The changes
@@ -71,12 +77,16 @@ <h2>Disclosure Policy</h2>
 <h2>Receiving Security Updates</h2>
 
 <p>The best way to receive all the security announcements is to subscribe to
-the <a href="https://groups.google.com/forum/#!forum/rustlang-security-announcements"></a>Rust security announcements mailing list</a>. The mailing list is very low traffic, and it
-receives the public notifications the moment the embargo is lifted.</p>
+the <a
+href="https://groups.google.com/forum/#!forum/rustlang-security-announcements">Rust
+security announcements mailing list</a>. The mailing list is very low traffic,
+and it receives the public notifications the moment the embargo is lifted.</p>
 
 <h3>Advance notification</h3>
 
-<p>We will announce vulnerabilities 72 hours before the embargo is lifted to <a href="http://oss-security.openwall.org/wiki/mailing-lists/distros">distros@openwall</a>, so that Linux distributions can update their packages.</p>
+<p>We will announce vulnerabilities 72 hours before the embargo is lifted to
+<a href="http://oss-security.openwall.org/wiki/mailing-lists/distros">distros@openwall</a>,
+so that Linux distributions can update their packages.</p>
 
 <h2>Comments on This Policy</h2>