doc: clean up blank lines in getting started docs

code blocks had unnecessary blank lines

Change-Id: I7fae271db0e7e975d717ccf7b0f7b686251405c0
Signed-off-by: David B. Kinder <[email protected]>

doc/getting_started/getting_started.rst

@@ -69,7 +69,6 @@ To build an example application follow these steps:
    .. code-block:: console
 
       $ export ZEPHYR_GCC_VARIANT=zephyr
-
       $ export ZEPHYR_SDK_INSTALL_DIR=<sdk installation directory>
 
 #. Navigate to the main project directory:
@@ -90,7 +89,6 @@ To build an example application follow these steps:
    .. code-block:: console
 
       $ cd $ZEPHYR_BASE/samples/hello_world
-
       $ make
 
 The above invocation of make will build the :ref:`hello_world` sample application
@@ -138,7 +136,6 @@ follow the steps below to build with any custom or 3rd party cross-compilers:
    .. code-block:: console
 
       $ unset ZEPHYR_GCC_VARIANT
-
       $ unset ZEPHYR_SDK_INSTALL_DIR
 
 #. We will use the `GCC ARM Embedded`_ compiler for this example, download the
@@ -165,11 +162,8 @@ follow the steps below to build with any custom or 3rd party cross-compilers:
    .. code-block:: console
 
       $ export GCCARMEMB_TOOLCHAIN_PATH="~/gcc-arm-none-eabi-5_3-2016q1/"
-
       $ export ZEPHYR_GCC_VARIANT=gccarmemb
-
       $ cd $ZEPHYR_BASE/samples/hello_world
-
       $ make CROSS_COMPILE=~/gcc-arm-none-eabi-5_3-2016q1/bin/arm-none-eabi- BOARD=arduino_due
 
 The above will build the sample using the toolchain downloaded from
@@ -180,15 +174,10 @@ Alternatively, you can use the existing support for GCC ARM Embedded:
    .. code-block:: console
 
       $ export GCCARMEMB_TOOLCHAIN_PATH="~/gcc-arm-none-eabi-5_3-2016q1/"
-
       $ export ZEPHYR_GCC_VARIANT=gccarmemb
-
       $ cd zephyr-project
-
       $ source zephyr-env.sh
-
       $ cd $ZEPHYR_BASE/samples/hello_world
-
       $ make BOARD=arduino_due
 
 Running a Sample Application in QEMU

doc/getting_started/installation_linux.rst

@@ -112,7 +112,6 @@ Follow these steps to install the SDK on your Linux host system.
    .. code-block:: console
 
       $ chmod +x zephyr-sdk-<version>-setup.run
-
       $ ./zephyr-sdk-<version>-setup.run
 
    There is no need for `sudo` if the SDK is installed in the current
@@ -129,7 +128,6 @@ Follow these steps to install the SDK on your Linux host system.
    .. code-block:: console
 
       $ export ZEPHYR_GCC_VARIANT=zephyr
-
       $ export ZEPHYR_SDK_INSTALL_DIR=<sdk installation directory>
 
   To use the same toolchain in new sessions in the future you can set the

doc/getting_started/installation_mac.rst

@@ -56,15 +56,9 @@ the brew command line.
 .. code-block:: console
 
    $ brew install gettext qemu help2man mpfr gmp coreutils wget python3 dfu-util
-
    $ brew tap homebrew/dupes
-
    $ brew install grep --with-default-names
-
    $ pip3 install ply
-
-.. code-block:: console
-
    $ brew install crosstool-ng
 
 Alternatively you can install the latest version of :program:`crosstool-ng`
@@ -73,17 +67,11 @@ latest version usually supports the latest released compilers.
 
 .. code-block:: console
 
-   $ wget
-   http://crosstool-ng.org/download/crosstool-ng/crosstool-ng-1.22.0.tar.bz2
-
+   $ wget http://crosstool-ng.org/download/crosstool-ng/crosstool-ng-1.22.0.tar.bz2
    $ tar xvf crosstool-ng-1.22.0.tar.bz2
-
    $ cd crosstool-ng/
-
    $ ./configure
-
    $ make
-
    $ make install
 
 .. _setting_up_mac_toolchain:
@@ -117,9 +105,7 @@ When mounted, the file system of the image will be available under
 .. code-block:: console
 
    $ cd /Volumes/CrossToolNG
-
    $ mkdir build
-
    $ cd build
 
 Setting the Toolchain Options
@@ -185,7 +171,6 @@ and use the target location where the toolchain was installed, type:
 .. code-block:: console
 
    $ export ZEPHYR_GCC_VARIANT=xtools
-
    $ export XTOOLS_TOOLCHAIN_PATH=/Volumes/CrossToolNG/x-tools