diff --git a/RELEASING.md b/RELEASING.md
index c1c0733..66fdacb 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -1,5 +1,7 @@
 # How to release `cloud.google.com/go`
 
+1. Navigate `google-cloud-go/` and switch to master.
+1. `git pull`
 1. Determine the current release version with `git tag -l`. It should look
    something like `vX.Y.Z`. We'll call the current version `$CV` and the new
    version `$NV`.
@@ -8,8 +10,9 @@
 1. Edit `CHANGES.md` to include a summary of the changes.
 1. `cd internal/version && go generate && cd -`
 1. `./tidyall.sh`
-1. Mail the CL. When the CL is approved, submit it.
-1. Without submitting any other CLs:
+1. Mail the CL: `git add -A && git change && git mail`
+1. Wait for the CL to be submitted. Once it's submitted, and without submitting
+   any other CLs in the meantime:
    a. Switch to master.
    b. `git pull`
    c. Tag the repo with the next version: `git tag $NV`.
@@ -24,19 +27,22 @@
 
 To release a submodule:
 
-1. (these instructions assume we're releasing cloud.google.com/go/datastore -
-   adjust accordingly)
-1. Determine the current release version with `git tag -l`. It should look
-   something like `datastore/vX.Y.Z`. We'll call the current version `$CV` and
-   the new version `$NV`, which should look something like `datastore/vX.Y+1.Z`
+(these instructions assume we're releasing cloud.google.com/go/datastore - adjust accordingly)
+
+1. Navigate `google-cloud-go/` and switch to master.
+1. `git pull`
+1. Determine the current release version with `git tag -l | grep datastore`. It
+   should look something like `datastore/vX.Y.Z`. We'll call the current version
+   `$CV` and the new version `$NV`, which should look something like `datastore/vX.Y+1.Z`
    (assuming a minor bump).
 1. On master, run `git log $CV.. -- datastore/` to list all the changes to the
    submodule directory since the last release.
 1. Edit `datastore/CHANGES.md` to include a summary of the changes.
 1. `./tidyall.sh`
 1. `cd internal/version && go generate && cd -`
-1. Mail the CL. When the CL is approved, submit it.
-1. Without submitting any other CLs:
+1. Mail the CL: `git add -A && git change && git mail`
+1. Wait for the CL to be submitted. Once it's submitted, and without submitting
+   any other CLs in the meantime:
    a. Switch to master.
    b. `git pull`
    c. Tag the repo with the next version: `git tag $NV`.
diff --git a/tidyall.sh b/tidyall.sh
index cdfa496..20c362e 100755
--- a/tidyall.sh
+++ b/tidyall.sh
@@ -16,8 +16,8 @@
 # Run at repo root.
 
 go mod tidy
-for m in logging datastore bigquery bigtable; do
-    pushd $m
-    go mod tidy
-    popd
+for i in `find . -name go.mod`; do
+pushd `dirname $i`;
+    go mod tidy;
+popd;
 done