use-cases.md

@@ -55,7 +55,7 @@ A Exchange user sends cryptocurrency and wants to receive Euro.
 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)   
+ i.	If it is SEPA transfer, then it is sent to DIS  - see [diagram flow](use cases/uc-1)   
 ii.	If it is non-SEPA transfer, then it is rejected.
 
 
@@ -68,7 +68,7 @@ An exchange user sends Euro from his banking account ( not in Dan's bank) and wa
 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).
+5.	DIS sends a transfer to CBS see [diagram flow](use cases/uc-2).
 6.	CBS registers transaction in its database.
 7.	EURO-client transaction scanner checks via CBS if there are any new incoming transactions on Dan’s account (same as for any crypto/blockchain).
 8.	If there are any, EURO-client transaction scanner fetches those transactions (served by CBS from its database) and processes them (same as for any crypto/blockchain).