Merge pull request ribot#5 from ribot/fix_boilerplate_and_typo

Linked to our new public boilerplate

Author: Ivan Carballo

architecture_guidelines/android_architecture.md

@@ -6,7 +6,7 @@ The architecture of our Android apps is structured in two layers.
 
 * __Data Layer__: this is responsible for retrieving, saving, caching and massaging data so it is provided to the UI layer in its optimal form to be displayed. It can communicate with local databases and other data stores as well as with restful APIs or third party SDKs. It is divided in two parts: a group of helpers and a `DataManager`. The number of helpers vary between project and each of them has a very specific function, e.g. talking to an API or saving data in `SharedPreferences`. The `DataManager` combines and transforms the outputs from different helper using Rx operators so it can provide meaningful data to the UI layer. 
 
-![](achitecture_diagram.png)
+![](architecture_diagram.png)
 
 Looking at the diagram from right to left: 
 

architecture_guidelines/achitecture_diagram.png renamed to architecture_guidelines/architecture_diagram.png

@@ -2,7 +2,7 @@
 
 ## 1.1 Project structure 
 
-New projects should follow the Android Gradle project structure that is defined on the [Android Gradle plugin user guide](http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Project-Structure). The [BoilerPlate](http://git.ribot.io/ribot/android-boilerplate) project is a good reference.
+New projects should follow the Android Gradle project structure that is defined on the [Android Gradle plugin user guide](http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Project-Structure). The [BoilerPlate](https://github.com/ribot/android-boilerplate) project is a good reference.
 
 ## 1.2 Package structure