[readme] typos and cleanup including whitespaces.

7 files changed, 392 insertions, 382 deletions

diff --git a/docs/README.android b/docs/README.android
index a9c4c679f1..d672522e87 100644
--- a/docs/README.android
+++ b/docs/README.android
@@ -13,7 +13,7 @@ TOC
 1. Introduction
 -----------------------------------------------------------------------------
 
-We currently recommend Ubuntu "Precise Pangolin" (12.04) 64Bit. This is what our continuous 
+We currently recommend Ubuntu "Precise Pangolin" (12.04) 64Bit. This is what our continuous
 integration system "jenkins" is using.
 Additionally, building from OSX Snow Leopard or Mavericks (others on your own risk ;) ) is working (see 3.1).
 
@@ -25,20 +25,20 @@ character itself should NOT be typed as part of the command.
 -----------------------------------------------------------------------------
 2. Installing the required Ubuntu packages
 -----------------------------------------------------------------------------
-These are the minimum packages necessary for building Kodi. Non-Ubuntu
-users will need to get the equivalents.
+These are the minimum packages necessary for building Kodi.
+Non-Ubuntu users will need to get the equivalents.
 
-   # sudo apt-get install build-essential default-jdk git curl autoconf \
-       unzip zip zlib1g-dev gawk gperf cmake
+    $ sudo apt-get install build-essential default-jdk git curl autoconf \
+      unzip zip zlib1g-dev gawk gperf cmake
 
 If you run a 64bit operating system you will also need to get ia32-libs
 
- ubuntu >= 14.04:
-   # sudo apt-get install lib32stdc++6 lib32z1 lib32z1-dev
+Ubuntu >= 14.04:
+    $ sudo apt-get install lib32stdc++6 lib32z1 lib32z1-dev
+
+Older versions:
+    $ sudo apt-get install ia32-libs
 
- older versions:
-   # sudo apt-get install ia32-libs
-   
 The following versions are used on our continuous integration system "jenkins". Other (newer)
 versions might work as well.
 
@@ -53,30 +53,32 @@ JRE: openjre-6-jre (java version "1.6.0_27")
 To develop Kodi for Android the Android SDK and NDK are required.
 
 --------------------------------------------------------------------
-3.1. Prerequesites when compiling on Mac OSX
+3.1. Prerequisites when compiling on Mac OSX
 --------------------------------------------------------------------
 
 a. When building on Mac OSX you should download the java version from here: http://support.apple.com/kb/DL1572
 Or ensure otherwise that you are using java 1.6 (java -version tells you the version).
 b. The compilation for android needs a case sensitive filesystem. The
-   filesystem used on normal osx installations is case insensitive. So you 
+   filesystem used on normal OSX installations is case insensitive. So you
    need to generate a writeable hdd image and format it with hfs+ (case sensitive).
    The size should be 20GB.
 c. Generate a writable dmg with the following command:
-   # hdiutil create -type UDIF -fs 'Case-sensitive Journaled HFS+' -size 20g -volname android-dev ~/android-dev.dmg
+    $ hdiutil create -type UDIF -fs 'Case-sensitive Journaled HFS+' -size 20g -volname android-dev ~/android-dev.dmg
+
 d. Whenever you want to compile/develop you need to mount it:
-   # open ~/android-dev.dmg
+    $ open ~/android-dev.dmg
+
 e. Your workspace can be accessed in /Volumes/android-dev/ then
 f. Once you have your hdd image with case sensitive hfs+ file system do all steps
-   below inside of this filesystem. In the end you need to adapt all pathes in this
+   below inside of this filesystem. In the end you need to adapt all paths in this
    document so that they match your local environment. As an example here is a
-   configure line from step 5.1 which demonstrates possible pathes. In this 
+   configure line from step 5.1 which demonstrates possible paths. In this
    example the hdd image is mounted on /Volumes/android-dev.
-   ./configure --with-tarballs=/Users/Shared/xbmc-depends/tarballs --host=arm-linux-androideabi \
-               --with-sdk-path=/Volumes/android-dev/android/android-sdk-macosx \
-               --with-ndk=/Volumes/android-dev/android/android-ndk-r10d \
-               --with-toolchain=/Volumes/android-dev/android/android-toolchain-arm/android-17 \
-               --prefix=/Volumes/android-dev/android/xbmc-depends
+    $ ./configure --with-tarballs=/Users/Shared/xbmc-depends/tarballs --host=arm-linux-androideabi \
+                  --with-sdk-path=/Volumes/android-dev/android/android-sdk-macosx \
+                  --with-ndk=/Volumes/android-dev/android/android-ndk-r10d \
+                  --with-toolchain=/Volumes/android-dev/android/android-toolchain-arm/android-17 \
+                  --prefix=/Volumes/android-dev/android/xbmc-depends
 
 --------------------------------------------------------------------
 3.2. Getting the Android SDK and NDK
@@ -84,15 +86,15 @@ f. Once you have your hdd image with case sensitive hfs+ file system do all step
 
 To get the Android SDK, go to http://developer.android.com/sdk and
 download the latest version for your operating system. The NDK
-can be downloaded from http://developer.android.com/tools/sdk/ndk/ 
+can be downloaded from http://developer.android.com/tools/sdk/ndk/
 
 [NOTICE] Compiling Kodi for Android requires Android NDK
-         Revision at least 10d. For the SDK just use the latest available. 
+         Revision at least 10d. For the SDK just use the latest available.
          It will work.
 
 After downloading the SDK and NDK extract the files contained in the
 archives to your harddisk. For our example we are extracting in the following
-directories (this matches the example from tools/depends/README aswell):
+directories (this matches the example from tools/depends/README as well):
 
 NDK (referenced as <android-ndk> from now on):
 /opt/android-ndk-r10d
@@ -116,9 +118,9 @@ Android SDK will not work. (see point 2.)
 After having extracted the Android SDK to <android-sdk> you need to
 install some android packages using the Android SDK Manager:
 
-   # cd <android-sdk>/tools
-   # ./android update sdk -u -t platform,platform-tool
-   # ./android update sdk -u -t build-tools-20.0.0
+    $ cd <android-sdk>/tools
+    $ ./android update sdk -u -t platform,platform-tool
+    $ ./android update sdk -u -t build-tools-20.0.0
 --------------------------------------------------------------------
 3.4. Setup the Android toolchain
 --------------------------------------------------------------------
@@ -129,27 +131,27 @@ the Android NDK which you earlier extracted to <android-ndk>. The
 following commands will create a toolchain suitable for the most
 common scenario.
 The --install-dir option (and therefore the <android-toolchain-arm>/<android-toolchain-x86> value)
-specifies where the resulting toolchain should be installed (your choice). 
+specifies where the resulting toolchain should be installed (your choice).
 
 [NOTICE] Kodi uses the android API Version 17 and gcc version 4.8!
 
 Building for arm architecture:
 
-   # cd <android-ndk>
-   # ls platforms
-   # cd build/tools
-   # ./make-standalone-toolchain.sh --ndk-dir=../../ \
-     --install-dir=<android-toolchain-arm>/android-17 --platform=android-17 \
-     --toolchain=arm-linux-androideabi-4.8
-     
+    $ cd <android-ndk>
+    $ ls platforms
+    $ cd build/tools
+    $ ./make-standalone-toolchain.sh --ndk-dir=../../ \
+      --install-dir=<android-toolchain-arm>/android-17 --platform=android-17 \
+      --toolchain=arm-linux-androideabi-4.8
+
 Building for x86 architecture:
 
