diff --git a/README.md b/README.md
index 140ecc7..01e59d0 100644
--- a/README.md
+++ b/README.md
@@ -19,10 +19,10 @@ A Multisig HD Wallet Service, with minimum trust.
  cd bit-wallet
  
  # Create a 2-of-2 wallet (john.dat is the file where the wallet critical data will be stored, add -t for testnet)
- ./bit  create 2-2 john 
+ ./bit create 2-2 john 
   * Secret to share:
     JevjEwaaxW6gdAZjqgWcimL525DR8zQsAXf4cscWDa8u1qKTN5eFGSFssuSvT1WySu4YYLYMUPT
- ./bit  status
+ ./bit status
  
  # Use -h or BIT_HOST to setup the BWS URL .
  # Use -f or BIT_FILE to setup the wallet data file
@@ -95,8 +95,8 @@ You can safely access a wallet from different devices. Just copy the wallet file
 It is possible to export a wallet with restricted access level. The levels are:
 ```
     readonly : allows to read wallet data: balance, tx proposals 
-    readwrite: + allows to create addresses and unsigned tx prposals 
-    full     : + allows sign tx prposals 
+    readwrite: + allows to create addresses and unsigned tx proposals 
+    full     : + allows sign tx proposals 
 ```
 `readonly` will only export the Wallet's Extended PublicKeys, and only the derived private key required for signing 'GET' request (readonly) to BWS. `readwrite` will add the derived private key required for signing all other requests (as POST) so readwrite access will be possible. And `full` will export also the Extended Private Key, which is necesary for signing wallet's transactions.  `bit import` can handle any for the levels correctly.
 
@@ -108,7 +108,7 @@ bit export -o wallet.dat
 bit export -o wallet.dat --access readonly
 # readwrite access (can create addresses, propose transactions, reject TX, but does not have signing keys)
 
-# Import the wallet , with giveng access level
+# Import the wallet , with given access level
 bit import wallet.dat
 
 # Export also support QR output: