more detail for Example: Simple transfer

bsip-0040.md

@@ -191,7 +191,7 @@ Assume `asset_update_operation`. All attributes of its `options` must be filled
 
 #### Example: Simple transfer
 Assume account A and B and some unrelated key K. 
-The custom active authority should be put that transfer transaction sending funds away from A can be signed with key K as long as the receiver is B. More concrete, the authority would look like
+The custom active authority should be put such that a transfer transaction sending funds away from A can be signed with key K, as long as the receiver is B. More concrete, the authority would look like
 ```
 custom active authority = {
     valid_from: 7.7.2018 00:00
@@ -211,7 +211,17 @@ custom active authority = {
     ]
 }
 ```
-Note: This is included with the first Milestone
+Exemplatory outcomes:
+- Transfer asset X with amount Y from account A to account B, signed with Key K: Accepted
+- Transfer asset X with amount Y from account B to account A, signed with Key K: Denied
+- Transfer asset X with amount Y from account A to account C, signed with Key K: Denied
+- Transfer asset X with amount Y from account A to account B, signed with active authority of B: Denied
+- Transfer asset X with amount Y from account A to account B, signed with active authority of A: Accepted
+- Create a proposal that includes operation 'transfer asset X with amount Y from account A to account B', signed with Key K: Denied
+
+Note:
+- This is included with the first Milestone
+- Normal permission logic is not altered. Account A can still sign the a transfer from account A to account B with its active authority
 
 
 #### Example: Either or