README.md in nexaas-throttle-1.0.0 vs README.md in nexaas-throttle-2.0.0

@@ -92,18 +92,20 @@
       </pre>
     </td>
   </tr>
   <tr>
     <td><code>ignored_user_agents</code></td>
-    <td>Ignores how many User-Agent the application wants, in case of other applications from the same organization.</td>
+    <td>An array of User Agents that should be ignored by the throttler. Values are regexes that will be matched against the request User-Agent</td>
     <td><code>nil</code></td>
   </tr>
 </table>
 
 ### Request Identification
 
 `Nexaas::Throttle` doesn't know how to identify a consumer. Some applications might rely on request IP, others on an API TOKEN. You must provide a way of getting an unique token
 that identify a request consumer.
+
+If there is no token, the request will go through and won't be accounted for.
 
 `Nexaas::Throttle` do this by providing a configuration `request_identifier`, a class where your application would keep the logic that identifies a consumer. This class must have the following
 interface:
 
 ```ruby