Fix example in tutorial. Fixes #449.

README.md

@@ -291,20 +291,16 @@ mailing list and mailing a SASE.
 You don't need to "build" Leiningen per se, but when you're using a
 checkout you will need to get its dependencies in place.
 
-For example, if you'd like to use the 1.x branch you can:
-
-   git clone https://github.com/technomancy/leiningen.git
-   git checkout 1.x
-   lein self-install
-
-Using Leiningen 1.x, run `lein install` in the `leiningen-core`
-subproject directory. When the dependencies change you will also have
-to do `rm .lein-classpath` in the project root.
+For the master branch, use Leiningen 1.x to run `lein install` in the
+`leiningen-core` subproject directory. When the dependencies change
+you will also have to do `rm .lein-classpath` in the project root.
 
 Once you've done that, symlink `bin/lein` to somewhere on your
 `$PATH`, usually as `lein2` in order to keep it distinct from your
 existing installation.
 
+If you want to develop on the 1.x branch, this should be unnecessary.
+
 ## License
 
 Source Copyright © 2009-2012 Phil Hagelberg, Alex Osborne, Dan Larkin, and

doc/TUTORIAL.md

@@ -29,8 +29,8 @@ Generating a new project is easy:
 
 Here we've got your project's README, a `src/` directory containing the
 code, a `test/` directory, and a `project.clj` file which describes your
-project to Leiningen. The `src/my/stuff.clj` file corresponds to
-the `my.stuff` namespace.
+project to Leiningen. The `src/my_stuff/core.clj` file corresponds to
+the `my-stuff.core` namespace.
 
 Note that we use `my-stuff.core` instead of just `my-stuff` since
 single-segment namespaces are discouraged in Clojure. Also note that