Skip to content

Conversation

@jhudsl-robot
Copy link
Collaborator

Using the spell check results from the last closed PR to make an arbitrary change to retrigger actions. @susannasiebert could you merge this if it looks good?

@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2025

OTTR Check Results

Summary

  • Spelling check: ❌ FAILED (1 errors found, threshold: 0)
  • URL check: ✅ PASSED (0 errors found, threshold: 0)

⚠️ Some Checks Failed Click here to download detailed error reports

Last Updated: 2025-12-04-18:37:47

Copy link
Contributor

@susannasiebert susannasiebert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2025

Re-rendered previews from the latest commit:

* note not all html features will be properly displayed in the "quick preview" but it will give you a rough idea.

Updated at 2025-12-04 with changes from the latest commit da2f790

@susannasiebert
Copy link
Contributor

@jhudsl-robot I had a look at the preview and it doesn't show the updates. Would you still like me to go ahead and merge it?

@jhudsl-robot
Copy link
Collaborator Author

@susannasiebert I see the updated spelling of "appropriate" in both the quick preview and the comprehensive download preview linked within this PR:
image

So yes, please merge it

@jhudsl-robot
Copy link
Collaborator Author

There is also another typo that the spell check flags in the PR (#40 (comment)) if you want to update that first:
image

@susannasiebert
Copy link
Contributor

ok, I feel really dumb right now but I've been editing the md files in the docs folder, not the Rmd file in the main folder. So of course my updates didn't work. My apologies but it's been a couple of years since I updated the course and I got things mixed up. Let me make a new PR with the updates to the correct files and I can make the typo fixes there as well.

@jhudsl-robot
Copy link
Collaborator Author

@susannasiebert No worries at all! I just noticed that as well reading the issue again and realizing that the preview in this PR didn't have the updated language to the introduction you mentioned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants