small typos and modif in guidelines jc

Author: jchiquet

site/guidelines-authors.qmd

@@ -25,7 +25,7 @@ The [Computo](https://github.com/computorg) organization provides template repos
 
 ### Setup a git repository {#sec-git}
 
-Setup a new github repository by going on the URL of either the R or Python or Julia template repository and clicking on the **"use this template"** button on the top of the page, as illustrated in @fig-template.
+Setup a new Github repository by going on the URL of either the R or Python or Julia template repository and clicking on the **"use this template"** button on the top of the page, as illustrated in @fig-template.
 
 ![Screenshot of the R Computo template GitHub page.](/assets/img/computo-template-screenshot.png){#fig-template width="100%"}
 
@@ -82,7 +82,7 @@ To build your document (both in PDF and HTML by default), you can run the comman
 
 ```bash
 # will render both to html and PDF
-quarto render template-computo-{R,python,julia}.qmd
+quarto render
 ```
 
 #### Metadata of your contribution
@@ -195,7 +195,7 @@ Next, as illustrated in @fig-deploy, under `Settings > Pages` on the webpage of
 
 ![Deploy your website with GitHub Actions](/assets/img/2025-03-20-revised-github-process/depoy-github.png){#fig-deploy width="100%"}
 
-Authors can find more detailed about Computo's workflow in @sec-workflow.
+Authors can find more details about Computo's workflow in @sec-workflow.
 
 ::: {.callout-note title="Compatibility with old reproducibility system"}
 You can safely delete the `gh-pages` branch if you have one, as we don't need anymore to push the HTML files to the site.
@@ -205,15 +205,15 @@ You can safely delete the `gh-pages` branch if you have one, as we don't need an
 
 While you should have by now handled R, Python or Julia package dependencies using appropriate tools that register environments and version numbers, some of the packages your work depend upon might require external *system* dependencies that must be installed either when setting up the environment in the GitHub runner or when taking care of the paper rendering or in both cases. To take care of that, you can add and customize two scripts at the root of your repository. Specifically:
 
-- `setup-env-ci.sh` is meant to install system dependencies required to set up the environment in the GitHub runner. Here is an example of such a file taken from @giorgi2024:
+- `setup-env-ci.sh` is meant to install system dependencies required to set up the environment in the GitHub runner. Here is an example of such a file taken from a published article:
 
 ```bash
 # The CI runs on Linux Ubuntu, here goes system dependencies
 # needed at environment setup step
 sudo apt-get install -y libcurl4-openssl-dev
 ```
 
-- `setup-render-ci.sh` is meant to install system dependencies required for rendering the paper, like plotting software or running a script to generate data. Here is an example of such a file taken from @giorgi2024:
+- `setup-render-ci.sh` is meant to install system dependencies required for rendering the paper, like plotting software or running a script to generate data. Here is an example of such a file taken from a published article:
 
 ```bash
 # The CI runs on Linux Ubuntu, here goes system dependencies
@@ -222,12 +222,12 @@ sudo apt-get install -y libblas-dev liblapack-dev
 ```
 
 ::: {.callout-warning title="Ubuntu GitHub runner"}
-Remember that the GitHub runner uses Linux Ubuntu and therefore software installation is achieved through `apt-get`. Furthermore, you should prepend calls to `apt-get` with the `sudo` word to specify that you want to execute this command as administrator of the machine.
+Remember that the GitHub runner uses Linux Ubuntu and therefore software installation is achieved through `apt-get`. Furthermore, you must precede calls to `apt-get` with the word `sudo` to indicate that you wish to run this command as an administrator.
 :::
 
 ### Submit your manuscript {#sec-submitting}
 
-Once you are done writing your contribution, recall that you can render it in both HTML and PDF by running `quarto render .` from a terminal within the folder in which you cloned the Computo template.
+Once you are done writing your contribution, recall that you can render it in both HTML and PDF by running `quarto render` from a terminal within the folder in which you cloned the Computo template.
 
 If the Quarto rendering is successful locally (hence you get both HTML and PDF files), then, once you push the last modification to your repository on GitHub, the continuous integration and deployment scripts should automatically run and, if successful, the HTML version of your contribution will be published online, as well as a PDF version (see "Other format" at the end of the table of content of the rendered HTML).
 
@@ -326,13 +326,13 @@ Authors simply use the `build.yml` workflow in their repository to trigger the c
 
 ### Reproducing an existing paper published in Computo
 
-Our publication workflow makes it very easy for anyone to reproduce a given paper. To do that, you can first clone the repository. Then you need to install Quarto and the Computo Quarto extension in the `published-202412-giorgi-efficient` folder that the cloning step made. Finally, you can render the document. In summary, you do that with the following commands:
+Our publication workflow makes it very easy for anyone to reproduce a given paper. Consider for instance the paper <https://doi.org/10.57750/sfxn-1t05> associated with the Github repository [published-202412-giorgi-efficient][https://github.com/computorg/published-202412-giorgi-efficient]. You first need to clone the repository. Then you need to install Quarto and the Computo Quarto extension in the `published-202412-giorgi-efficient` folder that the cloning step made. Finally, you can render the document. In summary, you do that with the following commands:
 
 ```bash
 git clone https://github.com/computorg/published-202412-giorgi-efficient.git
 cd published-202412-giorgi-efficient
 quarto add computorg/computo-quarto-extension
-quarto render .
+quarto render
 ```
 
 ## Computo's code of ethics {#sec-ethics}
@@ -367,4 +367,3 @@ Copyright/author's right/license compliance
 
 : Authors guarantee that they comply with the usage license of any third party contents/works (code, software, data, figures/images, documents, etc.) that were used to produce their work.
 
-## References