-   # cd <android-ndk>
-   # ls platforms
-   # cd build/tools
-   # ./make-standalone-toolchain.sh --ndk-dir=../../ \
-     --install-dir=<android-toolchain-x86>/android-17 --platform=android-17 \
-     --toolchain=x86-4.8 --arch=x86 --system=linux-x86_64
+    $ cd <android-ndk>
+    $ ls platforms
+    $ cd build/tools
+    $ ./make-standalone-toolchain.sh --ndk-dir=../../ \
+      --install-dir=<android-toolchain-x86>/android-17 --platform=android-17 \
+      --toolchain=x86-4.8 --arch=x86 --system=linux-x86_64
 
 Make sure to pick a toolchain for your desired architecture. If an error about
 the used system is shown - please add proper --system parameter as mentioned
@@ -163,7 +165,7 @@ in the error message.
   self-signed debug key. If the result is a cryptic error, it
   probably just means a debug key already existed, no cause for alarm.
 
-  # keytool -genkey -keystore ~/.android/debug.keystore -v -alias \
+    $ keytool -genkey -keystore ~/.android/debug.keystore -v -alias \
       androiddebugkey -dname "CN=Android Debug,O=Android,C=US" -keypass \
       android -storepass android -keyalg RSA -keysize 2048 -validity 10000
 
@@ -171,10 +173,10 @@ in the error message.
 4. Getting the source code
 -----------------------------------------------------------------------------
 
-   # cd $HOME
-   # git clone git://github.com/xbmc/xbmc.git kodi-android
-   # cd kodi-android
-   # git submodule update --init addons/skin.re-touched
+    $ cd $HOME
+    $ git clone git://github.com/xbmc/xbmc.git kodi-android
+    $ cd kodi-android
+    $ git submodule update --init addons/skin.re-touched
 
 -----------------------------------------------------------------------------
 5. How to compile
@@ -188,42 +190,42 @@ on with the Android toolchain and creating an Android Application Package
 5.1. Building dependencies
 --------------------------------------------------------------------
 
-   # cd $HOME/kodi-android/tools/depends
-   # ./bootstrap
-   # ./configure --help
+    $ cd $HOME/kodi-android/tools/depends
+    $ ./bootstrap
+    $ ./configure --help
 
    Run configure with the correct settings for you local configuration.
    See tools/depends/README for examples.
 
    Anyone working on the dependencies themselves will want to set the
    environment variables specified in ~/.bashrc or similar, to avoid
-   having to input these with each configure. 
+   having to input these with each configure.
 
-   # make -j <jobs>
-   # make -j <jobs> -C target/binary-addons
+    $ make -j <jobs>
+    $ make -j <jobs> -C target/binary-addons
 
    NOTE: if you only want to build specific addons you can specify like this:
-   # make -C target/binary-addons ADDONS="pvr.hts pvr.dvblink"
+    $ make -C target/binary-addons ADDONS="pvr.hts pvr.dvblink"
 
    This build was designed to be massively parallel. Don't be afraid to
    give it a 'make -j20' or so.
 
    Verify that all deps built correctly (it will tell you so) before
    continuing. You will get crazy build errors otherwise. If in doubt
-   run another 'make' (single threaded) until the message 
+   run another 'make' (single threaded) until the message
    "Dependencies built successfully." appears. If the single make
-   fails keep cleaning the dependend library in charge by issueing
-   make -C target/<name_of_failed_lib> distclean. Then try make again.
+   fails keep cleaning the dependes library in charge by issuing
+    $ make -C target/<name_of_failed_lib> distclean. Then try make again.
    Rinse and repeat until you are really done and all libs are built.
 
 --------------------------------------------------------------------
 5.2. Building Kodi
 --------------------------------------------------------------------
 
-   # cd $HOME/kodi-android
-   # make -C tools/depends/target/xbmc
-   # make
-   # make apk
+    $ cd $HOME/kodi-android
+    $ make -C tools/depends/target/xbmc
+    $ make
+    $ make apk
 
    After the first build (assuming bootstrap and configure are successful),
    subsequent builds can be run with a simple 'make' and 'make apk'.
@@ -247,10 +249,10 @@ device's Android settings:
   - Applications
     [X] Unknown sources
 
-   # cd $HOME/kodi-android/tools/android/packaging
-   # adb devices
-   # adb -s <device-id> install -r images/xbmcapp-debug.apk
-      
+    $ cd $HOME/kodi-android/tools/android/packaging
+    $ adb devices
+    $ adb -s <device-id> install -r images/xbmcapp-debug.apk
+
 The <device-id> can be retrieved from the list returned by the
 "adb devices" command and is the first value in the row representing
 your device.
@@ -278,7 +280,7 @@ when using the emulator):
 To access the log output of your Android system run (the -s parameter
 and the <device-id> may not be needed when using the Android emulator)
 
-  # adb -s <device-id> logcat
+    $ adb -s <device-id> logcat
 
 
 --------------------------------------------------------------------
@@ -290,7 +292,7 @@ using gdb directly, you will need to use ndk-gdb which wraps it. Do NOT trust
 the -p/--project switches, as they do not work. Instead you will need
 to cd to tools/android/packaging/xbmc and execute it from there.
 
-  # ndk-gdb --start --delay=0
+    $ ndk-gdb --start --delay=0
 
 This will open the installed version of Kodi and break. The warnings can be
 ignored as we have setup the appropriate paths already.
@@ -350,18 +352,16 @@ Below are a few helpful commands when building/debugging. These assume that pwd
 is 'tools/android/packaging' and that the proper sdk/ndk paths are set.
 
 -Install a new build over the existing one
-  # adb -e install -r images/xbmcapp-debug.apk
+    $ adb -e install -r images/xbmcapp-debug.apk
 
 -Launch Kodi on the emulator without the GUI
-  # adb shell am start -a android.intent.action.MAIN -n org.xbmc.xbmc/android.app.NativeActivity
+    $ adb shell am start -a android.intent.action.MAIN -n org.xbmc.xbmc/android.app.NativeActivity
 
 -Kill a misbehaving Kodi
-  # adb shell ps | grep org.xbmc | awk '{print $2}' | xargs adb shell kill
+    $ adb shell ps | grep org.xbmc | awk '{print $2}' | xargs adb shell kill
 
 -Filter logcat messages by a specific tag (e.g. "XBMC")
-  # adb logcat -s XBMC:V
-  
--Enable CheckJNI (BEFORE starting the application)
-  # adb shell setprop debug.checkjni 1
-  
+    $ adb logcat -s XBMC:V
 
+-Enable CheckJNI (BEFORE starting the application)
+    $ adb shell setprop debug.checkjni 1
diff --git a/docs/README.armel b/docs/README.armel
index 1ad32fe908..81fb933464 100644
--- a/docs/README.armel
+++ b/docs/README.armel
@@ -40,115 +40,115 @@ All lines that are prefixed with the '#' character are commands that need to be
 
 First, you need scratch box, along with some other packages.
 The easiest way is to do the following automatic installation.
