use-cases.md

@@ -49,14 +49,14 @@ Bank of Lithuania system managing message exchange between various bank and exte
 **UC 1** 
  
 A Exchange user sends cryptocurrency and wants to receive Euro.
-1.    An exchange user initiates trade using the Exchange interface.
-2.    Exchange generates order id – order id includes an encrypted receiver IBAN account.   
-3.	A user sends crypto to Dan’s account using generated order id as memo or address.
+1.    An exchange user initiates trade using the Exchange interface, as output address enters IBAN and BIC.
+2.    Exchange generates standard input adress suitable for given input blockchain.
+3.    A user sends crypto to Dan’s account using generated input address as memo or address.
 4.	A transaction is processed with a standard path in the Exchange:   
 a.	 The transaction scanner in the source blockchain recognizes an operation and takes an appropriate action (as now) – sends it to CBS via EURO-client.    
 b.	CBS recognizes whether it is an SEPA transfer  or non-SEPA transfer:   
  i.	If it is SEPA transfer, then it is sent to DIS  - see [diagram flow](use cases/uc-2)   
-ii	If it is non-SEPA transfer, then it is rejected.
+ii.	If it is non-SEPA transfer, then it is rejected.
 
 
 **II. Sending EURO and receiving cryptocurrency**  
@@ -65,8 +65,8 @@ ii	If it is non-SEPA transfer, then it is rejected.
 **UC 2**   
 An exchange user sends Euro from his banking account ( not in Dan's bank) and wants to receive cryptocurrency.    
 1.    An exchange user initiates trade using Exchange interface.
-2.	Exchange generates order id.
-3.	A user sends EURO to Dan’s account using generated order id as transfer title via his internet banking.
+2.    Exchange generates unique input_address.
+3.    A user sends EURO to Dan’s account using generated input_address as transfer title via his internet banking.
 4.	DIS registers a transaction. 
 5.	DIS sends a transfer to CBS see [diagram flow](use cases/uc-4).
 6.	CBS registers transaction in its database.