Pr 285 clarify faded example

[morskyjezek]

If this pull request addresses an open issue on the repository, please add 'Closes #NN' below, where NN is the issue number.

Responds to #285 by clarifying the faded example challenge introduction, the question, and the explanation of the solution.

Please briefly summarise the changes made in the pull request, and the reason(s) for making these changes.

Responds by clarifying the faded example challenge introduction, the question, and the explanation of the solution.

I'd request a review by other maintainers prior to merging this PR, though if it is outstanding after a month with no objections, I will merge it.

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/LibraryCarpentry/lc-shell/compare/md-outputs..md-outputs-PR-306

The following changes were observed in the rendered markdown documents:

 05-counting-mining.md | 12 ++++++++----
 md5sum.txt            |  2 +-
 2 files changed, 9 insertions(+), 5 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2026-09-19 16:19:36 +0000