Improve formatting to streamline translation

Thank you!

Thank you for your pull request :smiley:

:robot: 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:

:dart: correct output
:framed_picture: correct figures
:question: new warnings
:bangbang: new errors

Rendered Changes

:mag: Inspect the changes: https://github.com/epiverse-trace/tutorials-middle/compare/md-outputs..md-outputs-PR-103

The following changes were observed in the rendered markdown documents:

 config.yaml (new)                                  |   86 +
 create-forecast.md                                 |   47 +-
 ...create-forecast-rendered-unnamed-chunk-10-1.png |  Bin 9599 -> 9606 bytes
 ...create-forecast-rendered-unnamed-chunk-13-1.png |  Bin 8495 -> 8618 bytes
 fig/create-forecast-rendered-unnamed-chunk-4-1.png |  Bin 49923 -> 49388 bytes
 md5sum.txt                                         |    4 +-
 renv.lock (new)                                    | 2419 ++++++++++++++++++++
 severity-static.md                                 |   16 +-
 8 files changed, 2544 insertions(+), 28 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.

:stopwatch: Updated at 2024-07-03 10:47:56 +0000

epiverse-trace / tutorials-middle

Improve formatting to streamline translation #103

Thank you!

Rendered Changes