Fixed few grammatical errors

README.md

@@ -3,18 +3,18 @@ Android Blob Utility
 by JackpotClavin
 
 The Android Blob Utility is a program designed to make developing AOSP-based
-ROMs easier for developers. What is does is it allows the developer to pick
+ROM's easier for developers. What is does is it allows the developer to pick
 proprietary file, type the file's absolute path, and this program will spit
-back every library that should be needed in order to get that library or daemon
+back every library that should be needed to get that library or daemon
 to run on an AOSP ROM.
 
-How does it work? First the developer must dump their entire stock ROM's
+How does it work? First, the developer must dump their entire stock ROM's
 software to their computer, so that typing the command:
 `$ ls /home/android/dump/build.prop` will yield their device's build.prop.
 This is just meant to ensure that you have the correct path it is valid.
 Next, you are to compile this program with the `make` command. Once you run it,
 the program will prompt you to enter whatever the SDK version of you /system
-dump happens to be (check your /system/build.prop), for instance if your
+dump happens to be (check your /system/build.prop), for instance, if your
 /system dump is Android 4.3, type in `18` (use the following site for
 [guidelines](https://developer.android.com/guide/topics/manifest/uses-sdk-element.html#ApiLevels)).
 Secondly, the program will ask you for the location of your /system dump; so if
@@ -25,12 +25,12 @@ prompted for the manufacturer(vendor) and device name, I inputted `lge`, and
 `vs980`, respectively. For the third step of getting the necessary blobs,
 this program will prompt you to enter however many blobs files you want this
 program to process. If you want to only process one blob, type `1` and hit
-enter. After you enter the amount of blobs you want this program to process, you
+enter. After you enter the number of blobs you want this program to process, you
 will type the absolute path to the actual blob (see the [example program usage]
 (https://github.com/JackpotClavin/Android-Blob-Utility/blob/master/Example_Usage.txt)),
 and this program will print out all of the proprietary blobs that are mentioned
 in that particular blob that you entered, that aren't in the emulator's /system
-dump. That means that those files are either have to be built from source, or
+dump. That means that those files are either have to be built from source or
 are proprietary and must be copied into the ROM's build. This program will also
 format the blobs such that it is ready to be placed into a vendor-blobs.mk file
 in your vendor folder of the ROM's source tree root.
@@ -41,9 +41,9 @@ blobs that may slip past the linker because they are called in the actual code
 of the blob. Simply copying the shared libraries just appeases the linker, but
 the blob still not run properly as the blob may want additional libraries.
 
-This program also searches recursively, so each and every blob that is found is
+This program also searches recursively, so each blob that is found is
 also processed through the searching algorithm, to see which blobs *that*
-library also needs to run, so we cover all of the bases in order to get a
+library also needs to run, so we cover all of the bases to get a
 proprietary library or daemon to run.
 
 The following example was used on my LG G2. Running this program with the two
@@ -57,4 +57,3 @@ the proprietary file.
 
 Example program usage can be found in the [Example_Usage.txt](https://github.com/JackpotClavin/Android-Blob-Utility/blob/master/Example_Usage.txt)
 in this folder.
-