add edits from update after delivery

[avallecam]

• Please check if the PR fulfills these requirements

• I have read the CONTRIBUTING guidelines
• Checks have been run locally and pass
• No output errors in the Rendered Changes link generated by github-actions

[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/epiverse-trace/tutorials-middle-fr/compare/md-outputs..md-outputs-PR-7

The following changes were observed in the rendered markdown documents:

 ...ransmissibility-rendered-unnamed-chunk-10-1.png | Bin 69542 -> 57539 bytes
 ...ssibility-rendered-unnamed-chunk-12-1.png (new) | Bin 0 -> 9543 bytes
 ...ssibility-rendered-unnamed-chunk-19-1.png (new) | Bin 0 -> 28915 bytes
 ...ssibility-rendered-unnamed-chunk-20-1.png (new) | Bin 0 -> 32562 bytes
 ...transmissibility-rendered-unnamed-chunk-5-1.png | Bin 5925 -> 5127 bytes
 ...issibility-rendered-unnamed-chunk-8-1.png (new) | Bin 0 -> 13223 bytes
 md5sum.txt                                         |   2 +-
 quantify-transmissibility.md                       | 142 ++++++++++++---------
 8 files changed, 83 insertions(+), 61 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 2025-09-29 18:49:43 +0000