-If you dont succeed, or want to do it manually, follow the next step instead.
-
-	-----------------------------------------------------------------------------
-	2.1 Automatic Installation:
-	-----------------------------------------------------------------------------
-
-		$ sudo gedit /etc/apt/sources.list
-		
-	Add this to the end of the file, then save and exit gedit:
-		deb http://scratchbox.org/debian stable main
-		deb http://scratchbox.org/debian legacy main
-		
-	Now enter the following command:
-		$ sudo apt-get install scratchbox-core scratchbox-libs scratchbox-devkit-cputransp scratchbox-devkit-git scratchbox-devkit-mtd scratchbox-devkit-perl scratchbox-devkit-doctools scratchbox-toolchain-arm-linux-cs2007q3-51sb3 scratchbox-toolchain-host-gcc scratchbox-devkit-debian
-
-	-----------------------------------------------------------------------------
-	2.2 Manual Installation:
-	-----------------------------------------------------------------------------
-
-	Go to the following website:
-		http://www.scratchbox.org/download/files/sbox-releases/stable/tarball/
-	and download the following files (Unless specified, choose latest version):
-	- core
-	- libs
-	- cputransp
-	- doctools
-	- git
-	- mtd
-	- perl
-	- toolchain (cs2007q3-51sb3)
-	- host-gcc
-	- debian
-
-	To install
-		$ cd /
-		$ sudo tar xvf /<location of files>/scratchbox-core.tar.gz
-
-	Repeat for all the downloaded files.
-
-	-----------------------------------------------------------------------------
-	2.3 Installation Continued for both Automatic and Manual Methods:
-	-----------------------------------------------------------------------------
-
-	Now, a few changes needs to me made in order for it to work correctly:
-		$ sudo gedit /etc/sysctl.conf
-		
-	Change/Add these variables:
+If you don't succeed, or want to do it manually, follow the next step instead.
+
+-----------------------------------------------------------------------------
+2.1 Automatic Installation:
+-----------------------------------------------------------------------------
+
+    $ sudo gedit /etc/apt/sources.list
+
+Add this to the end of the file, then save and exit gedit:
+    deb http://scratchbox.org/debian stable main
+    deb http://scratchbox.org/debian legacy main
+
+Now enter the following command:
+    $ sudo apt-get install scratchbox-core scratchbox-libs scratchbox-devkit-cputransp scratchbox-devkit-git scratchbox-devkit-mtd scratchbox-devkit-perl scratchbox-devkit-doctools scratchbox-toolchain-arm-linux-cs2007q3-51sb3 scratchbox-toolchain-host-gcc scratchbox-devkit-debian
+
+-----------------------------------------------------------------------------
+2.2 Manual Installation:
+-----------------------------------------------------------------------------
+
+Go to the following website:
+http://www.scratchbox.org/download/files/sbox-releases/stable/tarball/
+and download the following files (Unless specified, choose latest version):
+  - core
+  - libs
+  - cputransp
+  - doctools
+  - git
+  - mtd
+  - perl
+  - toolchain (cs2007q3-51sb3)
+  - host-gcc
+  - debian
+
+To install
+    $ cd /
+    $ sudo tar xvf /<location of files>/scratchbox-core.tar.gz
+
+Repeat for all the downloaded files.
+
+-----------------------------------------------------------------------------
+2.3 Installation Continued for both Automatic and Manual Methods:
+-----------------------------------------------------------------------------
+
+Now, a few changes needs to me made in order for it to work correctly:
+    $ sudo gedit /etc/sysctl.conf
+
+Change/Add these variables:
 		vm.mmap_min_addr = 4096
-        vm.vdso_enabled = 0
-	Save and Close.
-
-	Add yourself to scratchbox:
-		$ sb-adduser <username>
-		
-	Make sure it worked by doing the following command, and see if sbox is listed.
-		$ groups
-
-	If it isnt listed, restart and try again. If it still isnt listed, then do the following:
-		$ usermod -a -G sbox <username>
-		
-	It should now list (possibly after another logout)
-	Now you have access to scratchbox.
-	
-	-----------------------------------------------------------------------------
-	2.4 Setup Scratchbox:
-	-----------------------------------------------------------------------------
-	
-	Before setting up your target, you need a rootstrap. Obtain the latest rootstrap from:
-		http://linux.onarm.com/download/images/generic-X/
-	You want to download the file 'beagleboard-<date>-rootstrap.tar.gz'.
-
-	Do this every time you want to access scratchbox:
-		$ /scratchbox/login
-	
-	Time to setup your target:
-		> sb-menu
-	
-	A GUI will appear for the setup procedure.
-	    - Choose Setup
-	    - Create a NEW target, give it any name
-	    - Select the compiler you downloaded (arm-linux-cs2007q3-51sb3)
-	    - Select all development kits listed by highlighting each one and pressing enter, then Done and enter
-	    - Select CPU transparency (qemu-arm-cvs-m)
-	    - Yes to rootstrap. Locate the previously downloaded rootstrap to install.
-	    - Yes to install files
-	    - Only select DEVKIT and ETC. Remove all other files in list, then continue
-	    - And finally Yes to selecting target.
-
-	Now scratchbox is setup
-
-	
+    vm.vdso_enabled = 0
+Save and Close.
+
+Add yourself to scratchbox:
+    $ sb-adduser <username>
+
+Make sure it worked by doing the following command, and see if sbox is listed.
+    $ groups
+
+If it isn't listed, restart and try again. If it still isnt listed, then do the following:
+    $ usermod -a -G sbox <username>
+
+It should now list (possibly after another logout)
+Now you have access to scratchbox.
+
+-----------------------------------------------------------------------------
+2.4 Setup Scratchbox:
+-----------------------------------------------------------------------------
+
+Before setting up your target, you need a rootstrap. Obtain the latest rootstrap from:
+http://linux.onarm.com/download/images/generic-X/
+You want to download the file 'beagleboard-<date>-rootstrap.tar.gz'.
+
+Do this every time you want to access scratchbox:
+    $ /scratchbox/login
+
+Time to setup your target:
+    $ sb-menu
+
+A GUI will appear for the setup procedure.
+  - Choose Setup
+  - Create a NEW target, give it any name
+  - Select the compiler you downloaded (arm-linux-cs2007q3-51sb3)
+  - Select all development kits listed by highlighting each one and pressing enter, then Done and enter
+  - Select CPU transparency (qemu-arm-cvs-m)
+  - Yes to rootstrap. Locate the previously downloaded rootstrap to install.
+  - Yes to install files
+  - Only select DEVKIT and ETC. Remove all other files in list, then continue
+  - And finally Yes to selecting target.
+
+Now scratchbox is setup
+
+
 -----------------------------------------------------------------------------
 3. Getting the source code
 -----------------------------------------------------------------------------
 
-   $ sudo apt-get install git-core
-   $ cd /scratchbox/users/<username>/home/<username>/
-   $ git clone git://github.com/xbmc/xbmc.git
+    $ sudo apt-get install git-core
+    $ cd /scratchbox/users/<username>/home/<username>/
+    $ git clone git://github.com/xbmc/xbmc.git
+
 
-   
 -----------------------------------------------------------------------------
 4. Installing the required ARMEL packages
 -----------------------------------------------------------------------------
 
 There is a simple shell script that downloads a list of packages that are required and installs them into scratchbox.
 
