From 985e825b70300097c27ce65194ed3c6c62ee64f5 Mon Sep 17 00:00:00 2001 From: Radovan Bast Date: Thu, 31 Aug 2023 11:18:24 +0200 Subject: [PATCH] cosmetics --- content/blog/2023-software-licensing-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2023-software-licensing-guide.md b/content/blog/2023-software-licensing-guide.md index 632d866..6f32f6c 100644 --- a/content/blog/2023-software-licensing-guide.md +++ b/content/blog/2023-software-licensing-guide.md @@ -246,7 +246,7 @@ Choosing a license, adding a license file, and putting your code on GitHub or GitLab is good start, but to ensure FAIR (findable, accessible, interoperable, and reusable) research software for long term access, we recommend to go two steps further: -- Add a [CITATION.cff file](https://citation-file-format.github.io/) ([example](https://github.com/bast/runtest/blob/main/CITATION.cff)) +- Add a file called [CITATION.cff](https://citation-file-format.github.io/) ([example](https://github.com/bast/runtest/blob/main/CITATION.cff)). - Get a [digital object identifier (DOI)](https://en.wikipedia.org/wiki/Digital_object_identifier) for your code on [Zenodo](https://zenodo.org/) ([example](https://zenodo.org/record/8003695)).