updates for the basics section for v0.23 / sc24 (#406)

Author: becker33

outputs/basics.sh

@@ -10,7 +10,7 @@ project="$(dirname "$0")"
 export SPACK_COLOR=never
 
 # basic installation
-example basics/clone           "git clone --depth=100 --branch=$tutorial_branch https://github.com/spack/spack.git ~/spack"
+example basics/clone           "git clone --depth=2 --branch=$tutorial_branch https://github.com/spack/spack.git ~/spack"
 example basics/clone           "cd ~/spack"
 
 cd ~/spack || exit

outputs/defs.sh

@@ -14,7 +14,7 @@ fi
 raw_outputs="${PROJECT}/raw"
 
 # used by scripts
-tutorial_branch=releases/v0.22
+tutorial_branch=releases/v0.23
 
 print_status() {
     printf "\n%b: %s\n\n" "\033[1;35m$1\033[0m" "$2"

tutorial_basics.rst

@@ -28,7 +28,7 @@ Installing Spack
 ----------------
 
 Spack works out of the box. Simply clone Spack to get going. We will
-clone Spack and immediately check out the most recent release, v0.22.
+clone Spack and immediately check out the most recent release, v0.23.
 
 .. literalinclude:: outputs/basics/clone.out
    :language: console
@@ -174,7 +174,7 @@ top-level package, we can also specify about a dependency using ``^``.
 Packages can also be referred to from the command line by their package
 hash. Using the ``spack find -lf`` command earlier we saw that the hash
 of our optimized installation of zlib-ng (``cflags="-O3"``) began with
-``6bhcy77``. We can now explicitly build with that package without typing
+``umrbkwv``. We can now explicitly build with that package without typing
 the entire spec, by using the ``/`` sigil to refer to it by hash. As with
 other tools like Git, you do not need to specify an *entire* hash on the
 command line.  You can specify just enough digits to identify a hash