Fix typos

lmu-osc · Sep 8, 2024 · 2b0eb43 · 2b0eb43
1 parent b0a8339
commit 2b0eb43
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/choose_license.qmd b/choose_license.qmd
@@ -57,7 +57,7 @@ Two other notable definitions include the _Open Definition_ [@OKFN2016], which w
 
 ### Existing License?
 
-First, if you adapt (i.e., modify, build on) a work by others you need to determine if it is provided to you under a free/open license.[You can determine whether a license is free/open by searching for its name in the [SPDX License List](https://spdx.org/licenses/) and looking for at least one `Y` in the two columns _FSF Free/Libre?_ and _OSI Approved?_]{.aside} If yes, we we recommend you to make your contribution available under the same license.^[Copyleft licenses even require you to choose the same or a compatible license.] For example, if you adapt code published in another paper, choose the same license for your modifications. The same applies if there are strong community norms to use a particular free/open license.^[Of course, this is only a heuristic and there might be good reasons to deviate from community norms.] Importantly, as discussed before, you are generally not allowed to adapt a work _not_ published under a free/open license.
+First, if you adapt (i.e., modify, build on) a work by others you need to determine if it is provided to you under a free/open license.[You can determine whether a license is free/open by searching for its name in the [SPDX License List](https://spdx.org/licenses/) and looking for at least one `Y` in the two columns _FSF Free/Libre?_ and _OSI Approved?_]{.aside} If yes, we recommend you to make your contribution available under the same license.^[Copyleft licenses even require you to choose the same or a compatible license.] For example, if you adapt code published in another paper, choose the same license for your modifications. The same applies if there are strong community norms to use a particular free/open license.^[Of course, this is only a heuristic and there might be good reasons to deviate from community norms.] Importantly, as discussed before, you are generally not allowed to adapt a work _not_ published under a free/open license.
 
 ### Work Type?
 

diff --git a/make_readme.qmd b/make_readme.qmd
@@ -6,7 +6,7 @@ engine: knitr
 
 ## Creating a README
 
-Once you have prepared your project and settled on a license, it is time to add a final touch. Imagine you are coming back to your project in five years, having forgotten most of the details of what you did exactly. What would be useful to know in order to quickly understand what is going on in the project? This is what needs to be described in the README. While you could just start writing along, most READMEs have some sections in common which we describe below.
+Once you have prepared your project and settled on a license, it is time to add a final touch. Imagine returning to your project in five years, having forgotten most of the details of what you did exactly. What would be useful to know in order to quickly understand what is going on in the project? This is what needs to be described in the README. While you could just start writing along, most READMEs have some sections in common which we describe below.
 
 Name
 
@@ -22,7 +22,7 @@ Description
 
 Visuals
 
-:   If there is anything you can show that demonstrates how the project can be used? Screenshots or other visuals can make the README more appealing.
+:   Is there anything you can show that demonstrates how the project can be used? Screenshots or other visuals can make the README more appealing.
 
 Installation/Dependencies
 
@@ -100,7 +100,7 @@ Authors
 
 Citation
 
-:   Is there a recommended way to cite this project? We recommend to increase citability by using the [CodeMeta generator](https://codemeta.github.io/codemeta-generator/) to create the file `codemeta.json`. Alternatively, one can also use the R package [`codemetar`](https://docs.ropensci.org/codemetar/) to create the file.
+:   Is there a recommended way to cite this project? We recommend to increase citability by using the [CodeMeta generator](https://codemeta.github.io/codemeta-generator/) to create a file called `codemeta.json`. Alternatively, one can also use the R package [`codemetar`](https://docs.ropensci.org/codemetar/) to create this file. Then, put it into the project folder.
 
 License
 

diff --git a/setup.qmd b/setup.qmd
@@ -25,7 +25,7 @@ And choose the project type _Quarto Project_.
 
 Finally, enter the name of the directory where our report will be created in, for example `code-publishing-exercise`.
 
-As we will use Git to track the version history of files, be sure to check _Create a git repository_. If you don't know what Git is, have a look at the tutorial "[Introduction to version Control with git and GitHub within RStudio](https://lmu-osc.github.io/Introduction-RStudio-Git-GitHub/)".
+As we will use Git to track the version history of files, be sure to check _Create a git repository_. If you don't know what Git is, have a look at the tutorial "[Introduction to version control with git and GitHub within RStudio](https://lmu-osc.github.io/Introduction-RStudio-Git-GitHub/)".
 
 ::: {.column-margin}
 ![renv: A dependency management toolkit for R](images/renv.svg){width=250px}
@@ -349,7 +349,7 @@ When you start a new session from the project root, the file is automatically re
 query_api(..., api_key = Sys.getenv("MY_FIRST_KEY"))
 ```
 
-Make sure that `.Renviron` is added to your `.gitignore` file in order to exclude it from the Git repository. If you already committed a file that you found contains credentials, you can follow @Chacon2024.
+Make sure that `.Renviron` is added to your `.gitignore` file in order to exclude it from the Git repository. If you already committed a file that contains credentials, you can follow @Chacon2024.
 :::
 
 ### Coding Best Practices