Merge pull request #74 from UN-Task-Team-for-Scanner-Data/how-to-start-amendment-1

Change in wording of how-to-start

Author: ONSBen

docs/reproducibility-guidance/how-to-start.qmd

@@ -61,15 +61,15 @@ Although this may feel like a foray away from research and into software develop
 
 ## Checklist
 
-Rather than a strictly-defined list of requirements, this is intended to provide suggestions for how you can improve your project with RAP principles. You're encouraged to consider the objective of your work and then determine which suggestions best support those objectives.
+Rather than a strictly-defined list of requirements, this list is intended to provide a checklist of suggestions for how you can improve your project with RAP principles. You're encouraged to consider the objective of your work and then determine which suggestions best support those objectives. Remember that any effort to make a paper replicable, however small, can turn an interesting paper and a vital reference tool for future researchers.
 
 ### Baseline
 
 -   [ ] Make the code available online. GitHub is free and considered the best option, but using an institution's website, or even a public blog, is better than nothing.
 
 -   [ ] Use a widely-accepted language, ideally an open-source one. R and Python are both free and widely used, and using a commonly-understood language makes the code more accessible.
 
--   [ ] Make input data available online when possible. Zenodo is a free-to-use option. You can also use existing open datasets if you don't want to go through the hastle of making your data availible.
+-   [ ] Make input data available online when possible. Zenodo is a free-to-use option. You can also use existing open datasets if you can't or don't wish to go through the process of making your data availible.
 
 -   [ ] Make documentation explaining the code and data available online. These should be sufficient for a user to repeat the analysis.
 
@@ -93,4 +93,4 @@ Rather than a strictly-defined list of requirements, this is intended to provide
 
 -   [ ] The explanatory documentation covers major changes over time (e.g., Semantic Versioning).
 
--   [ ] The project is automated end-to-end, including the writeup of the paper published alongside the code. In essense, it is clear how each figure and table in the paper was generated.
+-   [ ] The project is automated end-to-end, including the writeup of the paper published alongside the code. In essense, it is clear how each figure and table in the paper was generated.