Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I moved the header for the Codespaces vs dev editor up a bit more and broke up the paragraph a bit since it seemed dense.
Another piece of feedback I would recommend that Aaron preaches is driving the why. I would add and merge this paragraph I found from the following blog to the opening paragraph of the learning unit , https://github.blog/2023-05-10-revolutionize-your-open-source-workflows-the-top-3-reasons-why-github-codespaces-is-a-must-have-for-maintainers/
"GitHub Codespaces is a revolutionary cloud-based development environment that makes it easier than ever to create, manage, and collaborate on code in the cloud. You can spin up a pre-configured development environment in no time, complete with all the tools and dependencies you need to get started on your project. If you’re new to GitHub Codespaces, you can learn how to get started here.
This streamlined process eliminates the need for manual configuration tasks, freeing up valuable time for you and your contributors. And with GitHub Codespaces, contributors can easily access their IDE from anywhere with an internet connection. This means they can work on your project from any device, at any time, without worrying about compatibility issues."
Also I would recommend creating a new learning unit to encompass everything after the table. This unit seems a bit long.