diff --git a/README.md b/README.md
index 2ef447da6..e3e8b52e5 100644
--- a/README.md
+++ b/README.md
@@ -43,19 +43,19 @@ two steps because the mint-demo.json file contains private keys that will be
 used later in this demo.
 
 ```bash
-    $ echo 1000000000 | cargo run --release --bin solana-mint-demo > mint-demo.json
-    $ cat mint-demo.json | cargo run --release --bin solana-genesis-demo > genesis.log
+$ echo 1000000000 | cargo run --release --bin solana-mint-demo > mint-demo.json
+$ cat mint-demo.json | cargo run --release --bin solana-genesis-demo > genesis.log
 ```
 
 Before you start the server, make sure you know the IP address of the machine ou want to be the leader for the demo, and make sure that udp ports 8000-10000 are open on all the machines you wan to test with.  Now you can start the server:
 
 ```bash
-    $ cat ./multinode-demo/leader.sh
-    #!/bin/bash
-    export RUST_LOG=solana=info
-    sudo sysctl -w net.core.rmem_max=26214400
-    cat genesis.log leader.log | cargo run --release --features cuda --bin solana-testnode -- -s leader.json -l leader.json -b 8000 -d 2>&1 | tee leader-tee.log
-    $ ./multinode-demo/leader.sh
+$ cat ./multinode-demo/leader.sh
+#!/bin/bash
+export RUST_LOG=solana=info
+sudo sysctl -w net.core.rmem_max=26214400
+cat genesis.log leader.log | cargo run --release --features cuda --bin solana-testnode -- -s leader.json -l leader.json -b 8000 -d 2>&1 | tee leader-tee.log
+$ ./multinode-demo/leader.sh
 ```
 
 Wait a few seconds for the server to initialize. It will print "Ready." when it's safe
@@ -64,32 +64,31 @@ to start sending it transactions.
 Now you can start some validators:
 
 ```bash
-	$ cat ./multinode-demo/validator.sh
-	#!/bin/bash
-	rsync -v -e ssh $1:~/solana/mint-demo.json .
-	rsync -v -e ssh $1:~/solana/leader.json .
-	rsync -v -e ssh $1:~/solana/genesis.log .
-	rsync -v -e ssh $1:~/solana/leader.log .
-	rsync -v -e ssh $1:~/solana/libcuda_verify_ed25519.a .
-	export RUST_LOG=solana=info
-	sudo sysctl -w net.core.rmem_max=26214400
-	cat genesis.log leader.log | cargo run --release --features cuda --bin solana-testnode -- -l validator.json -s validator.json -v leader.json -b 9000 -d 2>&1 | tee validator-tee.log
-    $ ./multinode-demo/validator.sh ubuntu@10.0.1.51 #The leader machine
+$ cat ./multinode-demo/validator.sh
+#!/bin/bash
+rsync -v -e ssh $1:~/solana/mint-demo.json .
+rsync -v -e ssh $1:~/solana/leader.json .
+rsync -v -e ssh $1:~/solana/genesis.log .
+rsync -v -e ssh $1:~/solana/leader.log .
+rsync -v -e ssh $1:~/solana/libcuda_verify_ed25519.a .
+export RUST_LOG=solana=info
+sudo sysctl -w net.core.rmem_max=26214400
+cat genesis.log leader.log | cargo run --release --features cuda --bin solana-testnode -- -l validator.json -s validator.json -v leader.json -b 9000 -d 2>&1 | tee validator-tee.log
+$ ./multinode-demo/validator.sh ubuntu@10.0.1.51 #The leader machine
 ```
 
 
 Then, in a separate shell, let's execute some transactions. Note we pass in
 the JSON configuration file here, not the genesis ledger.
->>>>>>> logs
 
 ```bash
-    $ cat ./multinode-demo/client.sh
-    #!/bin/bash
-    export RUST_LOG=solana=info
-    rsync -v -e ssh $1:~/solana/leader.json .
-    rsync -v -e ssh $1:~/solana/mint-demo.json .
-    cat mint-demo.json | cargo run --release --bin solana-full-node -- -l leader.json -c 8100 -n 1
-    $ ./multinode-demo/client.sh ubuntu@10.0.1.51 #The leader machine
+$ cat ./multinode-demo/client.sh
+#!/bin/bash
+export RUST_LOG=solana=info
+rsync -v -e ssh $1:~/solana/leader.json .
+rsync -v -e ssh $1:~/solana/mint-demo.json .
+cat mint-demo.json | cargo run --release --bin solana-full-node -- -l leader.json -c 8100 -n 1
+$ ./multinode-demo/client.sh ubuntu@10.0.1.51 #The leader machine
 ```
 
 Try starting a more validators and reruning the client demo!
@@ -127,7 +126,7 @@ Testing
 Run the test suite:
 
 ```bash
-cargo test
+$ cargo test
 ```
 
 Debugging