-  > cd tools/arm/arm-scripts/
-  > ./install-pkgs.sh
-  
+    $ cd tools/arm/arm-scripts/
+    $ ./install-pkgs.sh
+
 Please check the output files for any possible errors that may have occured.
 
 Note. You will need the headers and shared object files for EGL and GLESv2 to continue.
@@ -162,6 +162,7 @@ In order to continue, you will need the SGX SDK from TI's website.
 Once you have installed said SDK on a standard Linux machine, copy the neccessary .h and .so files to the appropriate directories in scratchbox:
 e.g /scratchbox/users/<username>/targets/<target_name>/usr/include/EGL/egl.h
 These files will also need to be transferred over to the board eventually.
+
 NOTE: Kodi has only been tested with the following versions of the OMAP35x Graphics SDK:
 3.00.00.05, 3.00.00.06, 3.00.00.08, 3.00.00.09
 
@@ -172,88 +173,88 @@ NOTE: Kodi has only been tested with the following versions of the OMAP35x Graph
 
 To create the Kodi executable manually perform these following steps:
 
-	-----------------------------------------------------------------------------
-	6.1 Configure & Make:
-	-----------------------------------------------------------------------------
-	
-        $ ./bootstrap
-	    > ./configure --enable-gles
-
-    This will configure Kodi inside scratchbox ready for compilation on ARM.
-    Because the default is to build for OpenGL, we require the --enable-gles flag to be set for OpenGL ES 2.0.
-    (Note: No OpenGL ES 1.x available)
-	Now, build with the following:
-	
-		> make
-	
-	-----------------------------------------------------------------------------
-	6.2 Install:
-	-----------------------------------------------------------------------------
-
-	There is no need to do 'make install' as we dont want it installed into scratchbox.
-	There is also the slight problem of the fact that scratchbox's 'find' command is outdated and wont execute Kodi's 'make install' correctly.
-	Instead, use the provided shell script:
-		> cd /tools/arm/arm-scripts/
-		> ./create-xbmcfile.sh
-		
-	This will create a tar file tools/arm/arm-scripts/xbmc.tar.bz2 containing the Kodi files, ready for you to transfer to the board.
+-----------------------------------------------------------------------------
+6.1 Configure & Make:
+-----------------------------------------------------------------------------
+
+    $ ./bootstrap
+    $ ./configure --enable-gles
+
+This will configure Kodi inside scratchbox ready for compilation on ARM.
+Because the default is to build for OpenGL, we require the --enable-gles flag to be set for OpenGL ES 2.0.
+Note: No OpenGL ES 1.x available
+Now, build with the following:
+
+    $ make
+
+-----------------------------------------------------------------------------
+6.2 Install:
+-----------------------------------------------------------------------------
+
+There is no need to do 'make install' as we dont want it installed into scratchbox.
+There is also the slight problem of the fact that scratchbox's 'find' command is outdated and wont execute Kodi's 'make install' correctly.
+Instead, use the provided shell script:
+    $ cd /tools/arm/arm-scripts/
+    $ ./create-xbmcfile.sh
+
+This will create a tar file tools/arm/arm-scripts/xbmc.tar.bz2 containing the Kodi files, ready for you to transfer to the board.
 
 
 -----------------------------------------------------------------------------
 7. How to run
 -----------------------------------------------------------------------------
 
-It is assumed you have a beagleboard with all the neccessary hardware installed.
-(e.g keyboard, mouse, and ethernet adapter)
+It is assumed you have a beagleboard with all the necessary hardware installed.
+(e.g. keyboard, mouse, and Ethernet adapter)
 It is also assumed that you have it setup with either Angstrom or Ubuntu.
 
-	-----------------------------------------------------------------------------
-	7.1 Obtaining the Packages:
-	-----------------------------------------------------------------------------
-
-	For Ubuntu: See README.linux for list of packages to install.
-	If planning on not extracting the pkgs file, a few additional packages are required to be installed.
-	These are python and liblzo2
-
-	For Angstrom:
-		# opkg update
-		# opkg install subversion make g++ gcc gawk pmount libtool automake gperf unzip bison libsdl-1.2-dev libsdl-image-1.2-dev libsdl-gfx-dev libsdl-mixer-1.2-dev libfribidi-dev liblzo-dev libfreetype-dev libsqlite3-dev libasound2 python-sqlite3 libcurl4 libxrandr-dev libxrender-dev libmad-dev libogg-dev libvorbis-dev libmysqlclient-dev libpcre-dev libdbus-glib-1-dev hal-dev libjasper-dev libfontconfig-dev boost-dev libxt-dev libxmu-dev libpng-dev libjpeg-dev
-	
-	Unfortunately this will only install the packages that are available through opkg. There will be further packages that need to be installed.
-	Either use the method mentioned below, or selectively find and install packages, mentioned at the bottom of this README.
-
-	Alternatively, do the following:
-	First make sure you have done section 4. then do the following:
-		> cd xbmc_on_arm/arm-scripts/
-		> ./create-pkgsfile.sh
-
-	This will create a tar file xbmc_on_arm/arm-scripts/pkgs.tar.bz2 containing the packages, ready for you to transfer to the board.
-
-	-----------------------------------------------------------------------------
-	7.2 Installing the Files:
-	-----------------------------------------------------------------------------
-
-	Transfer the file(s), armel-pkgs.tar.bz2 (if using alternative method mentioned above) and xbmc.tar.bz2 to the beagleboard.
-	Do the following to extract them:
-		# tar xjf armel-pkgs.tar.bz2 -C /
-		# tar xjf xbmc.tar.bz2 -C /usr/
-
-	After this initial setup, during development, you should only need to replace /usr/share/kodi/kodi.bin with the newly created binary.
-	
-	-----------------------------------------------------------------------------
-	7.3 Running Kodi:
-	-----------------------------------------------------------------------------
-
-	Now, run Kodi by executing the binary:
-		# /usr/share/kodi/kodi.bin
-		
-	Run the binary and not the script as the script will fail.
-	
-	
+-----------------------------------------------------------------------------
+7.1 Obtaining the Packages:
+-----------------------------------------------------------------------------
+
+For Ubuntu: See README.linux for list of packages to install.
+If planning on not extracting the pkgs file, a few additional packages are required to be installed.
+These are python and liblzo2
+
+For Angstrom:
+    $ opkg update
+    $ opkg install subversion make g++ gcc gawk pmount libtool automake gperf unzip bison libsdl-1.2-dev libsdl-image-1.2-dev libsdl-gfx-dev libsdl-mixer-1.2-dev libfribidi-dev liblzo-dev libfreetype-dev libsqlite3-dev libasound2 python-sqlite3 libcurl4 libxrandr-dev libxrender-dev libmad-dev libogg-dev libvorbis-dev libmysqlclient-dev libpcre-dev libdbus-glib-1-dev hal-dev libjasper-dev libfontconfig-dev boost-dev libxt-dev libxmu-dev libpng-dev libjpeg-dev
+
+Unfortunately this will only install the packages that are available through opkg. There will be further packages that need to be installed.
+Either use the method mentioned below, or selectively find and install packages, mentioned at the bottom of this README.
+
+Alternatively, do the following:
+First make sure you have done section 4. then do the following:
+    $ cd xbmc_on_arm/arm-scripts/
+    $ ./create-pkgsfile.sh
+
+This will create a tar file xbmc_on_arm/arm-scripts/pkgs.tar.bz2 containing the packages, ready for you to transfer to the board.
+
+-----------------------------------------------------------------------------
+7.2 Installing the Files:
+-----------------------------------------------------------------------------
+
+Transfer the file(s), armel-pkgs.tar.bz2 (if using alternative method mentioned above) and xbmc.tar.bz2 to the beagleboard.
+Do the following to extract them:
+    $ tar xjf armel-pkgs.tar.bz2 -C /
+    $ tar xjf xbmc.tar.bz2 -C /usr/
+
+After this initial setup, during development, you should only need to replace /usr/share/kodi/kodi.bin with the newly created binary.
+
+-----------------------------------------------------------------------------
+7.3 Running Kodi:
+-----------------------------------------------------------------------------
+
+Now, run Kodi by executing the binary:
+    $ /usr/share/kodi/kodi.bin
+
+Run the binary and not the script as the script will fail.
+
+
 -----------------------------------------------------------------------------
 8. Troubleshooting
 -----------------------------------------------------------------------------
