Take notification API out of experimental.

chrome/common/extensions/docs/templates/intros/notifications.html

Index: chrome/common/extensions/docs/templates/intros/notifications.html
diff --git a/chrome/common/extensions/docs/templates/intros/experimental_notification.html b/chrome/common/extensions/docs/templates/intros/notifications.html
similarity index 93%
rename from chrome/common/extensions/docs/templates/intros/experimental_notification.html
rename to chrome/common/extensions/docs/templates/intros/notifications.html
index 8789e44c8dcfa5cf346242f1835de5feb505d5e4..4a1ae7027609d7b194070af4dcb9a525d5152800 100644
--- a/chrome/common/extensions/docs/templates/intros/experimental_notification.html
+++ b/chrome/common/extensions/docs/templates/intros/notifications.html
@@ -33,7 +33,7 @@ Currently this API only works on ChromeOS and Windows.
 
 <p>
 To use this API,
-call the $ref:experimental.notification.create method,
+call the $ref:notifications.create method,
 passing in the notification details
 via the <code>options</code> parameter:
 </p>
@@ -44,8 +44,8 @@ chrome.experimental.notification
 </pre>
 
 <p>
-The $ref:experimental.notification.NotificationOptions must include the
-$ref:experimental.notification.TemplateType
+The $ref:notifications.NotificationOptions must include the
+$ref:notifications.TemplateType
 which defines available notification details
 and how those details are displayed.
 All four available template types
@@ -112,10 +112,10 @@ all notifications can include event listeners and event handlers
 which respond to user actions.
 For example,
 you can write an event handler to respond to an
-$ref:experimental.notification.onButtonClicked event.
+$ref:notifications.onButtonClicked event.
 </p>
 
 <p>Consider including event listeners and handlers within the
   <a href="app_lifecycle.html#create_event_page">event page</a>,
 so that notifications can pop-up even when the app or extension isn't running.
-</p>
+</p>