update docs

Author: ElliotFriedman

Diff for: docs/adr-002-ebrelayer-eth-subscribe.md

@@ -12,7 +12,7 @@
 In this ADR, we discuss the solution for ebrelayer how to subscribe the events from Ethereum and process these events.
 ### Summary
 
-For ebrelaye, it just need subscribe the events from CosmosBridge smart contract, both LogLock event and LogBurn event, then process both events and send transaction to Sifchain. Basically, there are two problems.
+For ebrelayer, it just needs to subscribe to the events from the BridgeBank smart contract, both LogLock event and LogBurn event, then process both events and send transaction to Sifchain. Basically, there are two problems.
 1. The block produced in Ethereum maybe be reorganized, most of system opt to confirm the finalization of block after 6 blocks. So it is better to process the event with some dalay. For the events once we receive from subscription, we store them in the buffer and wait for more blocks produced.
 2. How to store the events, there are two options. First one is store them in memory, but events will be lost if ebrelayer restarted. Second solution is store in local db, message queue like Kafka, but will increase the complexity of ebrelayer's deployment.