From f6bdafae1833ac2890b13b080a19ce48ac39def0 Mon Sep 17 00:00:00 2001 From: Alyssa Rock <43180546+barbaricyawps@users.noreply.github.com> Date: Sat, 12 Sep 2020 13:29:16 -0600 Subject: [PATCH] Update style-guide/about-style-guide.md Co-authored-by: Lana Brindley --- style-guide/about-style-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/style-guide/about-style-guide.md b/style-guide/about-style-guide.md index 78eb1280..c02ac5f4 100644 --- a/style-guide/about-style-guide.md +++ b/style-guide/about-style-guide.md @@ -99,7 +99,7 @@ Also, avoid creating too many project-specific terms. Where possible, use the terms that are standard for your industry to avoid confusion. Ideally, you can inherit or defer to term definitions from a more authoritative glossary source. -This section includes a table to highlight or call out any terms that are unique +This section includes a table to highlight terms that are unique to your project, or which conflict with your default style guide. For example, the Google Developer's Guide uses "open source" but our project prefers "open-source" when used as a modifier, as in "open-source software."