Enforce onboarding doc improvements about edu

[ltagliaferri]

Hi Kim — I am looking at this onboarding doc but let me know if I should be looking elsewhere.

• Not sure where GCP and gcloud CLI are? I can't find them in either the onboarding doc or the UI doc
• I see the bash upgrade link in both the onboarding doc and the UI doc
• The path recommendation was based on previous docs and demos, is the bin folder workflow preferred / is there more context I can look at?
• Cosign is not used in the onboarding doc
• $TUTORIAL_IMAGE | jq is not in the doc
• We are working on a style guide! Writing style is not objective, but the"we" is intentional. It promotes a personal relationship between writer and reader, helps to avoid overusing "you" which can sound like a command in many repetitions, and allows us to avoid passive voice. Still, we don't want to overuse this, so we will read this again with a careful eye towards subject pronouns

[amdawson]

Hi Lisa, I took these notes before some of the changes that were put in this week. let me go through again and clarify which ones I see as still relevant.

[amdawson]

• we mention gcp and gcloud cli but then change to kind - looks like this been fixed
• mentions a bash upgrade guide but does not link to one - this has been fixed although the curl and jq links inside the console.enforce.dev tutorial still go to a blank page. I think these are being addressed in a separate issue.
• instead of adding the download location to the PATH, can we mv chainctl to a bin folder? - I'm checking with the team on this.
• add installing cosign to prerequisites - correct, cosign isn't used in this tutorial.
• add EXPERIMENTAL flag to cosign verify $TUTORIAL_IMAGE | jq - yes I think this was in an older version of the doc. disregard
• writing style, avoid using “we” - looking forward to the style guide!