I noticed that this code

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 1.4, available at
<https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>,
and the [Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html).

formats as

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html, and the Rust Code of Conduct.

the [homepage] needs to be corrected.

It looks like this probably affects all copies of the CoC.

Don’t just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they’re off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.

I'll get the pedantic (non-judgemental!) comment out of the way. I love, love using semi-colons, but there are a couple too many in this sentence.

I have a couple wording suggestions as well, but it's easier just to provide a full sample. 😄

The goal of the standards and moderation guidelines outlined above is to build and maintain a respectful community. We ask that you don’t just aim to be "technically unimpeachable", but rather try to be your best self. In particular, avoid offensive or sensitive issues, particularly if they’re off-topic to the channel or discussion. This all too often leads to unnecessary fights, perceptions or instances of disrespect, and damaged community trust. Worse, it can drive people away from the community entirely.

I know its still a work-in-progress and this may work itself out, but the scoping statements are confusing.

The repo and document title define it as the Discord CoC, and use of "On Discord" or Discord-centric terminology is used throughout the document without contrasting definitions (e.g. "On the forums").

Then, at the end of the document there is this statement:

The enforcement policies listed above apply to all official Adafruit venues. This includes but is not limited to the entire Adafruit Discord server, GitHub repositories under Adafruit, and all forums under forums.adafruit.com.

Again, I know this may work itself out. Or may be a small cog in a larger machine that I'm not aware of. Just confusion that I think could be addressed.

PRs fail with the following:

Run echo "::set-env name=PY::$(python -c 'import hashlib, sys;print(hashlib.sha256(sys.version.encode()+sys.executable.encode()).hexdigest())')"
  echo "::set-env name=PY::$(python -c 'import hashlib, sys;print(hashlib.sha256(sys.version.encode()+sys.executable.encode()).hexdigest())')"
  shell: /bin/bash -e {0}
  env:
    pythonLocation: /opt/hostedtoolcache/Python/3.9.1/x64
Error: Unable to process command '::set-env name=PY::8d19a760b2e5ab871a9f2f6daa7a1e22a98236991e81df060a0709222deb3662' successfully.
Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

The included link (https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/) points to an explanation of the security vulnerability and points to the documentation to update it. It may be simple, but it's not readily apparent to me and I am in the middle of something else at the moment and cannot dig into it.