Modified: trunk/base/portmgr/ReleaseProcess (68279 => 68280)

--- trunk/base/portmgr/ReleaseProcess	2010-05-30 22:47:54 UTC (rev 68279)
+++ trunk/base/portmgr/ReleaseProcess	2010-05-31 01:33:28 UTC (rev 68280)
@@ -159,8 +159,8 @@
  mv MacPorts-1.6.0.dmg MacPorts-1.6.0-10.5-Leopard.dmg
  for dmg in MacPorts-1.6.0-*.dmg; do for type in -md5 -sha1 -ripemd160; do openssl dgst $type $dmg; done >> MacPorts-1.6.0.chk.txt; done
 
-These new products, along with the new checksums, also have to be posted to the appropriate downloads
-directory of the MacPorts svn repository. Developers are required to validate the generated installer as
+These new products, along with the new checksums, also have to be posted to the appropriate
+directory of the MacPorts distfiles server. Developers are required to validate the generated installer as
 thoroughly as possible through extensive testing, which is mainly why this step of the release process
 is not automated through a Makefile target or similar. A good way of validating the installer is to first
 create the destroot of the port and examine it for: