Update PIP-0032B.md

PIP/PIP-0032B.md

@@ -64,16 +64,16 @@ So, proposal is introduce just one new field and improve current fields workarou
     price : UInt64;                // Fixed 0 when as_AtomicSwap, >0 when as_ForSale
     account_to_pay : Cardinal;     // Not used for as_AtomicSwap, <> itself when as_ForSale
     new_publicKey : TAccountKey;
-	hashed_secret : TRawBytes;     // Not used for as_ForSale, 32 bytes length when as_AtomicSwap
+    hashed_secret : TRawBytes;     // Not used for as_ForSale, 32 bytes length when as_AtomicSwap
   end;
 ```
 
 ***Note***
 
-We can set optional value for `account_to_pay` field, that means that we can have 2 different workarounds for AtomicSwap: Private AtomicSwap and Public AtomicSwap
-- Private AtomicSwap: The new public key of the account must be fixed prior to start process, that means that only "Bob" (owner of new public key) will receive this account
-- Public AtomicSwap: The new public key of the account can be anyone, so, no need to define "who is Bob" prior to start process: Example, a quiz where the solution is HASH(SECRET) = `TAccountInfo.hashed_secret`
-
+We can set optional value for `new_publicKey` field, that means that we can have 2 different workarounds for AtomicSwap: **Private AtomicSwap** and **Public AtomicSwap**
+- **Private AtomicSwap**: The new public key of the account must be fixed prior to start process, that means that only "Bob" (owner of new public key) will receive this account
+- **Public AtomicSwap**: The new public key of the account can be anyone, so, no need to define "who is Bob" prior to start process: Example, a quiz where the solution is HASH(SECRET) = `TAccountInfo.hashed_secret`
+- Note than **Private AtomicSwap** is the default usage defined in PIP-0032A, and **Public AtomicSwap** is an extra usage where Bob has not guaranteed to be the receiver of this account
 
 ### Atomic Swap Workflow