Add automated spell-check with codespell on PRs and fix existing typos

.codespell-ignore.txt

@@ -0,0 +1,98 @@
+# Project-specific terms and proper nouns for FORRT
+# Add one word per line (case-insensitive by default)
+
+# Project names and acronyms
+CREP
+forrt
+FORRT
+OSF
+
+# Research/Academic terms
+aer
+metascience
+preregistration
+preregistrations
+replicability
+reproducibility
+reprohack
+
+# Names and organizations
+Angelika
+Ans
+Buss
+Carmel
+Hart
+Kathawalla
+Loades
+Loder
+Nam
+Ned
+NWO
+nwo
+Priya
+recognised
+Shepard
+Sherif
+Shepperd
+Soler
+Stefan
+Strack
+Tennant
+Udo
+Yau
+
+# Technical or code related terms
+aCount
+agrc
+blogdown
+Github
+hugo
+netlify
+VSCode
+yaml
+
+# Common acceptable variations
+behaviour
+behavioural
+centre
+colour
+commend
+favour
+grey
+homogenous
+Homogenous
+honour
+organisation
+organise
+organised
+practise
+recognise
+re-use
+re-used
+theses
+visualisation
+
+# Legal/formal terms
+recusal
+recuse
+
+# Additional project-specific terms
+AREN's
+AREN’s
+Didactical
+ND
+OT
+Zenodo
+
+# Hyphenated words that are acceptable
+alpha-numeric
+re-use
+re-used
+
+# Other words/parts of words that the spell checker is incorrectly flagging
+ABl
+ist
+ons
+sie
+tru
+ublication

.codespellrc

