Index: branches/fc19-dev/server/doc/install-howto.sh
===================================================================
--- branches/fc19-dev/server/doc/install-howto.sh	(revision 2402)
+++ branches/fc19-dev/server/doc/install-howto.sh	(revision 2487)
@@ -339,5 +339,5 @@
 # [TESTSERVER] If you're installing a test server, this needs to be
 # much smaller; the max filesize on XVM is 10GB.  Pick something like
-# 500000. Also, some of the AFS parameters are kind of retarded (and if
+# 500000. Also, some of the AFS parameters are kind of silly (and if
 # you're low on disk space, will actually exhaust our inodes).  Edit
 # these parameters in /etc/sysconfig/openafs (I just chopped a zero
Index: branches/fc19-dev/server/doc/package-build-howto
===================================================================
--- branches/fc19-dev/server/doc/package-build-howto	(revision 2402)
+++ branches/fc19-dev/server/doc/package-build-howto	(revision 2487)
@@ -47,5 +47,8 @@
     # somewhere safe after each build to preserve them)
     # Add the packages to the repository by using a trusted machine and
-    krootscp root@[BUILD-SERVER]:/var/lib/mock/fedora-[RELEASE]-{x86_64|i386}/result /mit/scripts/rpm-fc[RELEASE]
+    krootscp root@[BUILD-SERVER]:/var/lib/mock/fedora-[RELEASE]-{x86_64|i386}/result /mit/scripts/yum-repos/rpm-fc[RELEASE]
+
+    # There has been some historic discussion about whether SRPMs should be
+    # added to the repository. At this point, the standard is to include them.
 
   * # Rebuild the repo metadata to include the new packages.
@@ -57,5 +60,5 @@
     createrepo -d -o /root/repodata-YYYYMMDD .
     # Then from your trusted machine
-    krootscp -r root@[BUILD-SERVER]:/root/repodata-YYYYMMDD /mit/scripts/rpm-fc[RELEASE]
+    krootscp -r root@[BUILD-SERVER]:/root/repodata-YYYYMMDD /mit/scripts/yum-repos/rpm-fc[RELEASE]
     # Sanity check the files, and then replace the current repodata directory
     # with the one in repodata-YYYYMMDD.