summaryrefslogtreecommitdiff
path: root/docs/dev/how_to/releasing_chef_infra.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/dev/how_to/releasing_chef_infra.md')
-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 74198ef459..10feeb53a4 100644
--- a/docs/dev/how_to/releasing_chef_infra.md
+++ b/docs/dev/how_to/releasing_chef_infra.md
@@ -12,7 +12,7 @@
### Write the release notes
-The importance of our release notes cannot be understated. As developers we understand changes between releases and we're accustomed to reading git history. Users are not and if don't call out new functionality they will not find it on their own. We need to take the time and effort to write quality release notes that give a compelling reason to upgrade and also properly warn of any potential breaking changes. Make sure to involve the docs team so we can make sure our English is legible.
+The importance of our release notes cannot be understated. As developers, we understand changes between releases and we are accustomed to reading git history. Users are not, and if we don't call out new functionality, they will not find it on their own. We need to take the time and effort to write quality release notes that give a compelling reason to upgrade and also properly warn of any potential breaking changes. Make sure to involve the docs team so we can make sure our English is legible.
#### Overall Release Notes Structure