Update README.md

README.md

@@ -9,18 +9,18 @@ The ideal situation is to have the build processes staggered:
 
 1. one large memory consumer that is just about to finish, 
 2. one medium sized process that will become the largest memory consumer next, and
-3. a couple small processes that aren't using much memory yet.
+3. a couple smaller processes that aren't using much memory yet.
 
-By keeping the processes pipelined in this fashion, we can keep all 4 cores of the Raspberry Pi 4 largely fully utilitized, without running into out of memory situations and swamping the system with swap space thrash.
+By keeping the processes pipelined in this fashion, we can keep all 4 cores of the Raspberry Pi 4 largely utilized, without running into out of memory situations and swamping the system with swap thrash.
 
-As a side benefit, this tool also ends up automatically throttling back emerge builds whenever you're busy using your computer for other tasks. Sure, you builds will take longer to complete, but at least they won't completely fail or prevent you from being able to use your computer at all, like they would otherwise.
+As a side benefit, this tool also ends up automatically throttling back emerge builds whenever you're busy using your computer for other tasks. Sure, your builds will take longer to complete, but at least they won't completely fail or prevent you from being able to use your computer at all, like they would otherwise.
 
 Requirements
 ============
-This program uses the procps library and executes the "ps" command internally to watch the portage user's processes. 
+This program is written in Qt, uses the procps library, and executes the "ps" command internally to watch the portage user's processes. 
 
 How to Use
 ==========
-Run this program as root, or at least as the "portage" user, so that it will have permission to send stop and continue "kill" signals to the cc1plus processes spawned by your emerge build. You can freely start up or terminate this program at any time and it will pick right up suspending and resuming portage build processes for you. 
+Run this program as root, or at least as the "portage" user, so that it will have permission to send stop and continue "kill" signals to the cc1plus processes spawned by your emerge build. You can freely start up, terminate, or re-start this program at any time and it will pick right up suspending and resuming the on-going portage build processes for you. 
 
 Unfortunately, this program does not work against "rustc" builds, as rust seems to do some funny business with CPU usage reporting and the way it manages to carry out builds. But it should work great for programs compiled with gcc or clang.