Move `browsingData` extension API out of experimental.

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

Index: chrome/common/extensions/docs/static/browsingData.html
diff --git a/chrome/common/extensions/docs/static/experimental.browsingData.html b/chrome/common/extensions/docs/static/browsingData.html
similarity index 70%
copy from chrome/common/extensions/docs/static/experimental.browsingData.html
copy to chrome/common/extensions/docs/static/browsingData.html
index 86e0fc2b98beb21e51f42569f163a822f101989e..27ed66b444b1a0d70f97cd0999ce3d72ce5c402d 100644
--- a/chrome/common/extensions/docs/static/experimental.browsingData.html
+++ b/chrome/common/extensions/docs/static/browsingData.html
@@ -2,18 +2,15 @@
 
 <!-- BEGIN AUTHORED CONTENT -->
 <p id="classSummary">
-  Use the <code>chrome.experimental.browsingData</code> module to remove
-  browsing data from a user's local profile. This module is still experimental.
-  For more information regarding the usage of experimental APIs, see the
-  <a href="experimental.html">chrome.experimental.* APIs</a> page.
+  Use the <code>chrome.browsingData</code> module to remove browsing data from a
+  user's local profile.
 </p>
 
 <h2 id="manifest">Manifest</h2>
 
 <p>
   You must declare the "clear" permission in the
-  <a href="manifest.html">extension manifest</a> to use this API. As the API is
-  still experimental, you must declare the "experimental" permisson as well.
+  <a href="manifest.html">extension manifest</a> to use this API.
 </p>
 
 <pre>{
@@ -21,7 +18,6 @@
   ...
   <b>"permissions": [
     "browsingData",
-    "experimental"
   ]</b>,
   ...
 }</pre>
@@ -48,7 +44,7 @@
 
 var millisecondsPerWeek = 1000 * 60 * 60 * 24 * 7;
 var oneWeekAgo = (new Date()).getTime() - millisecondsPerWeek;
-chrome.experimental.browsingData.remove({
+chrome.browsingData.remove({
   "since": oneWeekAgo
 }, {
   "appcache": true,
@@ -66,11 +62,11 @@ chrome.experimental.browsingData.remove({
 }, callback);</pre>
 
 <p>
-  The <code>chrome.experimental.browsingData.remove</code> method allows you to
-  remove various types of browsing data with a single call, and will be much
-  faster than calling multiple more specific methods. If, however, you only
-  want to clear one specific type of browsing data (cookies, for example), the
-  more granular methods offer a readable alternative to a call filled with JSON.
+  The <code>chrome.browsingData.remove</code> method allows you to remove
+  various types of browsing data with a single call, and will be much faster
+  than calling multiple more specific methods. If, however, you only want to
+  clear one specific type of browsing data (cookies, for example), the more
+  granular methods offer a readable alternative to a call filled with JSON.
 </p>
 
 <pre>var callback = function () {
@@ -79,7 +75,7 @@ chrome.experimental.browsingData.remove({
 
 var millisecondsPerWeek = 1000 * 60 * 60 * 24 * 7;
 var oneWeekAgo = (new Date()).getTime() - millisecondsPerWeek;
-chrome.experimental.browsingData.removeCookies({
+chrome.browsingData.removeCookies({
   "since": oneWeekAgo
 }, callback);</pre>
 
@@ -93,7 +89,7 @@ chrome.experimental.browsingData.removeCookies({
 <h2 id="samples">Examples</h2>
 <p>
   Samples for the <code>browsingData</code> API are available
-  <a href="http://code.google.com/chrome/extensions/trunk/samples.html#chrome.experimental.browsingData">on the samples page</a>.
+  <a href="http://code.google.com/chrome/extensions/trunk/samples.html#chrome.browsingData">on the samples page</a>.
 </p>
 
 <!-- END AUTHORED CONTENT -->