diff --git a/simple_token_bridge.md b/simple_token_bridge.md
index 8bd19a5..46e1e07 100644
--- a/simple_token_bridge.md
+++ b/simple_token_bridge.md
@@ -10,16 +10,16 @@ sequenceDiagram
 	actor O as Bridge Operator
 	O->>V: Register Trusted Auditor Key
 	U->>+B: Register Token with Audit
-	Note over B,V: Veras much as possibleify that the audit valid for the token<br>and verify the signature 
+	Note over B,V: Verify as much as possible that the audit is valid for the token<br>and verify the signature 
 	B->>+V: submitAudit(SignedAuditSummary audit, address token)
-	V-->>V: Check that the audit is from trusted auditor
+	V-->>V: Check that the audit is from a trusted auditor
 	V-->>-B: bool verified
 	Note over B,V: Check that ERC-1155 is supported
 	B->>+V: verifyStandardCheck(uint ercNum, address token)
 	V-->>V: Lookup supported ERCs on the audit
 	V-->>-B: bool supported
 	B-->-U: Registration Response
-	Note over B,V: Enable the token for bridging
+	Note over B,V: Authorize the token for bridging
 	O->>B: Activate Token
 	U->>B: Bridge Token
 	
@@ -40,4 +40,4 @@ With this the user (or token owner) can trigger the registration flow (2). There
 
 With the checks being done it is still recommended to have some manual check in place by the operator to activate a token for bridging (10). This step could be omitted if there is a strong trust in the auditor or if an ERC provides strong compatibility guarantees. 
 
-Once the token is available on the bridge the users can start using it (11). 
\ No newline at end of file
+Once the token is available on the bridge the users can start using it (11).