-	
+
 If it fails to run correctly, there are a few things to try out.
 First, is there any helpful output on the terminal?
 Check the log file, usually located ~/.kodi/temp/kodi.log
@@ -265,9 +266,10 @@ Then transfer them to the board, and extract: tar xjf pkg.tar.bz2
 This is because the .deb files cannot be extracted in Angstrom.
 
 If this is not the case, try various different parameters for kodi.bin such as:
-kodi.bin --standalone
-kodi.bin -p
-kodi.bin -fs
-Or build with debug for a more in-depth kodi.log file by ommitting the line --disable-debug on configure.
+    $ kodi.bin --standalone
+    $ kodi.bin -p
+    $ kodi.bin -fs
+
+Or build with debug for a more in-depth kodi.log file by omitting the line --disable-debug on configure.
 
 Feel free to contact me on mcgeagh@xbmc.org
diff --git a/docs/README.ios b/docs/README.ios
index fc585cd0bf..b1af07e741 100644
--- a/docs/README.ios
+++ b/docs/README.ios
@@ -16,7 +16,7 @@ TOC
 1. Introduction
 -----------------------------------------------------------------------------
 
-This is a platform port of Kodi for the Apple iOS operating system. 
+This is a platform port of Kodi for the Apple iOS operating system.
 The current build system supports Xcode 6.0.1 and 6.1.0 with iOS SDK 8.1
 There are two ways to build Kodi for Mac.
 
@@ -40,19 +40,19 @@ character itself should NOT be typed as part of the command.
 2. Getting the source code
 -----------------------------------------------------------------------------
 
- $ cd $HOME
- $ git clone git://github.com/xbmc/xbmc.git Kodi
- $ cd Kodi
- $ git submodule update --init addons/skin.re-touched
+    $ cd $HOME
+    $ git clone git://github.com/xbmc/xbmc.git Kodi
+    $ cd Kodi
+    $ git submodule update --init addons/skin.re-touched
 
 -----------------------------------------------------------------------------
 3.1 Install Xcode
 -----------------------------------------------------------------------------
 See point 3.1.1 below for an updated list of supported Xcode/osx constellations!!!
 
-Install latest Xcode (6.1.0 as of the writing). You can download it from 
+Install latest Xcode (6.1.0 as of the writing). You can download it from
 
-1. The MacOSX AppStore (Xcode). 
+1. The MacOSX AppStore (Xcode).
 
 
 Xcode 6.1.0 only runs on 10.9.5 and later (at least Mavericks).
@@ -62,8 +62,8 @@ The preferred iOS SDK Version is 8.1.
 -----------------------------------------------------------------------------
 3.1.1 Supported Xcode and OSX constellations
 -----------------------------------------------------------------------------
-As far as we know the compilation for ios should work with the following
-constellations of Xcode and osx versions (to be updated once we know more):
+As far as we know the compilation for iOS should work with the following
+constellations of Xcode and OSX versions (to be updated once we know more):
 
 1. Xcode 6.0.1 against iOS SDK 8.0 on 10.9.x (Mavericks)
 2. Xcode 6.1.0 against iOS SDK 8.1 on 10.10.x (Yosemite)
@@ -74,28 +74,28 @@ constellations of Xcode and osx versions (to be updated once we know more):
 3.2 Install Cross libs and runtime environment
 -----------------------------------------------------------------------------
 
- The following commands will build using the latest iOS SDK found on your 
+ The following commands will build using the latest iOS SDK found on your
  system.
 
- $ cd $HOME/Kodi
- $ cd tools/depends
- $ ./bootstrap
- $ ./configure --host=arm-apple-darwin
- $ make
- $ make -C target/binary-addons
- 
+    $ cd $HOME/Kodi
+    $ cd tools/depends
+    $ ./bootstrap
+    $ ./configure --host=arm-apple-darwin
+    $ make
+    $ make -C target/binary-addons
+
  NOTE: if you only want to build specific addons you can specify like this:
-  $ make -C target/binary-addons ADDONS="pvr.hts pvr.dvblink"
+     $ make -C target/binary-addons ADDONS="pvr.hts pvr.dvblink"
 
- NOTE: You can speedup compilation on multicore systems by doing 
- "make -j<number of cores>" instead of "make". For a dualcore this would read:
- "make -j2"
+ NOTE: You can speedup compilation on multicore systems by doing
+       "make -j<number of cores>" instead of "make". For a dualcore this would read:
+    $ make -j2
 
  ADVANCED developers only! If you want to specify an iOS SDK version (if
  multiple versions are installed) - then append it to the configure line
  above (example below would use iOS SDK 8.0):
 
- $ ./configure --host=arm-apple-darwin --with-sdk=8.0
+    $ ./configure --host=arm-apple-darwin --with-sdk=8.0
 
  Ensure that you also adapt the xcode project to use this SDK version or
  if building via cmdline the SDKROOT parameter of the xcodebuild command.
@@ -106,10 +106,10 @@ constellations of Xcode and osx versions (to be updated once we know more):
 Both Xcode and Terminal compilation require that build environment be setup
 from the step 3.2.
 
- $ cd $HOME/Kodi
- $ make -C tools/depends/target/xbmc
- $ make clean
- $ make xcode_depends
+    $ cd $HOME/Kodi
+    $ make -C tools/depends/target/xbmc
+    $ make clean
+    $ make xcode_depends
 
 -----------------------------------------------------------------------------
 4.1 Using Xcode
@@ -120,18 +120,18 @@ located in $HOME/Kodi.
 There are two relevant build configurations : Release and Debug. Compile always for device
 end not simulator and select the target Kodi-iOS.
 
-If you have selected a specific iOS SDK Version in step 3.2 then you might need 
-to adapt the active target to use the same iOS SDK version. Else build will fail 
+If you have selected a specific iOS SDK Version in step 3.2 then you might need
+to adapt the active target to use the same iOS SDK version. Else build will fail
 (you will see alot of errors with at least non-found boost/shared_ptr.hpp).
 
 -----------------------------------------------------------------------------
 4.2 Using Terminal (command-line)
 -----------------------------------------------------------------------------
 
