diff --git a/src/source/build-numbers.md b/src/source/build-numbers.md
index ecff4f1..8d1dd3b 100644
--- a/src/source/build-numbers.md
+++ b/src/source/build-numbers.md
@@ -97,9 +97,9 @@
 GRJ06D | android-2.3.4_r0.9 | Nexus S 4G
 GRJ22  | android-2.3.4_r1   | Nexus One, Nexus S, Nexus S 4G
 GRJ90  | android-2.3.5_r1   | Nexus S 4G
-GRK39C |                    | Nexus S
-GRK39F |                    | Nexus One, Nexus S
-GWK74  |                    | latest Gingerbread version, Nexus S 4G
+GRK39C | android-2.3.6_r0.9 | Nexus S
+GRK39F | android-2.3.6_r1   | Nexus One, Nexus S
+GWK74  | android-2.3.7_r1   | latest Gingerbread version, Nexus S 4G
 
 The branches donut, eclair, froyo, gingerbread represent development
 branches that do not exactly match configurations that were tested
@@ -121,17 +121,18 @@
 HRI93  | android-3.0_r1.3
 HMJ37  | android-3.1_r1
 HTJ85B | android-3.2_r1
-HTK55D |
-HTK75D |
-HLK75C |
-HLK75D |                    | latest Honeycomb version
+HTK55D | android-3.2.1_r1
+HTK75D | android-3.2.1_r2
+HLK75C | android-3.2.2_r1
+HLK75D | android-3.2.2_r2   | latest Honeycomb version
 
 There is no manifest that contains exactly those. However, there
 are manifests that allow building those components. The following
 commands work for 3.0_r1.1, and using other versions can be done by
-switching the git checkout paramater, and if necessary the -b parameter in
-repo init.
+switching the git checkout paramater, and if necessary the -m parameter in
+repo init. The git checkout command outputs an error for the non-GPL
+projects, where it can't find the tag in question.
 
-    $ repo init -b master -m 3.0-base.xml
+    $ repo init -b master -m base-for-3.0-gpl.xml
     $ repo sync
     $ repo forall -c git checkout android-3.0_r1.1
diff --git a/src/source/downloading.md b/src/source/downloading.md
index 7a120b8..42008e5 100644
--- a/src/source/downloading.md
+++ b/src/source/downloading.md
@@ -29,27 +29,29 @@
 
  - Download the Repo script and ensure it is executable:
 
-        $ curl https://android.git.kernel.org/repo > ~/bin/repo
+        $ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
         $ chmod a+x ~/bin/repo
 
- - The MD5 checksum for repo is bbf05a064c4d184550d71595a662e098
+ - The SHA-1 checksum for repo is e1fd3bef059d152edf4d0522590725d317bc637f
 
 ## Initializing a Repo client ##
 
 After installing Repo, set up your client to access the android source repository:
 
- - Create an empty directory to hold your working files:
+ - Create an empty directory to hold your working files.
+ Give it any name you like:
+
 
         $ mkdir WORKING_DIRECTORY
         $ cd WORKING_DIRECTORY
 
  - Run `repo init` to bring down the latest version of Repo with all its most recent bug fixes.  You must specify a URL for the manifest, which specifies where the various repositories included in the Android source will be placed within your working directory.
 
-        $ repo init -u git://android.git.kernel.org/platform/manifest.git
+        $ repo init -u https://android.googlesource.com/platform/manifest
 
     To check out a branch other than "master", specify it with -b:
 
-        $ repo init -u git://android.git.kernel.org/platform/manifest.git -b froyo
+        $ repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.7_r1
 
  - When prompted, please configure Repo with your real name and email address.  To use the Gerrit code-review tool, you will need an email address that is connected with a [registered Google account](http://www.google.com/accounts).  Make sure this is a live address at which you can receive messages.  The name that you provide here will show up in attributions for your code submissions.
 
@@ -63,7 +65,10 @@
 
     $ repo sync
 
-The Android source files will be located in your working directory under their project names.  The initial sync operation will take several minutes to complete.  For more about `repo sync` and other Repo commands, see [Version Control](version-control.html).
+The Android source files will be located in your working directory
+under their project names. The initial sync operation will take
+an hour or more to complete. For more about `repo sync` and other
+Repo commands, see [Version Control](version-control.html).
 
 
 ## Verifying Git Tags ##