From 58a1af4954eaeedff6ac7c5280a37b83e61fe51e Mon Sep 17 00:00:00 2001
From: Dave Herder <27025660+dherder@users.noreply.github.com>
Date: Fri, 15 Dec 2023 11:49:07 -0800
Subject: [PATCH] Update communications.md to clarify the specifics around noun
 labels (#15587)

Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
---
 handbook/company/communications.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/handbook/company/communications.md b/handbook/company/communications.md
index cb00766148..897d8932be 100644
--- a/handbook/company/communications.md
+++ b/handbook/company/communications.md
@@ -216,7 +216,9 @@ Fleet prefixes all GitHub labels with special characters or words to organize an
 | `customer-`       | [Customer request](TODO link to handbook section) | `customer-leo`, `customer-sagittarius`
 | `#g-`             | Group isssue | _An issue requesting something from a group at Fleet, such that it will be seen and procesed on their kanban board within 1 business day._
 
-Opionated conventions help people work faster and spend less time figuring out what to name things, or misunderstanding why they're named what they are.  This also reduces the total number of labels required while maintaining an expressive labeling system. For example, instead of a label called `platform-dev-backend`, we use `#platform :dev ~backend`.
+Opinionated conventions help people work faster and spend less time figuring out what to name things, or misunderstanding why they're named what they are.  This also reduces the total number of labels required while maintaining an expressive labeling system. For example, instead of a label called `platform-dev-backend`, we use `#platform :dev ~backend`.
+
+Labels with a `#g-` prefix refer to a kanban board. Since it is best practice to have an issue on a single board, make an effort to have only one label with the `#g-` prefix per issue.
 
 > _**Note:** There are only a few "special" labels that are exceptions to this rule:
 > - `bug`