Disable the managed storage API behind a flag for M22.

chrome/common/extensions/docs/static/storage.html

Index: chrome/common/extensions/docs/static/storage.html
diff --git a/chrome/common/extensions/docs/static/storage.html b/chrome/common/extensions/docs/static/storage.html
index 125bb0cb203e7ee8955664d521923d9f2e2646fe..02065f8e5d7d623494bd920b589b86e72cb6b649 100644
--- a/chrome/common/extensions/docs/static/storage.html
+++ b/chrome/common/extensions/docs/static/storage.html
@@ -21,8 +21,6 @@ with the following key differences:
   <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>
@@ -68,14 +66,6 @@ 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.