full review post-trial 02

[avallecam]

This PR aims to collect edit suggestions from trial 02

Fix #50
Fix #37
Fix #52
Fix #57
Fix #53
Fix #51
Fix #54

[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/compare/md-outputs..md-outputs-PR-47

The following changes were observed in the rendered markdown documents:

 create-forecast.md                                 | 172 ++++++++++++---------
 data-severity-static.R                             |  17 +-
 ...-forecast-rendered-unnamed-chunk-10-1.png (new) | Bin 0 -> 10137 bytes
 ...-forecast-rendered-unnamed-chunk-12-1.png (new) | Bin 0 -> 8226 bytes
 fig/create-forecast-rendered-unnamed-chunk-4-1.png | Bin 50555 -> 50085 bytes
 ...e-forecast-rendered-unnamed-chunk-8-1.png (new) | Bin 0 -> 18492 bytes
 fig/pkgs-hexlogos-2.png (new)                      | Bin 0 -> 622072 bytes
 md5sum.txt                                         |   6 +-
 reference.md                                       |  14 +-
 severity-static.md                                 |  35 +++--
 10 files changed, 141 insertions(+), 103 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 2024-04-30 11:51:00 +0000

[avallecam]

@Degoot-AM can we have your brief review of the edits post-trial 02

[Degoot-AM]

Hi @avallecam, I enjoyed reading two episodes: forecasting and severity measurement. I added a few changes to improve the readability.