Cleanup suggestions

[Jahteo]

Initial recommended changes, including minor discussion comments that should be implemented or removed.
Big changes are:

• Reorganizes steps so learner can simply go from top to bottom, instead of back and forth. Plus 2 of the 3 Common Setup Steps were only used in Local Setup which was confusing.
  • Exception: troubleshooting steps are still at the bottom
• adds Docker troubleshooting steps discussed in slack\

[justinbmeyer]

did you look at this rendered? H2s being underlined have a nice visual distinction isolating their content. These core "setup" sections should be h2s to make their content very clear where it is.

[Jahteo]

I think it's more important to be explicit that the ### DevContainer Setup and ### Local Setup are both options under the ## Setup Dev Environment versus both being steps that need to be followed. If they're H3's, a learner can look at the outline and understand the high level page structure as:

• Setup Visual Studio Code
• Setup Dev Environment
• Verifying Setup
• Troubleshooting
• Next Steps
  Since we haven't decided if this will be in the academy, read from github, or cloned locally, it feels weird to break semantic html patterns just for styling.

That said, I do agree the raw file and preview both needed visual distinction, and personally kept wanting to have AI add an emoji to each H2 & H3. So I get it if you decide to make them H2, we'd just want an inline way to be explicit that they're not both required steps.
It could be by making the headers something like "## Recommended DevContainer Setup" & "## Alternative Local Setup" and removing the "## Setup Dev Environment"

[Jahteo]

Do we want to add instructions or solution notes on how a learner can verify they setup correctly?

[Jahteo]

[minor discussion]
These "clone" instructions don't match the "clone" instructions in the DevContainer setup. There, it clones from inside VSCode terminal with different commands, here it assumes use of a generic terminal.