chore(pre-commit): ✏️ automatic fixes

Author: pre-commit-ci[bot]

CONTRIBUTING.md

@@ -78,7 +78,7 @@ Making videos (on Linux) is done using
 1280x720), [OpenShot](https://www.openshot.org/) (to edit the video if
 necessary), and the below command to reduce the video file size:
 
-```         
+```
 ffmpeg -i input.mp4 -crf 28 output.mp4
 ```
 

DESCRIPTION

@@ -3,7 +3,7 @@ Version: 1.0
 Package: guides
 URL: https://github.com/rostools/guides/, https://guides.rostools.org
 Encoding: UTF-8
-Imports: 
+Imports:
     downlit,
     dplyr,
     ggplot2,
@@ -15,5 +15,5 @@ Imports:
     tidyr,
     usethis,
     xml2
-Remotes:  
+Remotes:
     rostools/r3admin

_extensions/rostools/r3-theme/_extensions/quarto-ext/fontawesome/assets/css/all.css

@@ -6700,7 +6700,7 @@ readers do not read off random characters that represent icons */
 .fa-centos:before {
   content: "\f789"; }
 
-.fa-adn:before {
+.fa-and:before {
   content: "\f170"; }
 
 .fa-cloudsmith:before {
@@ -7291,7 +7291,7 @@ readers do not read off random characters that represent icons */
 .fa-spotify:before {
   content: "\f1bc"; }
 
-.fa-optin-monster:before {
+.fa-option-monster:before {
   content: "\f23c"; }
 
 .fa-fly:before {

_extensions/rostools/r3-theme/_extensions/quarto-ext/fontawesome/assets/css/all.min.css

@@ -37,4 +37,3 @@ editor:
   markdown:
     wrap: 72
     canonical: true
-

_quarto.yml

@@ -63,14 +63,14 @@ always check with:
 usethis::gh_token_help()
 ```
 
-```         
+```
 • GitHub host: 'https://github.com'
 • Personal access token for 'https://github.com': <unset>
 • To create a personal access token, call `create_github_token()`
 • To store a token for current and future use, call `gitcreds::gitcreds_set()`
 ℹ Read more in the 'Managing Git(Hub) Credentials' article:
   https://usethis.r-lib.org/articles/articles/git-credentials.html
-  
+
 ```
 
 The output is saying the token is `<unset>`, which means we need to make

connect-github.qmd

@@ -153,9 +153,9 @@ has lots of great resources explaining the why and how of live-coding:
         You could add new lines like:
 
         ``` r
-        ggplot(NHANES, 
-               aes(x = BMI, 
-                   y = Age, 
+        ggplot(NHANES,
+               aes(x = BMI,
+                   y = Age,
                    colour = Diabetes)) +
             geom_point()
         ```
@@ -237,15 +237,15 @@ has lots of great resources explaining the why and how of live-coding:
 ## After the workshop
 
 After the workshop we always do a "workshop and instructor debrief". During
-this time, we go over what worked and what could be improved on for the 
+this time, we go over what worked and what could be improved on for the
 workshop. It's also a time to give peer feedback. Workshops aren't just a
 source of learning for the participants, but also for the instructors!
-During the debrief we'll each say one thing each of us should continue 
+During the debrief we'll each say one thing each of us should continue
 doing and two things that they could improve on.
 
 So, while you are teaching or helping out, keep note of any feedback or
 comments you could give to improve the other instructors' (and your own)
-teaching. 
+teaching.
 
 ## Resources
 
@@ -254,4 +254,3 @@ teaching.
 
 -   [Carpentries: Tips for
     instructors](https://docs.carpentries.org/topic_folders/hosts_instructors/instructor_tips.html)
-

instructors.qmd

@@ -49,7 +49,7 @@
     Science](https://bookdown.org/rdpeng/rprogdatascience/): Great
     overview of using R for Data Science, with more of a focus on the
     programming side of things
--   [rstats.wtf](https://rstats.wtf/): What They Forgot to Teach You 
+-   [rstats.wtf](https://rstats.wtf/): What They Forgot to Teach You
     About R, a book on more advanced topics in R.
 -   [Data Science](https://datasciencebook.ca/): A book on data science
     using R, with a focus on the tidyverse.

learning.qmd

@@ -25,12 +25,12 @@ there to see how to use that package to streamline admin tasks.
 
 The function `r3admin::admin_create_planning_issue()` in the r3admin
 package creates an issue to help manage the workshop that includes
-a checklist of things to do. Check the r3admin package for documentation 
+a checklist of things to do. Check the r3admin package for documentation
 on it. A basic checklist to prepare for or have for the workshop is:
 
 -   Bring colourful origami hats (for the laptops) or post-it notes
     for participants to let us know how they are doing. Either one you
-    use, find very bright colours for them, like bright blue and bright 
+    use, find very bright colours for them, like bright blue and bright
     orange.
 
 -   Check that participants completed the pre-workshop tasks
@@ -41,7 +41,7 @@ on it. A basic checklist to prepare for or have for the workshop is:
 
 -   If there is group work, keep group size to 2 learners per group. Any
     more and they end up starting to split into smaller groups within
-    the group. 
+    the group.
 
     -   If there are groups, randomize it so participants go with random
         people. Since workshops are also a chance to network and meet new
@@ -84,7 +84,7 @@ on it. A basic checklist to prepare for or have for the workshop is:
     they don't finish).
 
 -   Use a timer set to 45-50 minutes throughout the workshop, so that we can
-    have regular, short 5 minute breaks. Using a timer will force us to 
+    have regular, short 5 minute breaks. Using a timer will force us to
     remember this.
 
 ## End of the workshop
@@ -95,7 +95,7 @@ on it. A basic checklist to prepare for or have for the workshop is:
 
 -   Always do a workshop debrief with all the instructors on what
     worked and what could be improved after the workshop finishes. It's
-    also a time to give peer feedback. See the 
+    also a time to give peer feedback. See the
     [instructor](instructors.qmd#after-the-workshop) section for more details.
 
 ## General workshop admin