docs: unify code and shell cmd blocks

docs/fuzz.md

@@ -6,24 +6,24 @@ The `fuzz` package is organized into subpackages which are named after the `lnd`
 This section will cover setup and installation of `go-fuzz` and fuzzing binaries.
 
 * First, we must get `go-fuzz`.
-```
-$ go get -u github.com/dvyukov/go-fuzz/...
+```shell
+⛰  go get -u github.com/dvyukov/go-fuzz/...
 ```
 * The following is a command to build all fuzzing harnesses for a specific package.
-```
-$ cd fuzz/<package>
-$ find * -maxdepth 1 -regex '[A-Za-z0-9\-_.]'* -not -name fuzz_utils.go | sed 's/\.go$//1' | xargs -I % sh -c 'go-fuzz-build -func Fuzz_% -o <package>-%-fuzz.zip github.com/lightningnetwork/lnd/fuzz/<package>'
+```shell
+⛰  cd fuzz/<package>
+⛰  find * -maxdepth 1 -regex '[A-Za-z0-9\-_.]'* -not -name fuzz_utils.go | sed 's/\.go$//1' | xargs -I % sh -c 'go-fuzz-build -func Fuzz_% -o <package>-%-fuzz.zip github.com/lightningnetwork/lnd/fuzz/<package>'
 ```
 
 * This may take a while since this will create zip files associated with each fuzzing target.
 
 * Now, run `go-fuzz` with `workdir` set as below!
-```
-$ go-fuzz -bin=<.zip archive here> -workdir=<harness> -procs=<num workers>
+```shell
+⛰  go-fuzz -bin=<.zip archive here> -workdir=<harness> -procs=<num workers>
 ```
 
 `go-fuzz` will print out log lines every couple of seconds. Example output:
-```
+```text
 2017/09/19 17:44:23 workers: 8, corpus: 23 (3s ago), crashers: 1, restarts: 1/748, execs: 400690 (16694/sec), cover: 394, uptime: 24s
 ```
 Corpus is the number of items in the corpus. `go-fuzz` may add valid inputs to
@@ -41,7 +41,7 @@ Fuzzing generally works best with a corpus that is of minimal size while achievi
 
 ### Test Harness ###
 If you take a look at the test harnesses that are used, you will see that they all consist of one function: 
-```
+```go
 func Fuzz(data []byte) int
 ```
 If: