Update README.md

README.md

@@ -215,8 +215,9 @@ If your mocker is `disabled`, it will not interfere with actual network calls. I
 it will need to find scenarios to mock the HTTP calls. Dynamic mocks imply that you have to 
 provide the response for each request programmatically, which allows you to define stateful 
 responses (identical calls could lead to different answers based on what the user did in between 
-these calls). The response can be provided as a `ResponseDescriptor` by implementing the 
-`RequestCallback` interface, or you can simply provide a lambda function to do the computation. 
+these calls, or on any other external parameter you want to use: time, location...). The response 
+can be provided as a `ResponseDescriptor` by implementing the `RequestCallback` interface, or you 
+can simply provide a lambda function to do the computation. 
 
 *NB: If you use dynamic mocks, the `bodyFile` attribute of your `ResponseDescriptor` is not needed (it 
 will be ignored). Its only use is for static scenarios that could save the response body in a separate