Use console instead of sh in markdown documents when the snippet is a list of shell commands and outputs.

Signed-off-by: Silvin Lubecki <silvin.lubecki@docker.com>

Author: silvin-lubecki

BUILDING.md

@@ -30,7 +30,7 @@ end you need to have `GOPATH` set in your environment.
 
 At this point you can use `go` to checkout `docker-app` in your `GOPATH`:
 
-```sh
+```console
 go get github.com/docker/app
 ```
 
@@ -39,14 +39,14 @@ You are ready to build `docker-app` yourself!
 `docker-app` uses `make` to create a repeatable build flow. It means that you
 can run:
 
-```sh
+```console
 make
 ```
 
 This is going to build all the project binaries in the `./bin/`
 directory, run tests (unit and end-to-end).
 
-```sh
+```console
 make bin/docker-app             # builds the docker-app binary
 make bin/docker-app-darwin      # builds the docker-app binary for darwin
 make bin/docker-app-windows.exe # builds the docker-app binary for windows
@@ -89,7 +89,7 @@ capabilities without using the `Makefile` targets. The following
 examples show how to specify a test name and also how to use the flag
 directly against `go test` to run root-requiring tests.
 
-```sh
+```console
 # run the test <TEST_NAME>:
 go test -v -run "<TEST_NAME>" .
 ```

README.md

@@ -2,7 +2,6 @@
 
 An *experimental* utility to help make Compose files more reusable and sharable.
 
-
 ## The problem application packages solve
 
 Compose files do a great job of describing a set of related services. Not only are Compose files easy to write, they are generally easy to read as well. However, a couple of problems often emerge: