consistent use of "

Author: nuest

nl/workshop1.md

@@ -15,7 +15,7 @@ redirect_from:
 
 On the 30th of May 2024, the CODECHECK-NL team organised its first roadshow event in Delft. The event marks the beginning of a series of four workshops to be conducted across the Netherlands, where we carry out live codechecks with authors and reviewers, while also training a new batch of codecheckers across universities in the Netherlands.
 
-The Delft event kicked off in the morning with 20 participants and members of the CODECHECK-NL team. We began with a short introduction to the  project and its scope by Frank Ostermann (PI for the project, based at the University of Twente), followed by an introduction to codechecking by Stephen Eglen, one of the founders of CODECHECK, and a computational neuroscientist based at the University of Cambridge. Stephen's presentation (which can be found [here](https://sje30.github.io/talks/2024/codecheck2024-02.html)) introduced the philosophy behind codecheck, and the importance of the concept of “good enough” in facilitating code reproducibility. The introduction was followed by a live demo codecheck, conducted on a project submitted by Filip Surma of Delft University of Technology. Curious to see what a CODECHECK certificate looks like? See Filip's certificate [here](https://zenodo.org/records/11403956).
+The Delft event kicked off in the morning with 20 participants and members of the CODECHECK-NL team. We began with a short introduction to the  project and its scope by Frank Ostermann (PI for the project, based at the University of Twente), followed by an introduction to codechecking by Stephen Eglen, one of the founders of CODECHECK, and a computational neuroscientist based at the University of Cambridge. Stephen's presentation (which can be found [here](https://sje30.github.io/talks/2024/codecheck2024-02.html)) introduced the philosophy behind codecheck, and the importance of the concept of "good enough" in facilitating code reproducibility. The introduction was followed by a live demo codecheck, conducted on a project submitted by Filip Surma of Delft University of Technology. Curious to see what a CODECHECK certificate looks like? See Filip's certificate [here](https://zenodo.org/records/11403956).
 
 Following lunch and the successful codecheck of Filip's project, in collaboration with the participants, in the afternoon we moved into breakout sessions, codechecking three more projects in smaller groups, with authors also present during the process. Three more successful codechecks later, participants had a much clearer picture of what codechecks are, how the process works, and how easy or difficult it can be to run or reuse someone else's code!
 
@@ -32,7 +32,7 @@ Do you find the topics of code reuse, reproducibility and learning a hands-on sk
 As part of our newly launched NWO project [CHECK-NL](https://codecheck.org.uk/nl/), **we are looking for
 researchers from the field of engineering at a Dutch knowledge
 institution or university who would like their papers or projects to
-be “codechecked” during a live, one-day code-checking workshop on 30th
+be "codechecked" during a live, one-day code-checking workshop on 30th
 May 2024**, at the X-building in TU Delft.  A codecheck is a light-touch independent peer review to
 check that your code and data can generate the computational results
 in your paper or project (see more details [here](https://codecheck.org.uk/process/)).

nl/workshop2.md

@@ -21,7 +21,7 @@ We wrapped up the day with an interesting reflection session. Along with the aut
 
 ## CALL FOR PAPERS/PREPRINTS/CODE: Are you a researcher in geosciences/environmental sciences interested in reproducible code and Open Science? We have the perfect opportunity for you!
 
-As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the field of geosciences/environmental sciences based at a Dutch knowledge institution or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 26 September 2024** at the University of Twente.  A codecheck is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project (see more details [here](https://codecheck.org.uk/process/)).
+As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the field of geosciences/environmental sciences based at a Dutch knowledge institution or university who would like their papers or projects to be "codechecked" during a live, one-day code-checking workshop on 26 September 2024** at the University of Twente.  A codecheck is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project (see more details [here](https://codecheck.org.uk/process/)).
 
 You can participate as a codechecker (i.e., a person reviewing code), or by submitting your own work to be checked (or both if you are up for it!). *Curious to know how it works? Read about our first [workshop in Delft](https://codecheck.org.uk/nl-workshop1/).*
 

nl/workshop3.md

@@ -27,7 +27,7 @@ We ended the session with a well-deserved borrel, a satisfying end to a producti
 
 **Are you from the social/behavioural sciences and interested in reproducible code and open science? We have the perfect opportunity for you!**
 
-As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the social and behavioural sciences at a Dutch knowledge institution or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 28 November 2024.** A [codecheck](https://codecheck.org.uk/process/) is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project.
+As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the social and behavioural sciences at a Dutch knowledge institution or university who would like their papers or projects to be "codechecked" during a live, one-day code-checking workshop on 28 November 2024.** A [codecheck](https://codecheck.org.uk/process/) is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project.
 
 You can participate (a) by submitting your own work to be checked, (b) as a codechecker (that is, a person reviewing code as a participant in the workshop), or (c) both, if you are up for it! Read on to see how…
 

nl/workshop4.md

@@ -22,7 +22,7 @@ As always, the reflection session with participants helped us understand how the
 
 **Are you from the Digital Humanities and interested in reproducible code and open science? We have the perfect opportunity for you!**
 
-As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the Digital Humanities at a Dutch knowledge or university who would like their papers or projects to be “codechecked” during a live, one-day code-checking workshop on 14 February 2025 at Leiden University**. A [codecheck](https://codecheck.org.uk/process/) is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project.
+As part of our NWO project [CHECK-NL](https://codecheck.org.uk/nl), **we are looking for researchers from the Digital Humanities at a Dutch knowledge or university who would like their papers or projects to be "codechecked" during a live, one-day code-checking workshop on 14 February 2025 at Leiden University**. A [codecheck](https://codecheck.org.uk/process/) is a light-touch independent peer review to check that your code and data can generate the computational results in your paper or project.
 
 You can participate as (a) by submitting your own work to be checked, (b) a codechecker (i.e., a person reviewing code as a participant in the workshop), or (c) both, if you are up for it! Read on to see how…
 

nl/wrap-up.md

@@ -60,7 +60,7 @@ Participants got the chance to learn from other people's workflows and software
 
 Another surprise was how difficult it still is to convince colleagues to submit their work to a reproducibility check.
 The social layer of this otherwise rather technical question is the biggest challenge for the project team and people working with reproducibility checks.
-The technological challenges are less exciting than the positive experiences and potential benefits, see e.g., [this blog post](https://blog.esciencecenter.nl/my-experience-of-getting-codechecked-39cf612cfd35) about an author's experience how it is to be “codechecked”.
+The technological challenges are less exciting than the positive experiences and potential benefits, see e.g., [this blog post](https://blog.esciencecenter.nl/my-experience-of-getting-codechecked-39cf612cfd35) about an author's experience how it is to be "codechecked".
 
 From discussions we distilled the notion that the best time to get a reproducibility check is at the preprint stage or during peer review - then people are still motivated to fix issues before the publication.
 Also, a certificate is a positive signal towards peer reviewers (at least that's what we hope).