Extension Docs Server Version 2: Various fixes.

chrome/common/extensions/docs/server2/templates/intros/permissions.html

 <!-- BEGIN AUTHORED CONTENT -->
 <p id="classSummary">
   Use the <code>chrome.permissions</code> module to implement
   optional permissions. You can request optional permissions during your
   extension's regular application flow rather than at install time, so users
   understand why the permissions are needed and use only those that are
   necessary.
 </p>
 <p>
   For general information about permissions and details about each permission,
   see the <a href="manifest.html#permissions">permissions</a> section of the
   manifest documentation.
 </p>
 <h2 id="howto"> Implementing optional permissions </h2>
 
-<h3 id="types">
-  Step 1: Decide which permissions are optional and required
-</h3>
+<h3 id="types"> Step 1: Decide which permissions are optional and required </h3>

[not at google - send to devlin, 2012/07/20 02:04:54]

maybe we should fix the parser rather than fix the HTML... this is probably just
going to happen again. The current parser is just regex I believe but python has
HTML parsers.

do that later though, this change is fine for now.

 <p>
   Extensions should generally require permissions when they are needed for the
   extension's basic functionality and employ optional permissions for optional
   features.
 </p>
 <p>
   Advantages of optional permissions:
   <ul>
     <li>
       Users run with less permissions since they enable only what is needed.
@@ skipping 126 matching lines @@
 }, function(removed) {
   if (removed) {
     // The permissions have been removed.
   } else {
     // The permissions have not been removed (e.g., you tried to remove
     // required permissions).
   }
 });
 </pre>
 <!-- END AUTHORED CONTENT -->