diff --git a/documentation/getting.sgml b/documentation/getting.sgml
index c354df3be11..2939f24e8c8 100644
--- a/documentation/getting.sgml
+++ b/documentation/getting.sgml
@@ -66,17 +66,10 @@
 	        They install everything else that's needed for their
 	        operation, they usually preconfigure a lot, and you
 	        don't need to worry about compiling anything or so.
-	        However, the Wine Team doesn't have "official" packages.
-	        All Wine packages are being offered by external groups,
-	        with often slightly inaccurate or quite inaccurate Wine
-	        environment setup.
-		Also, a package you downloaded might turn out to be
-		partially incompatible with your particular system
-		configuration.
-	        Thus it might actually be <emphasis>better</emphasis>
-	        to compile Wine from source and completely install it
-	        on your own, by following the instructions in this
-	        Guide.
+	        You can get the official wine packages from
+		<ulink url="http://sourceforge.net/project/showfiles.php?group_id=6241">
+          the sourceforge.net Wine download page</ulink>
+
 	      </para>
 	    </listitem>
 	  </varlistentry>
@@ -181,7 +174,7 @@
           and even from different versions of the same distribution.
           Often a package will only work on the distribution which it
 	  has been compiled for.  We'll cover
-          <link linkend="getting-dist-debian">Debian Linux</link>, 
+          <link linkend="getting-dist-debian">Debian Linux</link>,
           <link linkend="getting-dist-linux">Red Hat, Mandrake, SuSE and Slackware Linux</link>,
           <link linkend="getting-freebsd">FreeBSD</link>, and
           <link linkend="getting-other">other</link> distributions.
@@ -356,8 +349,8 @@
 	Wine files), either to use the most recent code possible or to
 	improve it, then the first thing to do is to obtain a copy of
 	the source code. We'll cover how to retrieve and compile the
-	official source releases from the <link
-	linkend="getting-source-ftp">FTP archives</link>, and also how
+	source releases from the <link
+	linkend="getting-source">official archives</link>, and also how
 	to get the cutting edge up-to-the-minute fresh Wine source code
 	from <link linkend="getting-source-cvs">CVS (Concurrent Versions
 	System)</link>.
@@ -387,8 +380,8 @@
         patch</link> and revert it if it doesn't work.
       </para>
 
-      <sect2 id="getting-source-ftp">
-        <title>Getting Wine Source Code from an FTP Archive</title>
+      <sect2 id="getting-source">
+        <title>Getting Wine Source Code from the official archives</title>
 
         <para>
           The safest way to grab the source is from one of the official
@@ -449,10 +442,6 @@
 
       <sect2 id="getting-source-cvs">
         <title>Getting Wine Source Code from CVS</title>
-	<!-- this part is sort of duplicated in cvs.sgml
-	     (this representation is meant to be a very short intro
-	     instead, but it's similar). Please don't forget to update both!
-	-->
 
         <para>
 	  This part is intended to be quick and easy, showing the bare minimum