Review tutorials early#230
Conversation
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:
Rendered Changes🔍 Inspect the changes: https://github.com/epiverse-trace/tutorials-early/compare/md-outputs..md-outputs-PR-230 The following changes were observed in the rendered markdown documents: 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-06-18 20:06:13 +0000 |
avallecam
left a comment
There was a problem hiding this comment.
thanks for edits! now all rebased including some of comments in word file. waiting for workflows to merge.
This PR makes several edits to the Clean case data (
episodes/clean-data.Rmd), Validate case data (episodes/validate.Rmd) and Aggregate and visualize (episodes/describe-cases.Rmd) episodes.This PR is part of the review of Epiverse tutorials for the upcoming Outbreak Analytics and Applied Modelling in R short course (Week 1).
Please feel free to revert any changes in this PR that you disagree with.
Edits to the 3 tutorials included in Week 1 of the Outbreak Analytics and Applied Modelling in R short course. Changes include some fixes to spelling and grammar, improved consistency and clarity. There were a few bug fixes/typos in the code chunks.
What is the issue you are addressing?
If contributing new additional material please explain why you think it is needed
Any new text in the 3 tutorials reviewed is aimed at improving the clarity of the content being read by the learners.