Typo fixes, plus a couple of code changes....

common/extensions/docs/static/content_scripts.html

 <div id="pageData-title" class="pageData">Content Scripts</div>
 <div id="pageData-showTOC" class="pageData">true</div>
 
 <p>Content Scripts are JavaScript files that run in the context of web pages. By using the standard <a href="http://www.w3.org/TR/DOM-Level-2-HTML/">Document Object Model</a> (DOM), they can read details of the web pages the browser visits, or make changes to them. 
 
 <p>Some examples of things that content scripts can do include:
 
 <ul>
   <li>Find unlinked URLs in web pages and convert them into hyperlinks
   <li>Increase the font size to make text more legible
@@ skipping 106 matching lines @@
 ================
 var e = document.getElementById("login");
 
 // Create a short-lived named channel to the extension and send a single
 // message through it.
 var port = chrome.extension.connect({name: "notifyChannel"});
 port.postMessage({found: (e != undefined)});
 
 // Also listen for new channels from the extension for when the button is
 // pressed.
-chrome.extension.onConnect.addListener(function(port, name) {
-  console.assert(name == "buttonClickedChannel");
+chrome.extension.onConnect.addListener(function(port) {
+  console.assert(port.name == "buttonClickedChannel");
   port.onMessage.addListener(function(msg) {
     if (msg.buttonClicked) {
       e.value = msg.passwordValue;
     }
   });
 });
 </pre>
 
 <p>with a toolstrip that looks like:
 
@@ skipping 28 matching lines @@
 <p>Although the execution environments of content scripts and the pages that host them are isolated from each other, they share access to the page's DOM. If the page wishes to communicate with the content script (or with the extension via the content script), it must do so through the shared DOM.</p>
 
 <p>An example can be accomplished using custom DOM events and storing data in a known location. Consider: </p>
 
 <pre>http://foo.com/example.html
 ================================
 var customEvent = document.createEvent('Event');
 customEvent.initEvent('myCustomEvent', true, true);
 
 function fireCustomEvent(data) {
-  hidenDiv = document.getElementById('myCustomEventDiv');
-  hidenDiv.innerHTML = data
-  hidenDiv.dispatchEvent(customEvent);
+  hiddenDiv = document.getElementById('myCustomEventDiv');
+  hiddenDiv.innerHTML = data
+  hiddenDiv.dispatchEvent(customEvent);
 }</pre>
 
 <pre>contentscript.js
 =====================
 var port = chrome.extension.connect();
 
 document.getElementById('myCustomEventDiv').addEventListener('myCustomEvent', function() {
   var eventData = document.getElementById('myCustomEventDiv').innerHTML;
   port.postMessage({message: "myCustomEvent", values: eventData});
 });</pre>
 
 <p>In the above example, example.html (which is not a part of the extension) creates a custom event and then can decide to fire the event by setting the event data to a known location in the DOM and then dispatching the custom event. The content script listens for the name of the custom event on the known element and handles the event by inspecting the data of the element, and turning around to post the message to the extension process. In this way the page establishes a line of communication to the extension. The reverse is possible through similar means.</p>
 
 <h2 id="extension-files">Referring to extension files</h2>
 
 <p>
 Get the URL of an extension's file using
 <code>chrome.extension.getURL()</code>.
 You can use the result
 just like you would any other URL,
 as the following code shows.
 </p>
 
 
 <pre>
 <em>//Code for displaying &lt;extensionDir>/images/myimage.png:</em>
 var imgURL = <b>chrome.extension.getURL("images/myimage.png")</b>;
 document.getElementById("someImage").src = imgURL;
 </pre>