diff --git a/Packaging.md b/Packaging.md
index 716e887..80962e2 100644
--- a/Packaging.md
+++ b/Packaging.md
@@ -11,11 +11,11 @@ The setup method that we offer to people when we don't know what platform they a
 
 ### binary .egg's of dependency native-code packages
 
-For quickstart.html to work on your platform there *must* exist a binary .egg for your platform of every dependency which has a native-code extension module. Currently those are: pycryptopp, zfec, pywin32, and [PyCrypto](PyCrypto). If there is not a binary .egg available of one of those packages for a given platform then this is a bug which prevents quickstart.html from working on that platform. (Note: if you already had that Python package installed on your system then you would be able to setup Tahoe-LAFS even if there is not a binary egg of that Python package available, e.g. if you manually installed the package already or if you installed the package already using an operating system packaging tool like apt-get. Nonetheless, since we can't rely on the user having done that and since quickstart.html cannot instruct the user to do that (see the section about quickstart.html above), then the absence of a binary .egg of a dependency for a platform is a bug preventing quickstart.html from working on that platform.
+For quickstart.html to work on your platform there *must* exist a binary .egg for your platform of every dependency which has a native-code extension module. Currently those are: pycryptopp, zfec, pywin32, and [PyCrypto](PyCrypto). If there is not a binary .egg available of one of those packages for a given platform then this is a bug which prevents quickstart.html from working on that platform. (Note: if you already had that Python package installed on your system then you would be able to setup Tahoe-LAFS even if there is not a binary egg of that Python package available, e.g. if you manually installed the package already or if you installed the package already using an operating system packaging tool like apt-get. Nonetheless, since we can't rely on the user having done that and since quickstart.html cannot instruct the user to do that (see the section about quickstart.html above), then the absence of a binary .egg of a dependency for a platform is a bug preventing quickstart.html from working on that platform.)
 
 ## [AdvancedInstall](AdvancedInstall)
 
-Another installation method, alternative to quickstart.html, is [AdvancedInstall](AdvancedInstall). This method would be appropriate for people who prefer for the setup to be done differently than the way quickstart.html works. It is also the fallback for people who have tried quickstart.html and it didn't work (although the fact that quickstart.html didn't work should also be treated as a build process bug even if falling back to [AdvancedInstall](AdvancedInstall) allows the user to proceed).
+An alternative method to quickstart.html, is [AdvancedInstall](AdvancedInstall). This method would be appropriate for people who prefer for the setup to be done differently than the way quickstart.html works. It is also the fallback for people who have tried quickstart.html and it didn't work (although the fact that quickstart.html didn't work should also be treated as a build process bug even if falling back to [AdvancedInstall](AdvancedInstall) allows the user to proceed).
 
 ## pre-built Debian packages