Clarify wording of checkout dependencies in tutorial.

NEWS.md

@@ -13,7 +13,6 @@
 * Test selectors may allow entire namespaces to be skipped. (Anthony Grimes)
 * Allow project's git repo to be different than project root. (David Greenberg)
 * Don't AOT the `:main` namespace outside of uberjar task.
-* Check Clojars releases repository by default instead of legacy Clojars.
 * Allow hooks from profiles to apply with limited scope. (Hugo Duncan)
 * Fix a bug where profile-specific paths were ignored in trampoline.
 * Support reading from stdin inside project process.

bin/release

@@ -36,7 +36,7 @@ time ../lein-$RELEASE_VERSION run -m clojure.main/main -e nil
 
 echo "If these are under 3 seconds then you should be set to upload"
 echo "target/leiningen-$RELEASE_VERSION-standalone.jar to S3."
-echo "s3c me put -P target/leiningen-2.0.0-RC1-standalone.jar s3://leiningen/downloads/"
+echo "s3c me put -P target/leiningen-2.0.0-$LEIN_VERSION-standalone.jar s3://leiningen/downloads/"
 echo "Also deploy this release of leiningen-core to Clojars."
 
 # Still manual for now:

doc/TUTORIAL.md

@@ -244,10 +244,13 @@ Then, under the checkouts directory, create symlinks to projects you need.
 Libraries located under the `checkouts` directory take precedence
 over libraries pulled from repositories, but this is not a replacement
 for listing the project in your main project's `:dependencies`; it
-simply supplements that for convenience.
+simply supplements that for convenience. If you have a project in
+`checkouts` without putting it in `:dependencies` then its source will
+be visible but its dependencies will not be found.
 
-The checkouts feature is not transitive: in other words, Leiningen
-will not find checkout dependencies of a checkout dependency.
+Checkouts are an opt-in feature; not everyone who is working on the
+project will have the same set of checkouts, so your project should
+work without checkouts before you push or merge.
 
 ## Running Code