fix documentation: api_key -> apiKey

readme_bridge.md

@@ -26,7 +26,7 @@ Alternatively, you can [build](#building) the binary yourself.
 The `bridge.cfg` file must be present in a working directory (you can load another file by using `-c` parameter). Here is an [example configuration file](https://github.com/stellar/bridge-server/blob/master/bridge_example.cfg). Config file should contain following values:
 
 * `port` - server listening port
-* `api_key` - when set, all requests to bridge server must contain `api_key` parameter with a correct value, otherwise the server will respond with `503 Forbidden`
+* `apiKey` - when set, all requests to bridge server must contain `apiKey` parameter with a correct value, otherwise the server will respond with `403 Forbidden`
 * `network_passphrase` - passphrase of the network that will be used with this bridge server:
    * test network: `Test SDF Network ; September 2015`
    * public network: `Public Global Stellar Network ; September 2015`
@@ -426,7 +426,7 @@ This MAC can be used on the receiving side of the notification to verify that th
 ## Security
 
 * This server must be set up in an isolated environment (ex. AWS VPC). Please make sure your firewall is properly configured 
-and accepts connections from a trusted IPs only. You can set the `api_key` config parameter as an additional protection but it's not recommended as the solely protection. 
+and accepts connections from a trusted IPs only. You can set the `apiKey` config parameter as an additional protection but it's not recommended as the solely protection. 
 If you don't set this properly, an unauthorized person will be able to submit transactions from your accounts!
 * Make sure the `callbacks` you provide only accept connections from the bridge server IP.
 * Remember that `callbacks.receive` may be called multiple times with the same payment. Check `id` parameter and ignore