Extensions Docs Server: Doc conversion script

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

-<!-- BEGIN AUTHORED CONTENT -->
 <p id="classSummary">
 Use the <code>chrome.storage</code> module
 to store, retrieve, and track changes to user data.
 This API has been optimized
 to meet the specific storage needs of extensions.
 It provides the same storage capabilities as the
 <a href="https://developer.mozilla.org/en/DOM/Storage#localStorage">localStorage API</a>
 with the following key differences:
 </p>
 <ul>
   <li>User data can be automatically synced with Chrome sync
   (using <code>storage.sync</code>).</li>
   <li>Your extension's content scripts can directly access user data
   without the need for a background page.</li>
   <li>A user's extension settings can be persisted
   even when using
   <a href="manifest.html#incognito">split incognito behavior</a>.</li>
   <li>User data can be stored as objects
   (the <code>localStorage API</code> stores data in strings).</li>
+  <li>Domain policies configured by the administrator for the extension
+  can be read (using <code>storage.managed</code>).</li>
 </ul>
 <h2 id="manifest">Manifest</h2>
 <p>You must declare the "storage" permission in the <a
   href="manifest.html">extension manifest</a>
   to use the storage API.
   For example:</p>
 <pre>{
   "name": "My extension",
   ...
   <b>"permissions": [
@@ skipping 19 matching lines @@
 Chrome syncs the data.
 Even if a user disables syncing,
 <code>storage.sync</code> will still work.
 In this case, it will behave identically
 to <code>storage.local</code>.
 </p>
 <p class="warning">
 Confidential user information should not be stored!
 The storage area isn't encrypted.
 </p>
+<p>
+The <code>storage.managed</code> is a read-only
+storage that contains settings configured by the
+domain administrator for the extension. Enforcing
+these settings allows administrators to configure
+your extension on enterprise deployments.
+</p>
 <h2 id="limits">Storage and throttling limits</h2>
 <p><code>chrome.storage</code> is not a big truck.
 It's a series of tubes.
 And if you don't understand,
 those tubes can be filled,
 and if they are filled
 when you put your message in,
 it gets in line,
 and it's going to be delayed
 by anyone that puts into that tube
@@ skipping 44 matching lines @@
                 key,
                 namespace,
                 storageChange.oldValue,
                 storageChange.newValue);
   }
 });
 </pre>
 <p>
 You can find examples that use this API on the
 <a href="samples.html#sty">Samples page</a>.
-</p>
-<!-- END AUTHORED CONTENT -->
+</p>