Changes to follow the codesite L&F....

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

 <div id="pageData-title" class="pageData">Message Passing</div>
 <div id="pageData-showTOC" class="pageData">true</div>
 
 <p>
 Since content scripts run in the context of a web page and not the extension,
 they often need some way of communicating with the rest of the extension. For
 example, an RSS reader extension might use content scripts to detect the
 presence of an RSS feed on a page, then notify the background page in order to
 display a page action icon for that page.
 
@@ skipping 66 matching lines @@
     else
       sendResponse({}); // snub them.
   });
 </pre>
 
 
 <h2 id="connect">Long-lived connections</h2>
 <p>
 Sometimes it's useful to have a conversation that lasts longer than a single
 request and response. In this case, you can open a long-lived channel from
-your content script to an extension page, or vice versa, using 
+your content script to an extension page, or vice versa, using
 <a href="extension.html#method-connect">chrome.extension.connect()</a>
 or
 <a href="tabs.html#method-connect">chrome.tabs.connect()</a> respectively. The
 channel can optionally have a name, allowing you to distinguish between
 different types of connections.
 
 <p>
 One use case might be an automatic form fill extension. The content script
 could open a channel to the extension page for a particular login, and send a
 message to the extension for each input element on the page to request the
@@ skipping 50 matching lines @@
       port.postMessage({question: "I don't get it."});
   });
 });
 </pre>
 
 <p>
 You may want to find out when a connection is closed, for example if you are
 maintaining separate state for each open port. For this you can listen to the
 <a href="extension.html#type-Port">Port.onDisconnect</a>
 event. This event is fired either when the other side of the channel manually
-calls 
+calls
 <a href="extension.html#type-Port">Port.disconnect()</a>, or when the page
 containing the port is unloaded (for example if the tab is navigated).
 onDisconnect is guaranteed to be fired only once for any given port.
 
 
 <h2 id="external">Cross-extension messaging</h2>
 <p>
 In addition to sending messages between different components in your
 extension, you can use the messaging API to communicate with other extensions.
 This lets you expose a public API that other extensions can take advantage of.
@@ skipping 39 matching lines @@
 chrome.extension.sendRequest(laserExtensionId, {getTargetData: true},
   function(response) {
     if (targetInRange(response.targetData))
       chrome.extension.sendRequest(laserExtensionId, {activateLasers: true});
   });
 
 // Start a long-running conversation:
 var port = chrome.extension.connectExternal(laserExtensionId);
 port.postMessage(...);
 </pre>