- $ cd $HOME/Kodi
- $ xcodebuild -project Kodi.xcodeproj -target Kodi-iOS -configuration Release build \
-   ONLY_ACTIVE_ARCH=YES ARCHS=armv7 VALID_ARCHS=armv7 SDKROOT=iphoneos8.0
- 
+    $ cd $HOME/Kodi
+    $ xcodebuild -project Kodi.xcodeproj -target Kodi-iOS -configuration Release build \
+      ONLY_ACTIVE_ARCH=YES ARCHS=armv7 VALID_ARCHS=armv7 SDKROOT=iphoneos8.0
+
  Make sure to set SDKROOT to the iOS SDK you want to use. This should be the same
  you used on point 3.2! If latest SDK should be used (and you didn't specify anything
  in step 3.2) - just remove the SDKROOT=iphoneos8.0 from the command line.
@@ -143,32 +143,31 @@ to adapt the active target to use the same iOS SDK version. Else build will fail
 This section describes how to package Kodi in a deb image for
 distribution.
 
-  1. build Kodi for iOS from XCode so that the application bundle is 
-     correctly updated.
+1.  Build Kodi for iOS from XCode so that the application bundle is
+    correctly updated.
+
+2.  $ cd tools/darwin/packaging/ios
 
-  2. 
-   $ cd tools/darwin/packaging/ios
+3.  $ chmod +x ./mkdeb-ios.sh && ./mkdeb-ios.sh release
 
-  3. $ chmod +x ./mkdeb-ios.sh && ./mkdeb-ios.sh release
-     
-  4. Use release or debug - you have to be sure that you build the corresponding 
-     version before.
-  
-  5. The resulting deb file can be copied to the iOS device via ssh/scp and then be 
-     installed manually. For this you need to ssh into the iOS device and do:
-     $ dpkg -i <name of the deb file>
+4.  Use release or debug - you have to be sure that you build the corresponding
+    version before.
+
+5.  The resulting deb file can be copied to the iOS device via ssh/scp and then be
+    installed manually. For this you need to SSH into the iOS device and do:
+    $ dpkg -i <name of the deb file>
 
 -----------------------------------------------------------------------------
 6. Gesture Handling on iPad/iPhone/iPod touch
 -----------------------------------------------------------------------------
 
- - double finger swipe left                   -> back
- - double finger tap/single finger long tap   -> right mouse
- - single finger tap                          -> left mouse
- - panning, and flicking                      -> for navigating in lists
- - dragging                                   -> for scrollbars and sliders
- - zoom gesture                               -> in the pictureviewer
- 
+ - Double finger swipe left                   -> Back
+ - Double finger tap/single finger long tap   -> Right mouse
+ - Single finger tap                          -> Left mouse
+ - Panning, and flicking                      -> For navigating in lists
+ - Dragging                                   -> For scrollbars and sliders
+ - Zoom gesture                               -> In the pictureviewer
+
  Gestures can be adapted in system/keymaps/touchscreen.xml
 
 ------------------------------------------------------------------------------
diff --git a/docs/README.linux b/docs/README.linux
index cf8f27a5ed..d0d02a5db0 100644
--- a/docs/README.linux
+++ b/docs/README.linux
@@ -59,8 +59,8 @@ Build-Depends: autoconf, automake, autopoint, autotools-dev, cmake, curl,
   libxmu-dev, libxrandr-dev, libxslt1-dev, libxt-dev, libyajl-dev (>=2.0), lsb-release,
   nasm [!amd64], python-dev, python-imaging, python-support, swig, unzip, uuid-dev, yasm,
   zip, zlib1g-dev
-  
-[NOTICE] crossguid / libcrossguid-dev all Linux destributions.
+
+[NOTICE] crossguid / libcrossguid-dev all Linux distributions.
 Kodi now requires crossguid which is not available in Ubuntu repositories at this time.
 We supply a Makefile in tools/depends/target/crossguid
 to make it easy to install into /usr/local.
@@ -101,19 +101,16 @@ Tip: By adding -j<number> to the make command, you describe how many
      concurrent jobs will be used. So for dualcore the command is:
 
     $ make -j2
- 	
+
 .3  $ make install
 
 This will install Kodi in the prefix provided in 4.1 as well as a launcher script.
 
-Note: You may need to run this with sudo (sudo make install) if your user doesn't have write permissions
-to the prefix you have provided (as in the default case, /usr/local).
-
 Tip: To override the location that Kodi is installed, use PREFIX=<path>.
 For example.
 
-    $ make install DESTDIR=$HOME/kodi
-	
+    $ sudo make install DESTDIR=$HOME/kodi
+
 -----------------------------------------------------------------------------
 4.4. Binary addons - compile
 -----------------------------------------------------------------------------
@@ -134,7 +131,7 @@ PVR addons:
     pvr.argustv, pvr.demo, pvr.dvblink, pvr.dvbviewer, pvr.filmon, pvr.hts, pvr.iptvsimple, pvr.mediaportal.tvserver,
     pvr.mythtv, pvr.nextpvr, pvr.njoy, pvr.pctv, pvr.stalker, pvr.vbox, pvr.vdr.vnsi, pvr.vuplus
 
-Audio decoders: 
+Audio decoders:
     audiodecoder.modplug, audiodecoder.nosefart, audiodecoder.sidplay, audiodecoder.snesapu,
     audiodecoder.stsound, audiodecoder.timidity, audiodecoder.vgmstream
 
@@ -168,7 +165,7 @@ The most useful options are,
     --gtest_list_tests
       List the names of all tests instead of running them.
 	  The name of TEST(Foo, Bar) is "Foo.Bar".
-      
+
     --gtest_filter=POSTIVE_PATTERNS[-NEGATIVE_PATTERNS]
       Run only the tests whose name matches one of the positive patterns but
       none of the negative patterns. '?' matches any single character; '*'
diff --git a/docs/README.osx b/docs/README.osx
index c6570f249d..9a60985870 100644
--- a/docs/README.osx
+++ b/docs/README.osx
@@ -44,8 +44,8 @@ its not part of OSX anymore since 10.8.
 2. Getting the source code
 -----------------------------------------------------------------------------
 
- $ cd $HOME
- $ git clone git://github.com/xbmc/xbmc.git Kodi
+       $ cd $HOME
+       $ git clone git://github.com/xbmc/xbmc.git Kodi
 
 -----------------------------------------------------------------------------
 3.1 Install XCODE
@@ -74,34 +74,34 @@ constellations of Xcode and osx versions (to be updated once we know more):
  system.
 
 3.2.1 Compiling as 32 Bit binary
- $ cd $HOME/Kodi
- $ cd tools/depends
- $ ./bootstrap
- $ ./configure --host=i386-apple-darwin
- $ make
+    $ cd $HOME/Kodi
+    $ cd tools/depends
+    $ ./bootstrap
+    $ ./configure --host=i386-apple-darwin
+    $ make
 
 3.2.2 Compiling as 64 Bit binary
- $ cd $HOME/Kodi
- $ cd tools/depends
- $ ./bootstrap
- $ ./configure --host=x86_64-apple-darwin
- $ make
+    $ cd $HOME/Kodi
+    $ cd tools/depends
+    $ ./bootstrap
+    $ ./configure --host=x86_64-apple-darwin
+    $ make
 
 3.2.3 Compile binary addons
- $ make -C target/binary-addons
+    $ make -C target/binary-addons
 
  NOTE: if you only want to build specific addons you can specify like this:
