Fixed a few spelling, grammar and phrase construction issues.

2 files changed, 12 insertions, 12 deletions

diff --git a/abstract.md b/abstract.md
index fbee8a4..864fffe 100644
--- a/abstract.md
+++ b/abstract.md
@@ -3,7 +3,7 @@ GNU/Linux based distribution: software components are built and bundled together
 a single image without using any package manager during the build process; external
 software components are also tasked with maintaining support for AOSP build system
 themselves. Theses differences creates some extremely serious issues that also affect
-Replicant, a fully free software Android distribution. To solve that, we aims to foster
+Replicant, a fully free software Android distribution. To solve that, we aim to foster
 a discussion with other projects and the community on sustainable ways to achieve an
 AOSP build that properly incorporates GNU/Linux projects such as Linux and Mesa.
 This talk might also be interesting to people packaging Android utilities like adb in
diff --git a/full-description.md b/full-description.md
index 644688b..e9dce0b 100644
--- a/full-description.md
+++ b/full-description.md
@@ -31,17 +31,17 @@ GNU/Linux distributions.
 
 ## Building AOSP vs building GNU/Linux distros
 Virtually all GNU/Linux distributions use package managers when building their
-software. This wrap around the build system being used by the software
-(Makefiles, autools, cmake, etc) and bundles the output in a reusable package.
-While such packages can usually be installed by the user, and are typicaly
+software. They wrap around the build system being used by the software
+(Makefiles, autools, cmake, etc) and bundle the output in a reusable package.
+While such packages can usually be installed by the user, and are typically
 delivered and updated via software repositories, it is not always the case.
 For instance, it is possible to create OpenWRT images lacking a package manager.
 
-In the AOSP build system, there is no package manager being used to build the
+In the AOSP build system, no package manager is used to build the
 system components. Instead, most software components are built from git
 repositories and bundled into a single image that includes the majority of the
-distribution. The output of the build ends up in a directory that is then used
-to create the distribution image that are to be installed on a device.
+distribution. The output of the build ends up in a directory, which is then
+compressed into a distribution image and later installed on a device.
 
 Besides the core components of AOSP, community distributions tend to use several
 external projects like Mesa. These must usually be integrated into the build
@@ -70,12 +70,12 @@ be unsustainable.
 More importantly, the future of all Android distributions are very seriously
 threatened by the lack of package manager in the build system. Packages
 definitions typically have a license field. Instead, as Android doesn't use
-packages during the build process, and as all its git repositories checked out
-under a single directory, there is no easy way to keep track of the list of
+packages during the build process, and as all its git repositories are checked
+out under a single directory, there is no easy way to keep track of the list of
 licenses that are used.
 
 Replicant is thus seeking to discuss and ultimately decide on a sustainable way
-to go deal with external software components.
+to deal with external software components.
 
-To really fix the issues, it would be crucial to make if Android support some
-form of packages during the build.
\ No newline at end of file
+To really fix these issues, it would be crucial to make Android support some
+form of packages during the build.