Merge pull request #20 from jgarciao/fix-some-typos

Fix some typos

docs/building-simple-apps.rst

@@ -8,7 +8,7 @@ This section describes how to build a simple application which doesn't require a
 Creating an app
 ---------------
 
-To create an application, the first step is to use the ``build-init`` command. This creates a directory into which an applcation can be built, which contains the correct directory structure and a metadata file which contains information about the app. The format for build-init is::
+To create an application, the first step is to use the ``build-init`` command. This creates a directory into which an application can be built, which contains the correct directory structure and a metadata file which contains information about the app. The format for build-init is::
 
   $ flatpak build-init DIRECTORY APPNAME SDK RUNTIME [BRANCH]
 

docs/flatpak-builder.rst

@@ -1,7 +1,7 @@
 Flatpak Builder
 ===============
 
-Most applications require additional dependencies that aren't provided by their runtimes. Flatpak allows these dependencies to be bundled as part of the application itself. In order to do this, each dependency must be built inside the application build directory. The ``flatpak-builder`` tool automates this multi-step build process, making it possible to build all application modules with a single command. 
+Most applications require additional dependencies that aren't provided by their runtimes. Flatpak allows these dependencies to be bundled as part of the application itself. In order to do this, each dependency must be built inside the application build directory. The ``flatpak-builder`` tool automates this multi-step build process, making it possible to build all application modules with a single command.
 
 flatpak-builder expects modules to be built in the standard manner by following what is called the `Build API <https://github.com/cgwalters/build-api/>`_. This requires modifying modules to follow the build API, if they don't already.
 
@@ -61,7 +61,7 @@ Files that are exported by a flatpak must be prefixed using the application ID.
 Splitting things up
 -------------------
 
-By default, flatpak-builder splits off translations and dubug information into separate .Locale and .Debug extensions. These 'standard' extension points are then added to the application's metadata file. You can turn this off with the ``separate-locales`` and ``no-debuginfo`` keys, but there shouldn't be any reason for it.
+By default, flatpak-builder splits off translations and debug information into separate .Locale and .Debug extensions. These 'standard' extension points are then added to the application's metadata file. You can turn this off with the ``separate-locales`` and ``no-debuginfo`` keys, but there shouldn't be any reason for it.
 
 When flatpak-builder exports the build into a repository, it automatically includes the .Locale and .Debug extensions. If you do the exporting manually, don't forget to include them.
 

docs/getting-setup.rst

@@ -8,7 +8,7 @@ Once flatpak has been installed, it is necessary to pick a runtime and install i
 Installing an SDK
 -----------------
 
-An SDK is a special type of runtime that is used to build applcations. Typically, an SDK is paired with a runtime that will be used by the application at runtime. For example the GNOME 3.22 SDK is used to build applications that use the GNOME 3.22 runtime. 
+An SDK is a special type of runtime that is used to build applications. Typically, an SDK is paired with a runtime that will be used by the application at runtime. For example the GNOME 3.22 SDK is used to build applications that use the GNOME 3.22 runtime.
 
 The Flatpak website provides a `list of the available runtimes <http://flatpak.org/runtimes.html>`_. Once you have decided which one to use, getting setup is just a matter of installing it and its SDK.