summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Smith <tsmith@chef.io>2020-06-17 10:58:41 -0700
committerGitHub <noreply@github.com>2020-06-17 10:58:41 -0700
commit0ee3957c6f3cbbbf1eb2d65091274406fb9c5746 (patch)
tree61f151a990521bbea853f9011dadbbe395b14e77
parent5b2d689aaabbb9ceafc49e21857844f073557b42 (diff)
downloadchef-0ee3957c6f3cbbbf1eb2d65091274406fb9c5746.tar.gz
Update RELEASE_NOTES.md
Signed-off-by: Tim Smith <tsmith@chef.io> Co-authored-by: Ian Maddaus <IanMadd@users.noreply.github.com>
-rw-r--r--RELEASE_NOTES.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 03e8b6fc70..8425a719a9 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -66,7 +66,7 @@ The `chef_client_scheduled_task` resource has been updated to default the `frequ
### cron / cron_d
-The `cron` and `cron_d` resources have been updated using the new Custom Resource Partials functionality introduced in Chef Infra Client 16. This has allowed us to standardize the properties used to declare cron job timing between the two resources. Timing properties all accept the same types / ranges and include the same validation, which makes moving from `cron` to `cron_d` seamless.
+The `cron` and `cron_d` resources have been updated using the new Custom Resource Partials functionality introduced in Chef Infra Client 16. This has allowed us to standardize the properties used to declare cron job timing between the two resources. The timing properties in both resources all accept the same types and ranges, and include the same validation, which makes moving from `cron` to `cron_d` seamless.
### cron_access