Update v0.6.0 docs to include fixed tutorial 🤒

[bobcatfish]

Changes

In #1199 @moficodes reported that the tutorial wasn't working which was
b/c in #1172 when I updated the braces, I only half updated the tutorial
example. I wanted to fix this for the v0.6.0 docs as well, but since the
released binary and yaml files don't need an update, it didn't make
sense to me to create v0.6.1 for this (and leave the v0.6.0 docs
broken!) so I created a 0.6 branch and cherry picked the docs fix into
it only, and am now updating the README to point at that.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• [n/a] Includes tests (if functionality changed/added)
• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

• If you are adding a new binary/image to the cmd dir, please update
  the release Task and TaskRun to build and release this image

Reviewer Notes

If API changes
are included, additive changes
must be approved by at least two OWNERS
and backwards incompatible changes
must be approved by more than 50% of the OWNERS,
and they must first be added
in a backwards compatible way.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bobcatfish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [bobcatfish]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[bobcatfish]

Heads up @vdemeester @imjasonh @afrittoli @dibyom @sbwsg @dlorenc @abayer - so I've created a 0.6 branch but I haven't actually tagged a new release (see description above). Let me know if you think this is too crazy and we should tag a new release after all.

[ghost]

This makes perfect sense to me. I would suggest that cutting release branches versus just tagging master is, in general, probably a good practice. But that's prolly a whole different convo to have another time.

[ghost]

/lgtm