docs: mark console output appropriately

docs/Adding-Software-to-Homebrew.md

@@ -250,19 +250,18 @@ See the [Acceptable Casks documentation](Acceptable-Casks.md#finding-a-home-for-
 
 Hop into your tap and check to make sure your new cask is there:
 
-```bash
+```console
 $ cd "$(brew --repository)"/Library/Taps/homebrew/homebrew-cask
 $ git status
-# On branch master
+On branch master
-# Untracked files:
+Untracked files:
-#   (use "git add <file>..." to include in what will be committed)
+  (use "git add <file>..." to include in what will be committed)
-#
+        Casks/m/my-new-cask.rb
-#       Casks/my-new-cask.rb
 ```
 
 So far, so good. Now make a feature branch `my-new-cask-branch` that you’ll use in your pull request:
 
-```bash
+```console
 $ git checkout -b my-new-cask-branch
 Switched to a new branch 'my-new-cask-branch'
 ```

docs/Formula-Cookbook.md

@@ -210,7 +210,7 @@ When a version scheme of a formula fails to recognise a new version as newer it
 
 When you already have a lot of formulae installed, it's easy to miss a common dependency. You can double-check which libraries a binary links to with the `otool` command (perhaps you need to use `xcrun otool`):
 
-```sh
+```console
 $ otool -L /usr/local/bin/ldapvi
 /usr/local/bin/ldapvi:
     /usr/local/opt/openssl/lib/libssl.1.0.0.dylib (compatibility version 1.0.0, current version 1.0.0)

docs/Taps.md

@@ -9,7 +9,7 @@ but the command isn't limited to any one location.
 * `brew tap` without arguments lists all currently tapped repositories. For
   example:
 
-  ```sh
+  ```console
   $ brew tap
   homebrew/cask
   homebrew/core

docs/Tips-N'-Tricks.md

@@ -39,7 +39,7 @@ brew install --only-dependencies <formula>
 
 ## Use the interactive Homebrew shell
 
-```sh
+```console
 $ brew irb
 ==> Interactive Homebrew Shell
 Example commands available with: `brew irb --examples`