-  $ make -C target/binary-addons ADDONS="pvr.hts pvr.dvblink"
+    $ make -C target/binary-addons ADDONS="pvr.hts pvr.dvblink"
 
  NOTE: You can speedup compilation on multicore systems by doing
- "make -j<number of cores>" instead of "make". For a dualcore this would read:
- "make -j2"
+       "make -j<number of cores>" instead of "make". For a dualcore this would read:
+    $ make -j2
 
  ADVANCED developers only! If you want to specify an OSX SDK version (if
  multiple versions are installed) - then append it to the configure line
  above (example below would use OSX SDK 10.9 and build for 64bit):
 
- $ ./configure --host=x86_64-apple-darwin --with-sdk=10.9
+    $ ./configure --host=x86_64-apple-darwin --with-sdk=10.9
 
  Ensure that you also adapt the xcode project to use this SDK version.
 
@@ -114,16 +114,16 @@ first. This is a simple step and involves the following:
 4.a Compilation by using command-line building via xcodebuild or
     by compiling via Xcode GUI
 
- $ cd $HOME/Kodi
- $ make -C tools/depends/target/xbmc
- $ make clean
- $ make xcode_depends
+    $ cd $HOME/Kodi
+    $ make -C tools/depends/target/xbmc
+    $ make clean
+    $ make xcode_depends
 
 4.b Compilation by using command-line building via make (experimental)
 
- $ cd $HOME/Kodi
- $ make -C tools/depends/target/xbmc
- $ make clean
+    $ cd $HOME/Kodi
+    $ make -C tools/depends/target/xbmc
+    $ make clean
 
 The configure operation will setup the build environment for codecs and
 internal libraries that are used by Kodi. This step is required for both Xcode
@@ -154,11 +154,11 @@ then build.
 
 If you have selected a specific OSX SDK Version in step 3.2 then you might need 
 to adapt the active target to use the same OSX SDK version. Else build will fail 
-(you will see alot of errors with at least non-found boost/shared_ptr.hpp).
+(you will see a lot of errors with at least non-found boost/shared_ptr.hpp).
 
 The build process will take a long time when building the first time. 
 You can see the progress in "Build Results". There are a large number of static 
-and dynamic libaries that will need to be built. Once these are built, 
+and dynamic libraries that will need to be built. Once these are built, 
 subsequent builds will be faster.
 
 After the build, you can ether run Kodi for Mac from Xcode or run it from
@@ -166,16 +166,16 @@ the command-line. If you run it from the command-line, make sure your set
 the KODI_HOME environment variable (export KODI_HOME=$HOME/Kodi). Then, to
 run the debug version:
 
-$ ./build/Debug/Kodi
+    $ ./build/Debug/Kodi
 
 Or the release version:
 
-$ ./build/Release/Kodi
+    $ ./build/Release/Kodi
 
 You can also build via Xcode from the command-line using the following:
 
-$ xcodebuild -configuration Release ONLY_ACTIVE_ARCH=YES ARCHS=i386 VALID_ARCHS=i386 \
-  -target "Kodi.app" -project Kodi.xcodeproj
+    $ xcodebuild -configuration Release ONLY_ACTIVE_ARCH=YES ARCHS=i386 VALID_ARCHS=i386 \
+      -target "Kodi.app" -project Kodi.xcodeproj
 
 You can specify "Release" instead of "Debug" as a configuration. Be sure to set *_ARCHS
 variables to the same architecture as selected in step 3.2 (either i386 for 32Bit or x86_64 
@@ -191,17 +191,17 @@ You could try xcodebuild from the command-line with altered SDK - like 10.9 in t
 below(normally unneeded - for advanced developers).
 
  a)
- $ cd $HOME/Kodi
- $ export KODI_HOME=`pwd`
- $ make xcode_depends
- $ xcodebuild -sdk macosx10.9 -project Kodi.xcodeproj -target Kodi.app ONLY_ACTIVE_ARCH=YES \
-   ARCHS=x86_64 VALID_ARCHS=x86_64  -configuration Release build
+    $ cd $HOME/Kodi
+    $ export KODI_HOME=`pwd`
+    $ make xcode_depends
+    $ xcodebuild -sdk macosx10.9 -project Kodi.xcodeproj -target Kodi.app ONLY_ACTIVE_ARCH=YES \
+      ARCHS=x86_64 VALID_ARCHS=x86_64  -configuration Release build
 
  b) building via make
- $ cd $HOME/Kodi
- $ export KODI_HOME=`pwd`
- $ make
- $ ./Kodi.bin
+    $ cd $HOME/Kodi
+    $ export KODI_HOME=`pwd`
+    $ make
+    $ ./Kodi.bin
 
 -----------------------------------------------------------------------------
 5. Packaging
@@ -209,13 +209,13 @@ below(normally unneeded - for advanced developers).
 This section describes how to package Kodi in a disk image for
 distribution.
 
-  1. build Kodi.app from XCode so that the application bundle is correctly updated.
+1. build Kodi.app from XCode so that the application bundle is correctly updated.
 
-  2. $ cd tools/darwin/packaging/osx
+2.  $ cd tools/darwin/packaging/osx
 
-  3. $ chmod +x ./mkdeb-osx.sh && ./mkdmg-osx.sh release
+3.  $ chmod +x ./mkdeb-osx.sh && ./mkdmg-osx.sh release
 
-  4. Use release or debug - you have to be sure that you build the corresponding
-     version before.
+4. Use release or debug - you have to be sure that you build the corresponding
+   version before.
 
-  6. Find the corresponding dmg in the packaging dir.
+6. Find the corresponding dmg in the packaging dir.
diff --git a/docs/README.raspberrypi b/docs/README.raspberrypi
index e6fa154e71..3e9b943f57 100644
--- a/docs/README.raspberrypi
+++ b/docs/README.raspberrypi
@@ -8,7 +8,7 @@ TOC
 -----------------------------------------------------------------------------
 
 You can build Kodi for the Raspberry Pi in different ways. This document
-shows two differnt methods. The first assumes that you want to run Kodi
+shows two different methods. The first assumes that you want to run Kodi
 on top of an image like Raspbian, the second shows how to create an entire
 image which includes Linux.
 
@@ -19,22 +19,22 @@ image which includes Linux.
 The following steps were tested with Ubuntu 14.04 x64. (Note that building on
 a 32 bit machine requires slightly different setting)
 
-    sudo apt-get install git autoconf curl g++ zlib1g-dev libcurl4-openssl-dev gawk gperf libtool autopoint swig default-jre
+    $ sudo apt-get install git autoconf curl g++ zlib1g-dev libcurl4-openssl-dev gawk gperf libtool autopoint swig default-jre
 
-    git clone https://github.com/raspberrypi/tools
-    sudo cp -r tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64 /opt
+    $ git clone https://github.com/raspberrypi/tools
+    $ sudo cp -r tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64 /opt
 
-    git clone https://github.com/raspberrypi/firmware
-    sudo mkdir -p /opt/bcm-rootfs/opt
-    sudo cp -r firmware/opt/vc /opt/bcm-rootfs/opt
+    $ git clone https://github.com/raspberrypi/firmware
+    $ sudo mkdir -p /opt/bcm-rootfs/opt
+    $ sudo cp -r firmware/opt/vc /opt/bcm-rootfs/opt
 
