aboutsummaryrefslogtreecommitdiff
path: root/content/go-brand.article
diff options
context:
space:
mode:
authorNathan Youngman <git@nathany.com>2018-04-28 03:22:25 +0000
committerSteve Francia <spf@golang.org>2018-04-28 18:34:28 +0000
commit8a50814fd77e1d71e99503d3e0c41b8d466f8138 (patch)
treec74a147094af02b2aefc2cbc0edd20f1389d794f /content/go-brand.article
parentba39ac5dc54ac8b5b86cd56b8935ff70c37f4076 (diff)
content/go-brand: minor grammar improvements
Change-Id: Ib7c3f3b40fe572ef32afbf6b8d62ef22150079d6 Change-Id: Ib7c3f3b40fe572ef32afbf6b8d62ef22150079d6 GitHub-Last-Rev: e49dd40d1f636412a670456cf174129d2a27c000 GitHub-Pull-Request: golang/blog#14 Reviewed-on: https://go-review.googlesource.com/110116 Reviewed-by: Steve Francia <spf@golang.org>
Diffstat (limited to 'content/go-brand.article')
-rw-r--r--content/go-brand.article6
1 files changed, 3 insertions, 3 deletions
diff --git a/content/go-brand.article b/content/go-brand.article
index f1e0cbb..ade49ff 100644
--- a/content/go-brand.article
+++ b/content/go-brand.article
@@ -38,7 +38,7 @@ revisions we went through…
The brand guide establishes the mission, values and voice for the Go project. In
general terms, a brand guide is a reference tool for establishing a consistent
-brand identity. It is sometimes referred to as a “brand guidelines” or a “brand
+brand identity. It is sometimes referred to as “brand guidelines” or a “brand
book”. It is a single document that serves as a guide and reference to
designers, writers, and developers to create consistent, on-brand content.
@@ -85,6 +85,6 @@ The brand guide contains the guidelines for acceptable logo use.
The website will be getting a refresh based on the new design. Since we are
making significant changes, we are also taking this opportunity to update our
-website infrastructure to support internationalization and multilingual to
-better serve our global community. The migration will happen in stages over the
+website infrastructure to better serve our global community with internationalization
+and multilingual support. The migration will happen in stages over the
next few months starting with this blog.