Fix @joshuagl suggestions

theupdateframework · Jun 8, 2022 · 0bfab6f · 0bfab6f
1 parent 21c807e
commit 0bfab6f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
@@ -6,15 +6,15 @@ Please familiarize yourself with these Contribution Guidelines before contributi
 
 There are many ways to help go-tuf besides contributing code:
 
-- Fix bugs or file issues
+- Fix bugs or file issues.
 - Provide feedback on the CLI experience or suggest feature enhancements.
 - Improve documentation.
 
 Please follow the [code of conduct](CODE_OF_CONDUCT.md) when contributing to this project.
 
 ## Contributing Code
 
-Unless you are fixing a known bug, we strongly recommend discussing it with the community via a GitHub issue or Slack before getting started to ensure that your work is consistent with TUF's specification.
+Unless you are fixing a known bug, we strongly recommend discussing it with the community via a GitHub issue or Slack (see [Communication](#communication) below for details) before getting started to ensure that your work is consistent with TUF's specification.
 
 All contributions are made via pull request. All patches from all contributors get reviewed. See the [Pull Request procedure](#pull-request-procedure).
 
@@ -49,7 +49,7 @@ We use the [#tuf](https://cloud-native.slack.com/archives/C8NMD3QJ3) and [#go-tu
 You might also be interested in the TUF community beyond go-tuf; good places to start include:
 
 - [TUF mailing list](https://groups.google.com/g/theupdateframework)
-- TUF community meetings (monthly; join the mailing list to receive invitations)
+- TUF community meetings (monthly; join the mailing list or watch the Slack channel to see invitations)
 
 
 ## Pull Request Review Policy

diff --git a/docs/MAINTAINERS.md b/docs/MAINTAINERS.md
@@ -12,7 +12,7 @@ Speedy communication makes contributors happy!
 - If you are assigned to review a PR, please try to *acknowledge* it within one business day (no need if you are OOO).
 - Please review all PRs within five business days (of course, it's okay if you're OOO).
 - Please use the review checklist below.
-- We should make sure there's a reviewer for every PR with tests passing within 
+- We should make sure there's an assigned reviewer for every PR which has passing tests.
 
 Versioning: