diff --git a/CompileError.md b/CompileError.md
index 33501a6..877f8fa 100644
--- a/CompileError.md
+++ b/CompileError.md
@@ -18,7 +18,7 @@ error: Python.h: No such file or directory
 
 ### Why This Happens
 
-To decide what to do about this, you have to understand that the Tahoe-LAFS software itself is written in 100% pure Python and never gets compiled. However, Tahoe-LAFS uses several libraries which themselves contain native C or C++ code that needs to be compiled. Currently there are six such libraries that Tahoe-LAFS uses: `Twisted`, `pyOpenSSL`, `pycrypto`, `pycryptopp`, `zfec`, and `zope.interface`.
+First of all, the Tahoe-LAFS software itself is written in 100% pure Python and never gets compiled. However, Tahoe-LAFS uses several libraries which themselves contain native C or C++ code that needs to be compiled. Currently there are six such libraries that Tahoe-LAFS uses: `Twisted`, `pyOpenSSL`, `pycrypto`, `pycryptopp`, `zfec`, and `zope.interface`.
 
 To understand why the compile failure happens and how to get past it, you have to understand that `python setup.py build` tries *three* different methods of satisfying Tahoe-LAFS' need for its libraries, and only if all three methods fail does it emit an error message like this.