diff --git a/README.md b/README.md
index 9c1afa64..6bfce84b 100644
--- a/README.md
+++ b/README.md
@@ -18,21 +18,22 @@ the directory from where its included, compile them, and and add them to a
 central shared library. It would also take all header files and copy them to a
 central include directory. `js.mk` would by default minify all JavaSript it
 finds, `java.mk` jar up .java files into classes and jar-files, and so on.
-JW-Build also handles installation and packaging of all of these files, to
+JW-Build also handles installation and packaging of these files, to
 customizable locations with standardish defaults.
 
-JW-Build is small. It's small enough to be self-documenting. Well, okay,
-somewhat self-documenting. It better be, given its lack of documentation. You
-have to know GNU Makefile syntax to understand what it does, and dig into its
-somtimes arcane code, ideally with a working example. You can install it with
-your distribution's package manager, or you can keep it within your code
-versioning system, alongside your own code. It's also designed to be the
-lightest possible touch on any given source code package, in terms of code you
-need to add to a package you want to build with it, and also in terms of needed
-prerequisite software packages. This way, it's easily introduced - and it's
-also easy to get rid of, should you choose to do so at some point in time.  You
-will then have all your settings like file system path definitions and compiler
-flags in well-defined places already.
+JW-Build is small, its tarball is about 200K. It's small enough to be shipped
+with your project, if you choose to do so. And it's small enough to be
+self-documenting. Well, okay, somewhat self-documenting. You have to know GNU
+Makefile syntax to understand what it does, and dig into its somtimes arcane
+code, ideally with a working example. You can install it with your
+distribution's package manager, or you can keep it within your code versioning
+system, alongside your own code. It's also designed to be the lightest possible
+touch on any given source code package, in terms of code needed to add to a
+given package that should be built with it, and also in terms of needed
+prerequisite software packages. This way, it's easily added - and it's also
+easy to replace, should you choose to do so at some point. You will then have
+all your settings like file system path definitions and compiler flags in
+well-defined places already.
 
 JW-Build runs a recursive make, so, with a few exceptions such as submodules,
 you will need a makefile in every directory with source code. Most, if not all