Rename <browser> shim to <webview>

chrome/common/extensions/docs/templates/articles/app_external.html

 <h1>Embed Content</h1>
 
 
 <p>
 The <a href="app_architecture.html#security">packaged apps security model</a> disallows
 external content in iframes and
 the use of inline scripting and <code>eval()</code>.
 You can override these restrictions,
 but your external content must be isolated from the app.
 </p>
@@ skipping 53 matching lines @@
   img.src = window.webkitURL.createObjectURL(this.response);
   document.body.appendChild(img);
 };
 
 xhr.send();
 </pre>
 
 <p>You may want to <a href="offline_apps.html#saving-locally">save</a>
 these resources locally, so that they are available offline.</p>
 
-<h2 id="browsertag">Embed external web pages</h2>
+<h2 id="webview">Embed external web pages</h2>
 
 <p class="note">
 <b>API Sample: </b>
 Want to play with the code? Check out the
-<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/browser-tag">browser-tag</a>
+<a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/browser-tag">webview</a>
 sample.
 </p>
 
 <p>
-The <code>browser</code> tag allows you to embed external web content in your
+The <code>webview</code> tag allows you to embed external web content in your
 app, for example, a web page. It replaces iframes that point to remote URLs,
 which are disabled inside packaged apps. Unlike iframes, the
-<code>browser</code> tag runs in a separate process. This means that an exploit
+<code>webview</code> tag runs in a separate process. This means that an exploit
 inside of it will still be isolated and won't be able to gain elevated
 privileges. Further, since its storage (cookies, etc.) is isolated from the app,
 there is no way for the web content to access any of the app's data.
 </p>
 
-<h3 id="browser_element">Add browser element</h3>
+<h3 id="webview_element">Add webview element</h3>
 
 <p>
-Your <code>browser</code> element must include the URL to the source content
+Your <code>webview</code> element must include the URL to the source content
 and specify its dimensions.
 </p>
 
-<pre>&lt;browser src="http://news.google.com/" width="640" height="480">&lt;/browser></pre>
+<pre>&lt;webview src="http://news.google.com/" width="640" height="480">&lt;/webview></pre>
 
 <h3 id="properties">Update properties</h3>
 
 <p>
 To dynamically change the <code>src</code>, <code>width</code> and
-<code>height</code> properties of a <code>browser</code> tag, you can either
+<code>height</code> properties of a <code>webview</code> tag, you can either
 set those properties directly on the JavaScript object, or use the
 <code>setAttribute</code> DOM function.
 </p>
 
 <pre>
-document.querySelector('#mybrowser').src =
+document.querySelector('#mywebview').src =
     'http://blog.chromium.org/';
 // or
-document.querySelector('#mybrowser').setAttribute(
+document.querySelector('#mywebview').setAttribute(
     'src', 'http://blog.chromium.org/');
 </pre>
 
 <h2 id="sandboxing">Sandbox local content</h2>
 
 <p>
 Sandboxing allows specified pages
 to be served in a sandboxed, unique origin.
 These pages are then exempt from their Content Security Policy.
 Sandboxed pages can use iframes, inline scripting,
@@ skipping 146 matching lines @@
 
 <pre>
 var messageHandler = function(e) {
   console.log('Background script says hello.', e.data);
 };
 
 window.addEventListener('message', messageHandler);
 </pre>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>