-    sudo mkdir -p /opt/xbmc-bcm
-    sudo chmod 777 /opt/xbmc-bcm
+    $ sudo mkdir -p /opt/xbmc-bcm
+    $ sudo chmod 777 /opt/xbmc-bcm
 
-    git clone https://github.com/xbmc/xbmc
+    $ git clone https://github.com/xbmc/xbmc
 
-    cd xbmc/tools/depends
-    ./bootstrap
+    $ cd xbmc/tools/depends
+    $ ./bootstrap
     PATH="$PATH:/opt/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin" \
        ./configure --host=arm-linux-gnueabihf \
        --prefix=/opt/xbmc-bcm/xbmc-dbg \
@@ -43,8 +43,8 @@ a 32 bit machine requires slightly different setting)
        --with-platform=raspberry-pi \
        --build=i686-linux
 
-    make
-    cd ../..
+    $ make
+    $ cd ../..
 
     CONFIG_EXTRA="--with-platform=raspberry-pi \
        --enable-libcec --enable-player=omxplayer \
@@ -52,10 +52,10 @@ a 32 bit machine requires slightly different setting)
        --disable-optical-drive --disable-dvdcss --disable-joystick \
        --disable-crystalhd --disable-vtbdecoder --disable-vaapi \
        --disable-vdpau --enable-alsa" \
-       make -C tools/depends/target/xbmc
+    $ make -C tools/depends/target/xbmc
 
-    make
-    make install
+    $ make
+    $ sudo make install
 
 -----------------------------------------------------------------------------
 3. Building Kodi using buildroot environment
@@ -67,18 +67,18 @@ Create a top level directory where you checkout Kodi and buildroot.
 
 For example :
 
-mkdir /opt/kodi-raspberrypi
-cd /opt/kodi-raspberrypi
+    $ mkdir /opt/kodi-raspberrypi
+    $ cd /opt/kodi-raspberrypi
 
 Checkout kodi :
 
-git clone https://github.com/xbmc/xbmc.git kodi
+    $ git clone https://github.com/xbmc/xbmc.git kodi
 
 Checkout buildroot :
 
-git clone https://github.com/huceke/buildroot-rbp.git
+    $ git clone https://github.com/huceke/buildroot-rbp.git
 
-cd /opt/kodi-raspberrypi/buildroot-rbp
+    $ cd /opt/kodi-raspberrypi/buildroot-rbp
 
 Follow the instructions in README.rbp how to build the system and Kodi.
 
diff --git a/docs/README.ubuntu b/docs/README.ubuntu
index c36ccd6637..7bf1fe3641 100644
--- a/docs/README.ubuntu
+++ b/docs/README.ubuntu
@@ -55,7 +55,7 @@ For <= 12.04 lts:
 
 For >= 14.04 lts:
     $ sudo apt-get install software-properties-common
-    $ sudo add-apt-repository -s ppa:team-xbmc/xbmc-nightly 
+    $ sudo add-apt-repository -s ppa:team-xbmc/xbmc-nightly
 
 Add build-depends PPA:
     $ sudo add-apt-repository ppa:team-xbmc/xbmc-ppa-build-depends
@@ -81,17 +81,29 @@ Tip: For those with multiple computers at home is to try out distcc
 -----------------------------------------------------------------------------
 
 For Ubuntu (all versions >= 7.04):
-    $ sudo apt-get install automake bison build-essential cmake curl cvs dcadec-dev default-jre fp-compiler gawk gdc gettext git-core gperf libasound2-dev libass-dev libboost-dev libboost-thread-dev libbz2-dev libcap-dev libcdio-dev libcurl3 libcurl4-openssl-dev libdbus-1-dev libfontconfig-dev libfreetype6-dev libfribidi-dev libgif-dev libglew-dev libiso9660-dev libjasper-dev libjpeg-dev liblzo2-dev libmicrohttpd-dev libmodplug-dev libmpeg2-4-dev libmpeg3-dev libmysqlclient-dev libnfs-dev libogg-dev libpcre3-dev libplist-dev libpng-dev libpulse-dev libsdl2-dev libsmbclient-dev libsqlite3-dev libssh-dev libssl-dev libtiff-dev libtinyxml-dev libtool libudev-dev libusb-dev libva-dev libvdpau-dev libvorbis-dev libvorbisenc2 libxml2-dev libxmu-dev libxrandr-dev libxrender-dev libxslt1-dev libxt-dev libyajl-dev mesa-utils nasm pmount python-dev python-imaging python-sqlite swig unzip uuid-dev yasm zip zlib1g-dev
+    $ sudo apt-get install automake bison build-essential cmake curl cvs dcadec-dev \
+      default-jre fp-compiler gawk gdc gettext git-core gperf libasound2-dev libass-dev \
+      libboost-dev libboost-thread-dev libbz2-dev libcap-dev libcdio-dev libcurl3 \
+      libcurl4-openssl-dev libdbus-1-dev libfontconfig-dev libfreetype6-dev libfribidi-dev \
+      libgif-dev libglew-dev libiso9660-dev libjasper-dev libjpeg-dev liblzo2-dev libmicrohttpd-dev \
+      libmodplug-dev libmpeg2-4-dev libmpeg3-dev libmysqlclient-dev libnfs-dev libogg-dev libpcre3-dev \
+      libplist-dev libpng-dev libpulse-dev libsdl2-dev libsmbclient-dev libsqlite3-dev libssh-dev \
+      libssl-dev libtiff-dev libtinyxml-dev libtool libudev-dev libusb-dev libva-dev libvdpau-dev \
+      libvorbis-dev libvorbisenc2 libxml2-dev libxmu-dev libxrandr-dev libxrender-dev libxslt1-dev \
+      libxt-dev libyajl-dev mesa-utils nasm pmount python-dev python-imaging python-sqlite swig \
+      unzip uuid-dev yasm zip zlib1g-dev
 
 For >= 10.10:
     $ sudo apt-get install autopoint libltdl-dev
 
 For >= 12.04 lts: Backport for Precise of libyajl2
-	& sudo-add-apt-repository ppa:team-xbmc/xbmc-nightly
-	& sudo apt-get install libyajl-dev
-	
+    $ sudo-add-apt-repository ppa:team-xbmc/xbmc-nightly
+    $ sudo apt-get install libyajl-dev
+
+Note: Ubuntu Precise users also need a upgraded GCC, else compile will fail.
+
 For >= 12.10:
-	$ sudo apt-get install libtag1-dev
+    $ sudo apt-get install libtag1-dev
 
 On 8.10 and older versions, libcurl is outdated and thus Kodi will not compile properly.
 In this case you will have to manually compile the latest version.
@@ -111,10 +123,10 @@ We also supply a Makefile in lib/taglib to make it easy to install into /usr/loc
 1.  $ sudo apt-get remove libtag1-dev
     $ make -C lib/taglib
     $ sudo make -C lib/taglib install
-	
+
 [NOTICE] crossguid / libcrossguid-dev all Linux destributions.
 Kodi now requires crossguid which is not available in Ubuntu repositories at this time.
-If build-deps PPA doesnt provide a pre-packaged version for your dissee (1.) below.
+If build-deps PPA doesn't provide a pre-packaged version for your distribution, see (1.) below.
 
 Use prepackaged from the Kodi build-depends PPA.
 0.  $ sudo apt-get install libcrossguid-dev