rename title to "How to document your research software"

bast · bast · commit e99556ef3b66 · 2023-08-08T20:59:25.000+02:00
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-# Code documentation lesson
+# How to document your research software
 
 - [Credit and license](https://coderefinery.github.io/documentation/license/)
 - [How to preview the lesson locally](https://coderefinery.github.io/sphinx-lesson/contributing-to-a-lesson/#build-and-test-locally)
diff --git a/citation.cff b/citation.cff
@@ -26,9 +26,9 @@ authors:
   given-names: "Marijn"
 - family-names: "Orozco"
   given-names: "Luisa"
-title: "CodeRefinery Documentation lesson"
+title: "How to document your research software"
 type: "data"
-abstract: "The documentation lesson gives an overview of the different ways how a code project can be documented: from small projects to larger projects. Markdown and Sphinx are central tools in this lesson."
+abstract: "The lesson 'How to document your research software' gives an overview of the different ways how a code project can be documented: from small projects to larger projects. Markdown and Sphinx are central tools in this lesson."
 version: 1.0.0
 date-released: 2023-08-08
 url: "https://coderefinery.github.io/documentation/"
diff --git a/content/guide.md b/content/guide.md
@@ -47,7 +47,7 @@ of time.
 ### Detailed schedule
 
 ```markdown
-* 10:45 - 12:30 Documentation
+* 10:45 - 12:30 How to document your research software
     - 10:45 - 10:55 Motivation and tools
         - create a wishlist in HackMD
     - 10:55 - 11:05 Break
diff --git a/content/index.rst b/content/index.rst
@@ -1,5 +1,5 @@
-Code documentation
-==================
+How to document your research software
+======================================
 
 In this lesson we will discuss different solutions for implementing and
 deploying code documentation.
