X-Git-Url: https://review.fuel-infra.org/gitweb?a=blobdiff_plain;f=README.md;h=efea96351c56774ad35b0906682abd2daf584664;hb=31a4535a58df874d773a2b56019a8bf49b868bb7;hp=9c2ded4b12abc33c40ae8ce23378e85f7512e525;hpb=0fd497d58b47e48f830a8fcea49e37d8df65930b;p=puppet-modules%2Fpuppetlabs-apt.git

diff --git a/README.md b/README.md
index 9c2ded4..efea963 100644
--- a/README.md
+++ b/README.md
@@ -91,7 +91,8 @@ class { 'apt':
   },
 }
 ```
-When `Exec['apt_update']` is triggered, it will generate a `Notice` message. Because the default [logging level for agents](https://docs.puppet.com/puppet/latest/configuration.html#loglevel) is `notice`, this will cause the repository update to appear in logs and agent reports. Some tools, such as [The Foreman](https://www.theforeman.org), report the update notice as a significant change. By setting the [loglevel](https://docs.puppet.com/puppet/latest/metaparameter.html#loglevel) metaparameter for `Exec['apt_update']` above the agent logging level, one can eliminate these updates from reports:
+When `Exec['apt_update']` is triggered, it generates a `Notice` message. Because the default [logging level for agents](https://docs.puppet.com/puppet/latest/configuration.html#loglevel) is `notice`, this causes the repository update to appear in logs and agent reports. Some tools, such as [The Foreman](https://www.theforeman.org), report the update notice as a significant change. To eliminate these updates from reports, set the [loglevel](https://docs.puppet.com/puppet/latest/metaparameter.html#loglevel) metaparameter for `Exec['apt_update']` above the agent logging level:
+
 ```puppet
 class { 'apt':
   update => {