The provided markdown filename in the "Example" link does not match the actual example file; the path is different, the filename is different, and the file extension is different.
This change updates the path/name/extension used in the markdown link so that prospective users can follow the link instead of getting a 404 error from GitHib, but the example file name and extension does not match what the rest of the text refers to. (In the text the file is referred to as "deamon-config" with extension "yaml" but the example uses the name "daemon-conf" instead of -config and the extension "yml") (Disregarding the "example" portion of the latter file name)) It would probably be more intuitive if the example file matched the naming convention used in the text.
The provided markdown filename in the "Example" link does not match the actual example file; the path is different, the filename is different, and the file extension is different.
This change updates the path/name/extension used in the markdown link so that prospective users can follow the link instead of getting a 404 error from GitHib, but the example file name and extension does not match what the rest of the text refers to. (In the text the file is referred to as "deamon-config" with extension "yaml" but the example uses the name "daemon-conf" instead of -config and the extension "yml") (Disregarding the "example" portion of the latter file name)) It would probably be more intuitive if the example file matched the naming convention used in the text.