Extensions Docs Server: Doc conversion script - SVN

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

-<div id="pageData-name" class="pageData">Omnibox</div>
-
-<!-- BEGIN AUTHORED CONTENT -->
 <p>
 The omnibox API allows you to register a
 keyword with Google Chrome's address bar,
 which is also known as the omnibox.
 </p>
 
 <p>
-<img src="../images/omnibox.png" width="300" height="150"
+<img src="{{static}}/images/omnibox.png" width="300" height="150"
   alt="A screenshot showing suggestions related to the keyword 'Chromium Search'"/>
 </p>
 
 <p>
 When the user enters your extension's
 keyword, the user starts
 interacting solely with your extension.
 Each keystroke is sent to your
 extension, and you can provide suggestions
 in response.
 </p>
 
 <p>
 The suggestions can be richly formatted
 in a variety of ways.
-<!-- PENDING: for example? (include a mention of method name, maybe show a code snippet) -->
+
 When the user accepts
 a suggestion, your extension is notified
 and can take action.
 </p>
 
 <h2 id="manifest">Manifest</h2>
 
 <p>
 You must include an <code>omnibox</code> <code>keyword</code> field
 in the <a href="manifest.html">manifest</a> 
@@ skipping 29 matching lines @@
 For example, the <a href="contextMenus.html"
 >context menus API</a> also uses a 16x16-pixel
 icon, but it is displayed in color.
 </p>
 
 
 <h2 id="examples">Examples</h2>
 
 <p>
 You can find samples of this API on the
-<a href="samples.html#omnibox">sample page</a>.
-
-<!-- END AUTHORED CONTENT -->
+<a href="samples.html#omnibox">sample page</a>.