summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2019-06-11 14:10:37 -0700
committerGitHub <noreply@github.com>2019-06-11 14:10:37 -0700
commita1dc4a69815c8e4060be021b30dec368b01bc6d9 (patch)
tree313d4492a34f63ab4452789619232158bc7a16e4
parent81b44518275dfa77fb539b5ba9808f808d762eac (diff)
downloadchef-a1dc4a69815c8e4060be021b30dec368b01bc6d9.tar.gz
Update docs/dev/how_to/releasing_chef_infra.md
Signed-off-by: Tim Smith <tsmith@chef.io> Co-Authored-By: mjingle <mjingle@users.noreply.github.com>
-rw-r--r--docs/dev/how_to/releasing_chef_infra.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/dev/how_to/releasing_chef_infra.md b/docs/dev/how_to/releasing_chef_infra.md
index b55b223660..022cb6d3ef 100644
--- a/docs/dev/how_to/releasing_chef_infra.md
+++ b/docs/dev/how_to/releasing_chef_infra.md
@@ -50,7 +50,7 @@ or for a previous release branch:
We want to make sure to announce the build on Discourse. It is helpful that these announcements come from real people because people like people and not machines. You can copy a previous release announcement, and change the version numbers and release notes content.
-Also make sure to announce the build in any social media platforms you present on if you feel comfortable doing so. It's great to announce it in `#sous-chefs` and `#general` in Community Slack as well as on Twitter where we tend to get a good response.
+Also, make sure to announce the build on any social media platforms that you occupy if you feel comfortable doing so. It's great to make an announcement in `#sous-chefs` and `#general` in Community Slack, as well as on Twitter, where we tend to get a good response.
### Update homebrew Content