Skip to content

Commit 46e13c4

Browse files
typos in blogpost
1 parent 2d3b029 commit 46e13c4

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/_posts/2018-08-31-cite_packages.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -19,24 +19,24 @@ summary: Citing the packages, modules and softwares you used for your analysis i
1919
What should I cite?
2020
===================
2121

22-
Ideally, you should indeed cite all the packages that you used. However, it's not very diegetic. Therefore, I would recommand the following.
22+
Ideally, you should indeed cite all the packages that you used. However, it's not very diegetic. Therefore, I would recommand the following:
2323

2424
1. Cite the main / important packages in the manuscript
2525

26-
These are for the packages that were central to your specific analysis (*i.e.,* that got you the results that you reported) rather than data manipulation tools (even though these are as much important).
26+
This should be done for the packages that were central to your specific analysis (*i.e.,* that got you the results that you reported) rather than data manipulation tools (even though these are as much important).
2727

2828
For example:
2929

30-
> Statistics were done using R 3.5.0 (R Core Team, 2018), the *rstanarm* (*v2.13.1*; Gabry & Goodrich, 2016) and the *psycho* (*v0.3.4*; Makowski, 2018). The code is available in **Supplementary Materials**.
30+
> Statistics were done using R 3.5.0 (R Core Team, 2018), the *rstanarm* (*v2.13.1*; Gabry & Goodrich, 2016) and the *psycho* (*v0.3.4*; Makowski, 2018) packages. The full reproducible code is available in **Supplementary Materials**.
3131
32-
1. Present everything in Supplementary Materials
32+
2. Present everything in Supplementary Materials
3333

34-
Then, in Supplementary Materials, you show the packages and function to use. Moreover, in R, you can include (usually at the end) every used package and their version using the `sessionInfo()` version.
34+
Then, in Supplementary Materials, you show the packages and functions you used. Moreover, in R, you can include (usually at the end) every used package and their version using the `sessionInfo()` function.
3535

3636
How should I cite it?
3737
=====================
3838

39-
Finding the right citation information is sometimes complicated indeed. In R, this process is made quite easy, you simply run `citation("dplyr")`:
39+
Finding the right citation information is sometimes complicated. In R, this process is made quite easy, you simply run `citation("packagename")`. For instance, `citation("dplyr")`:
4040

4141
To cite ‘dplyr’ in publications use:
4242

@@ -53,7 +53,7 @@ Finding the right citation information is sometimes complicated indeed. In R, th
5353
url = {https://CRAN.R-project.org/package=dplyr},
5454
}
5555

56-
For other languages, such as python, it might be a little trickier, but a **quick search on google (*or github*)** should provide you with all the necessary information (version, authors, date). **It's better to have a slightly incomplete citation than no citation at all.**
56+
For other languages, such as Python or Julia, it might be a little trickier, but a **quick search on google (*or github*)** should provide you with all the necessary information (version, authors, date). **It's better to have a slightly incomplete citation than no citation at all.**
5757

5858
Previous blogposts
5959
==================

0 commit comments

Comments
 (0)