From 7f361c126e40909a82ea94440ca9c6414bce1d2c Mon Sep 17 00:00:00 2001 From: Sebastian Spier Date: Tue, 12 Sep 2023 20:12:02 +0200 Subject: [PATCH] [vale] 'incoming' seems like a reasonable replacement? --- patterns/2-structured/project-setup/base-documentation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/patterns/2-structured/project-setup/base-documentation.md b/patterns/2-structured/project-setup/base-documentation.md index e64261007..07376584e 100644 --- a/patterns/2-structured/project-setup/base-documentation.md +++ b/patterns/2-structured/project-setup/base-documentation.md @@ -86,7 +86,7 @@ topics: Create a separate `COMMUNICATION.md` document. Link this document to your README.md so comprehensive contact information can be provided and not take up the extra space in your README. This document should answer frequently asked questions about communicating with your team that contributors need to know. The goal is to streamline communications so users and contributors reach out to the correct person through a single channel. This reduces unnecessary distractions for team members and organizes communications so they do not get lost. -These communications can be broken into ingoing and outgoing communications. Sections in the COMMUNICATION.md include: +These communications can be broken into incoming and outgoing communications. Sections in the COMMUNICATION.md include: Points of contact for incoming communication and how to contact those users. Some examples include: * Reporting a bug