Stop forcing optional permission on usbDevices section

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

 <h1>Accessing Hardware Devices</h1>
 
 <p>
 This doc shows you how packaged apps can connect to USB devices
 and read from and write to a user's serial ports.
 See also the reference docs for the
 <a href="usb.html">USB API</a>
 and the
 <a href="serial.html">Serial API</a>.
 The <a href="bluetooth.html">Bluetooth API</a> is also available;
@@ skipping 46 matching lines @@
 
 <table class="simple">
   <tr>
     <th scope="col"> Parameter (type) </th>
     <th scope="col"> Description </th>
   </tr>
   <tr>
     <td>FindDeviceOptions (object)</td>
     <td>An object specifying both a <code>vendorId</code> (long) and
       <code>productId</code> (long) used to find the correct type of device on
-      the bus. Before calling this, your extension manifest must declare the
-      <code>optional_permissons</code> with a <code>usbDevices</code>
-      section containing the same <code>vendorId</code> and
-      <code>deviceId</code> combination and must have received user consent
-      via <code>chrome.permissions.request(...)</code>.
+      the bus. Your manifest must declare the<code>usbDevices</code> permission
+      section listing all the <code>vendorId</code> and
+      <code>deviceId</code> pairs your app wants to access.
     </td>
   </tr>
   <tr>
     <td>callback (function)</td>
     <td>Called when the device scan is finished.
       The callback will be executed with one parameter, an array of device objects
       with three properties: <code>handle</code>,
       <code>vendorId</code>,
       <code>productId</code>. If the optional permissions for this USB device
       were not declared in the extension manifest or the user did not consent
@@ skipping 600 matching lines @@
 
 <p>
 You can flush your serial port buffer by issuing the flush command:
 </p>
 
 <pre>
   chrome.serial.flush(connectionId, onFlush);
 </pre>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>