Update README.md

- Fix `failed` type for `EXECUTED_MULTISIG_TRANSACTION`
- Update default `timeout` from `5` -> `2`

README.md

@@ -32,7 +32,7 @@ If you want to integrate with the events service, you need to:
 - Endpoint need to answer with:
   - `HTTP 202` status
   - Nothing in the body.
-  - It should answer **as soon as posible**, as events service will timeout in 5 seconds, if multiple timeouts are detected **service will stop sending requests** to your endpoint. So you should receive the event, return a HTTP response and then act upon it.
+  - It should answer **as soon as posible**, as events service will timeout in 2 seconds, if multiple timeouts are detected **service will stop sending requests** to your endpoint. So you should receive the event, return a HTTP response and then act upon it.
   - Configuring HTTP Basic Auth in your endpoint is recommended so a malicious user cannot post fake events to your service.
 
 ## Events supported
@@ -62,7 +62,7 @@ Some parameters are common to every event:
   "address": "<Ethereum checksummed address>",
   "type": "EXECUTED_MULTISIG_TRANSACTION",
   "safeTxHash": "<0x-prefixed-hex-string>",
-  "failed": <bool>,
+  "failed": "true" | "false",
   "txHash": "<0x-prefixed-hex-string>",
   "chainId": "<stringified-int>"
 }