@@ -0,0 +1,15 @@
+[codespell]
+# Skip these files and directories
+skip = .git,*.png,*.jpg,*.jpeg,*.gif,*.svg,*.ico,*.woff,*.woff2,*.ttf,*.eot,*.min.js,*.min.css,themes,node_modules,public,resources,static/admin,*.lock,package-lock.json,.hugo_build.lock,go.sum,*.json,*.css,*.scss,*.toml,content/glossary/german,content/glossary/portuguese,content/glossary/arabic,content/glossary/spanish,content/glossary/french,data,*.pdf
+
+# Ignore these words (project-specific terms and proper nouns)
+ignore-words = .codespell-ignore.txt
+
+# Check file names as well
+check-filenames =
+
+# Check hidden files
+check-hidden =
+
+# Exclude certain patterns in files
+ignore-regex = (https?://|www\.|[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Z|a-z]{2,}|<!--.*?-->)

.github/workflows/spell-check.yaml

@@ -0,0 +1,56 @@
+name: Spell Check
+
+# =======================
+# Automated Spell Checking
+# =======================
+# Purpose: Checks for spelling errors in pull requests using codespell
+# Triggers: PR opened, synchronized, or reopened
+# Reports: Comments on PR with potential typos and suggestions
+
+on:
+  pull_request:
+    types: [opened, synchronize, reopened]
+
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  spell-check:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.x'
+
+      - name: Install codespell
+        run: |
+          python -m pip install --upgrade pip
+          pip install codespell
+
+      - name: Run Spell Check Script
+        id: spell_check
+        run: |
+          python scripts/spell_check/check_spelling.py
+
+      - name: Find Comment
+        uses: peter-evans/find-comment@v3
+        id: fc
+        with:
+          issue-number: ${{ github.event.pull_request.number }}
+          comment-author: 'github-actions[bot]'
+          body-includes: Spell Check Results
+
+      - name: Create or update comment
+        uses: peter-evans/create-or-update-comment@v4
+        with:
+          comment-id: ${{ steps.fc.outputs.comment-id }}
+          issue-number: ${{ github.event.pull_request.number }}
+          body: ${{ steps.spell_check.outputs.comment }}
+          edit-mode: replace

CONTRIBUTING.md

@@ -56,7 +56,7 @@ A way to run the project locally without installing Hugo on the host machine is
 2. Open `.devcontainer/devcontainer.json` in VSCode. If you are on a Windows host, go to `.devcontainer\dev\devcontainer.json` and uncomment the line `"remoteUser": "root"` before continuing.
 3. In the context menu of VSCode (Crl + Shift + P), select `Dev Containers: Open Folder in Container`. Alternatively, a pop-up will appear in the bottom right corner of the window asking if you want to open the folder in a container. Click on `Reopen in Container`.
 4. Wait for the container to build. The context of VS Code will change. In the bottom left corner, you will see a green icon with the name of the container (Hugo Dev).
-5. Run `hugo server -D`. The container will foward port 1313 to the host machine, so you can access the website at `http://localhost:1313`.
+5. Run `hugo server -D`. The container will forward port 1313 to the host machine, so you can access the website at `http://localhost:1313`.
 
 ### Development - R-Studio
 

content/about/partnerships/partnerships.md

@@ -209,7 +209,7 @@ classtitle = "text-center"
 <br>
 
 
-<img src="logos/AREN.webp" align="right" alt="The African Reproducibility Network (AREN) logo" /> [The African Reproducibility Network (AREN)](https://africanrn.org/) is a community-led grassroots initiative which seeks to bridge the gaps in open science (OS) across Africa. AREN’s mission is to furnish African researchers with the necessary support and resources through training and workshops tailored to the local context, ensuring they are well-equipped to meet the growing global demand for openness and reproducibility in research. We also seek to establish local networks at universities and research institutes across Africa that will serve as advocay hubs for collaboration and cooperation, providing research communities with the necessary support for adopting and practising OS principles while also ensuring institutions are better prepared to implement OS policies.
+<img src="logos/AREN.webp" align="right" alt="The African Reproducibility Network (AREN) logo" /> [The African Reproducibility Network (AREN)](https://africanrn.org/) is a community-led grassroots initiative which seeks to bridge the gaps in open science (OS) across Africa. AREN’s mission is to furnish African researchers with the necessary support and resources through training and workshops tailored to the local context, ensuring they are well-equipped to meet the growing global demand for openness and reproducibility in research. We also seek to establish local networks at universities and research institutes across Africa that will serve as advocacy hubs for collaboration and cooperation, providing research communities with the necessary support for adopting and practising OS principles while also ensuring institutions are better prepared to implement OS policies.
 
 
 <br>

content/about/steering-committee/index.md

@@ -782,7 +782,7 @@ In FORRT, she has been involved in co-leading Team Citational Politics and is ve
                     <div class="sc-modal-bio">Fotis Mystakopoulos is a professional actively engaged in advancing Open Science. His career trajectory reflects the evolution of information science, from its traditional roots in library services to its modern role in shaping research policy and data infrastructure. With a background in Library and Information Science, he has developed expertise in key areas of scholarly communication, including Responsible Research Assessment, Open Access, Open Science Training, and Research Data Management.
 
 Beyond his formal roles, he is actively engaged in community building, supporting initiatives that connect researchers and professionals around shared values and practices of openness and advocating for cultural change in academia that aligns with the ethos of Open Science.
-Currently, alongside his professional duties, he is pursuing a PhD at the University of West Attica, examining the evolution of academic libraries, and theire services within the expanding global landscape of Open Science.
+Currently, alongside his professional duties, he is pursuing a PhD at the University of West Attica, examining the evolution of academic libraries, and their services within the expanding global landscape of Open Science.
 
 
 

content/authors/fotis-mystakopoulos-phd-student/_index.md

@@ -38,7 +38,7 @@ social:
 Fotis Mystakopoulos is a professional actively engaged in advancing Open Science. His career trajectory reflects the evolution of information science, from its traditional roots in library services to its modern role in shaping research policy and data infrastructure. With a background in Library and Information Science, he has developed expertise in key areas of scholarly communication, including Responsible Research Assessment, Open Access, Open Science Training, and Research Data Management.
 
 Beyond his formal roles, he is actively engaged in community building, supporting initiatives that connect researchers and professionals around shared values and practices of openness and advocating for cultural change in academia that aligns with the ethos of Open Science.
-Currently, alongside his professional duties, he is pursuing a PhD at the University of West Attica, examining the evolution of academic libraries, and theire services within the expanding global landscape of Open Science.
+Currently, alongside his professional duties, he is pursuing a PhD at the University of West Attica, examining the evolution of academic libraries, and their services within the expanding global landscape of Open Science.
 
 
 

content/awop/index.md

@@ -2,6 +2,6 @@
 # FORRT page
 type = "widget_page"
 headless = false  # Homepage is headless, other widget pages are not.
-title = "Academic Wheel of Priviledge (AWoP)"
+title = "Academic Wheel of Privilege (AWoP)"
 # url = "/awop"
 +++

content/coc.md

@@ -26,7 +26,7 @@ Our open community strives to:
 
 -   **Use preferred pronouns (e.g. she/her/hers, they/their/theirs, he/him/his).**
 
--   **Be respectful of differing opinions, viewpoints, and experiences**: Not all of us will agree all the time, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. It is important to demonstrate empathy and kindness toward other people. Please keep in mind that viewpoints and opinions must not interfere with, hinder, or restrain our strongly-held community values on social justice, diversity, equity, inclusion and accessibilty.
+-   **Be respectful of differing opinions, viewpoints, and experiences**: Not all of us will agree all the time, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. It is important to demonstrate empathy and kindness toward other people. Please keep in mind that viewpoints and opinions must not interfere with, hinder, or restrain our strongly-held community values on social justice, diversity, equity, inclusion and accessibility.
 
 -   **Try to understand why we disagree**: Disagreements, both social and technical, happen all the time. It is important that we resolve disagreements and differing views constructively by giving and gracefully accepting constructive feedback. Remember that we’re different. Diversity contributes to the strength of our community, which is composed of people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.
 

content/contributor-analysis/index.Rmd

@@ -74,7 +74,7 @@ dt <- bind_rows(data_list, .id = "Source_Sheet")
 dt <- dt %>%
   select(`Project Name`, everything())
 
-# Remove PM column as it is unncessary and might cause problems with binding
+# Remove PM column as it is unnecessary and might cause problems with binding
 dt <- dt %>%
   select(-`Project Managers`)
 ```

content/contributor-analysis/network-graph.Rmd

@@ -84,7 +84,7 @@ dt <- bind_rows(data_list, .id = "Source_Sheet")
 dt <- dt %>%
   select(`Project Name`, everything())
 
-# Remove PM column as it is unncessary and might cause problems with binding
+# Remove PM column as it is unnecessary and might cause problems with binding
 dt <- dt %>%
   select(-`Project Managers`)
 ```
@@ -171,7 +171,7 @@ ContributorGroups_nodes <- dt_long %>%
 colnames(ContributorGroups_nodes) <- c("id", "projects")
 
 Contributor_nodes <- left_join(Contributor_nodes_n, ContributorGroups_nodes)
-Contributor_nodes$title <- paste0(Contributor_nodes$id,"<br>", gsub(patter = ",", replacement = "<br>", x = Contributor_nodes$projects))
+Contributor_nodes$title <- paste0(Contributor_nodes$id,"<br>", gsub(pattern = ",", replacement = "<br>", x = Contributor_nodes$projects))
 ```
 
 ```{r create-edges}

content/dei/2-intro-text.md

@@ -71,7 +71,7 @@ Hence, we at FORRT, have devised ***4 ways*** to be proactive in the outreach to
 
 * FORRT's ***Open Office Hours***
    - Periodically, and at least once a month, the FORRT community will hold its Open and Reproducible Science *"office hours"* for anyone in the world wishing to learn, adopt, and disseminate open and reproducible science tenets, as well as those with interest or questions about teaching and mentoring these concepts, and/or raising awareness of its pedagogical implications and its associated challenges (e.g., curricular reform, epistemological uncertainty, methods of education).
-   - Please check the [calendar of meetings](#calendar-mentorship) down below. The first meeting will happen Friday, October 30th, 2020. All necessary information should be available in the Google calender, but also feel free to [email us.](mailto:info@forrt.org)
+   - Please check the [calendar of meetings](#calendar-mentorship) down below. The first meeting will happen Friday, October 30th, 2020. All necessary information should be available in the Google calendar, but also feel free to [email us.](mailto:info@forrt.org)
 
 <br>
 

content/glossary/english/plan_s.md

@@ -1,7 +1,7 @@
 {
     "type": "glossary",
     "title": "Plan S",
-    "definition": "Plan S is an initiative, launched in September 2018 by cOAlition S, a consortium of research funding organisations, which aims to accelerate the transition to full and immediate Open Access. Participating funders require recipients of research grants to publish their research in compliant Open Access journals or platforms, or make their work openly and immediately available in an Open Access repository, from 2021 onwards. cOAlition S funders have commited to not financially support ‘hybrid’ Open Access publication fees in subscription venues. However, authors can comply with plan S through publishing Open Access in a subscription journal under a “transformative arrangement” as further described in the implementation guidance. The “S” in Plan S stands for shock.",
+    "definition": "Plan S is an initiative, launched in September 2018 by cOAlition S, a consortium of research funding organisations, which aims to accelerate the transition to full and immediate Open Access. Participating funders require recipients of research grants to publish their research in compliant Open Access journals or platforms, or make their work openly and immediately available in an Open Access repository, from 2021 onwards. cOAlition S funders have committed to not financially support ‘hybrid’ Open Access publication fees in subscription venues. However, authors can comply with plan S through publishing Open Access in a subscription journal under a “transformative arrangement” as further described in the implementation guidance. The “S” in Plan S stands for shock.",
     "related_terms": [
         "Open Access",
         "DORA",

content/glossary/english/pro.md

@@ -1,7 +1,7 @@
 {
     "type": "glossary",
     "title": "PRO (peer review openness) initiative",
-    "definition": "The agreement made by several academics that they will not provide a peer review of a manuscript unless certain conditions are met. Specifically, the manuscript authors should ensure the data and materials will be made publically available (or give a justification as to why they are not freely available or shared), provide documentation detailing how to interpret and run any files or code and detail where these files can be located via the manuscript itself.",
+    "definition": "The agreement made by several academics that they will not provide a peer review of a manuscript unless certain conditions are met. Specifically, the manuscript authors should ensure the data and materials will be made publicly available (or give a justification as to why they are not freely available or shared), provide documentation detailing how to interpret and run any files or code and detail where these files can be located via the manuscript itself.",
     "related_terms": [
         "Non-anonymised peer review",
         "Open Science",

content/glossary/english/research_protocol.md

@@ -1,7 +1,7 @@
 {
     "type": "glossary",
     "title": "Research Protocol",
-    "definition": "A detailed document prepared before conducting a study, often written as part of ethics and funding applications. The protocol should include information relating to the background, rationale and aims of the study, as well as hypotheses which reflect the researchers’ expectations. The protocol should also provide a “recipe” for conducting the study, including methodological details and clear analysis plans. Best practice guidelines for creating a study protocol should be used for specific methodologies and fields. It is possible to publically share research protocols to attract new collaborators or facilitate efficient collaboration across labs (e.g. [https://www.protocols.io/](https://www.protocols.io/)). In medical and educational fields, protocols are often a separate article type suitable for publication in journals. Where protocol sharing or publication is not common practice, researchers can choose preregistration.",
+    "definition": "A detailed document prepared before conducting a study, often written as part of ethics and funding applications. The protocol should include information relating to the background, rationale and aims of the study, as well as hypotheses which reflect the researchers’ expectations. The protocol should also provide a “recipe” for conducting the study, including methodological details and clear analysis plans. Best practice guidelines for creating a study protocol should be used for specific methodologies and fields. It is possible to publicly share research protocols to attract new collaborators or facilitate efficient collaboration across labs (e.g. [https://www.protocols.io/](https://www.protocols.io/)). In medical and educational fields, protocols are often a separate article type suitable for publication in journals. Where protocol sharing or publication is not common practice, researchers can choose preregistration.",
     "related_terms": [
         "Many Labs",
         "Preregistration"

content/glossary/english/type_i_error.md

@@ -1,7 +1,7 @@
 {
     "type": "glossary",
     "title": "Type I error",
-    "definition": "“Incorrect rejection of a null hypothesis” (Simmons et al., 2011, p. 1359), i.e. finding evidence to reject the null hypothesis that there is no effect when the evidence is actually in favouring of retaining the null that there is no effect (For example, a judge imprisoning an innocent person). Concluding that there is a significant effect and rejecting the null hypothesis when your findings actually occured by chance.",
+    "definition": "“Incorrect rejection of a null hypothesis” (Simmons et al., 2011, p. 1359), i.e. finding evidence to reject the null hypothesis that there is no effect when the evidence is actually in favouring of retaining the null that there is no effect (For example, a judge imprisoning an innocent person). Concluding that there is a significant effect and rejecting the null hypothesis when your findings actually occurred by chance.",
     "related_terms": [
         "Frequentist statistics",
         "Null Hypothesis Significance Testing (NHST)",