diff options
| author | Tim Smith <tsmith@chef.io> | 2019-06-11 13:20:23 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-06-11 13:20:23 -0700 |
| commit | cfcf16431b3b6dd2fa39e020cfa607fa24038e7d (patch) | |
| tree | 39ec5b6d18e1dc9087f67e3752e6a145aed03ebc | |
| parent | 5b5b10cbeefc219ec92525eb2bbab85fbd221804 (diff) | |
| download | chef-cfcf16431b3b6dd2fa39e020cfa607fa24038e7d.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.md | 2 |
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 dfb9279fd5..d2810fb8c3 100644 --- a/docs/dev/how_to/releasing_chef_infra.md +++ b/docs/dev/how_to/releasing_chef_infra.md @@ -20,7 +20,7 @@ The importance of our release notes cannot be understated. As developers we unde 2. `Updated Resources`: It's important to let users know about new functionality in resources they may already be using. Cover any important bug fixes or new properties/actions here. 3. `Major new features`: Document new features with a high level bullet. This is a great opportunity to show off our work and sell users on new workflows. 4. `Updated InSpec Releases`: We should always call out the updated InSpec release with a description of new functionality included. -5. `Security Updates`: Call out any updated components we're shipping with links to the CVEs if available. +5. `Security Updates`: Call out any updated components we are shipping and include links to the CVEs if available. ### Update the Docs Site |