*However, if you want to add new patches to an existing external,
 you should change the version number and add a new external!  We do
 NOT want to have multiple things which are different code to be using
-the same version! The new version number should include a -p<number> on the end.*
+the same version!*
+
+When adding new patches to an existing external, add a =-p1= to the =[version]= to get your new version. If the =[version]= already ends in =-p<number>=, increment the number for your new version. You should continue to use the original tarball (with it's original name).
 
 Again, if you have any questions or are uncertain, just ask.
 
@@ -185,9 +187,7 @@
 named "=[name]-[version].tar.gz=" (and, needless to say, it must
 be a real gzip'ed tar file).  For example, "=krb5-1.2.7.tar.gz=".
 An important exception is that the =-p<number>= at the end of the version
-is optional in the tarball name. For example, the tarball for external =krb5-1.2.7-p1= can be named =krb5-1.2.7.tar.gz=.
-
-We'll discuss what to do with the tarball later on.
+is optional in the tarball name. For example, the tarball for external =krb5-1.2.7-p1= can be named =krb5-1.2.7.tar.gz= (the same tarball used for external =krb5-1.2.7=).
 
 {subsection: Putting the source tarball on the web server}