Fix typo in documentations

CONTRIBUTING.md

@@ -71,7 +71,7 @@ New contributions are added under AGPL version 3.
 We are all about quality while not sacrificing speed so we use a very pragmatic workflow.
 
 * create an issue with feature request
-    * discuss it with other developers 
+    * discuss it with other developers
     * create mockup if necessary
     * must be approved --> label approved
     * after that no conceptual changes!
@@ -143,17 +143,17 @@ We do differentiate between three different kinds of releases:
 
 ### Stable
 Play store and f-droid releases for the masses.
-Pull Requests that have been tested and reviewed can go to master. After the last release candidate is out in the wild for ~2 weeks and no errors get reported (by users or in the developer console) the master branch is ready for the stable release. 
+Pull Requests that have been tested and reviewed can go to master. After the last release candidate is out in the wild for ~2 weeks and no errors get reported (by users or in the developer console) the master branch is ready for the stable release.
 So when we decide to go for a new release we freeze the master feature wise.
 
 ### Release Candidate
 _stable beta_ releases done via the Beta program of the Google Play store and f-droid.
 Whenever a PR is reviewed/approved we put it on master.
-Before releasing a new stable version there is at least one release candidate. It is based on the current master and during this phase the master is feature freezed. After ~2 weeks with no error a stable version will be releaded, which is identically to the latest release candidate. 
+Before releasing a new stable version there is at least one release candidate. It is based on the current master and during this phase the master is feature freezed. After ~2 weeks with no error a stable version will be released, which is identical to the latest release candidate. 
 
 ### Dev
 Done as a standalone app that can be installed in parallel to the stable app.
-Any PR which is labelled "ready for dev" will be automatically included in the dev app. This label should only set by the main developers. 
+Any PR which is labelled "ready for dev" will be automatically included in the dev app. This label should only set by the main developers.
 Same applies for the android-library. This repository also has a branch called dev which includes all upcoming features. The dev branch on this repository must always use the android-library dev branch.
 
 ## Version Name and number

SETUP.md

@@ -51,12 +51,12 @@ To set up the project in Android Studio follow the next steps:
 
 * Make sure you have called ```git submodule update``` whenever you switched branches
 * Open Android Studio and select 'Import Project (Eclipse ADT, Gradle, etc)'. Browse through your file system to the folder 'android' where the project is located. Android Studio will then create the '.iml' files it needs. If you ever close the project but the files are still there, you just select 'Open Project…'. The file chooser will show an Android face as the folder icon, which you can select to reopen the project.
-* Android Studio will try to build the project directly after importing it. To build it manually, follow the menu path 'Build'/'Make Project', or just click the 'Play' button in the tool bar to build and run it in a mobile device or an emulator. The resulting APK file will be saved in the 'build/outputs/apk/' subdirectory in the project folder.
+* Android Studio will try to build the project directly after importing it. To build it manually, follow the menu path 'Build'/'Make Project', or just click the 'Play' button in the toolbar to build and run it in a mobile device or an emulator. The resulting APK file will be saved in the 'build/outputs/apk/' subdirectory in the project folder.
 
 
 ### 3. Working in a terminal with Gradle:
 
-[Gradle][7] is the build system used by Android Studio to manage the building operations on Android apps. You do not need to install Gradle in your system, and Google recommends not to do it, but instead trusting on the [Graddle wrapper][8] included in the project.
+[Gradle][7] is the build system used by Android Studio to manage the building operations on Android apps. You do not need to install Gradle in your system, and Google recommends not to do it, but instead trusting on the [Gradle wrapper][8] included in the project.
 
 * Open a terminal and go to the 'android' directory that contains the repository.
 * Make sure you have called ```git submodule update``` whenever you switched branches