diff --git a/01-introduction.html b/01-introduction.html
index 845c556a..00f6bdee 100644
--- a/01-introduction.html
+++ b/01-introduction.html
@@ -303,7 +303,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -703,7 +703,7 @@ <h3 class="callout-title">What does open and reproducible research mean
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -726,7 +726,7 @@ <h3 class="callout-title">What does open and reproducible research mean
   "identifier": "https://softwaresaved.github.io/fair-research-software/01-introduction.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-07-04",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/02-fair-research-software.html b/02-fair-research-software.html
index 5bdbda4d..d7980c8a 100644
--- a/02-fair-research-software.html
+++ b/02-fair-research-software.html
@@ -300,7 +300,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -373,7 +373,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>FAIR research software</h1>
-        <p>Last updated on 2024-07-04 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/02-fair-research-software.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -458,39 +458,55 @@ <h3 class="callout-title">Motivation</h3>
 below is not exhaustive, but any of the practices that you employ in
 your research software workflow will bring you closer to the gold
 standard of a fully reproducible research.</p>
-<ul><li>Findable
-<ul><li>Create a description of your software</li>
+<div class="section level3">
+<h3 id="findable">Findable<a class="anchor" aria-label="anchor" href="#findable"></a></h3>
+<p>In order to make your software more findable, you should:</p>
+<ul><li>Create a description of your software to make it discoverable by
+search engines and other search tools</li>
 <li>Place your software in a public software repository (and ideally
-register it in a <a href="https://github.com/NLeSC/awesome-research-software-registries" class="external-link">software
-registry</a>)</li>
+register it in a [general-purpose or domain-specific software
+registry][software-registries])</li>
 <li>Use a unique and persistent identifier (DOI) for your software
-(e.g. by depositing your code on Zenodo), which is also useful for
+(e.g. by depositing your code on <a href="https://zenodo.org/" class="external-link">Zenodo</a>), which is also useful for
 citations - note that depositing your data/code on GitHub and similar
 software repositories may not be enough as they may change their open
-access model or disappear completely in the future</li>
-</ul></li>
-<li>Accessible
+access model or disappear completely in the future, so archiving your
+code means it stands a better chance at being preserved</li>
+</ul></div>
+<div class="section level3">
+<h3 id="accessible">Accessible<a class="anchor" aria-label="anchor" href="#accessible"></a></h3>
+<p>In order to make your software more accessible, you should:</p>
 <ul><li>Make sure people can freely, legally and easily get a copy your
 software</li>
-<li>Use coding conventions and comments to make your code readable and
-understandable by people (once they get a copy of it)</li>
-</ul></li>
-<li>Interoperable
-<ul><li>Explain the functionality of your software</li>
+<li>Use code style conventions and code structure patterns, use comments
+and create documentation to make your code comprehensible by people
+(once they get a copy of it) - i.e. make your code accessible in the
+<em>intelligible</em> sense</li>
+</ul></div>
+<div class="section level3">
+<h3 id="interoperable">Interoperable<a class="anchor" aria-label="anchor" href="#interoperable"></a></h3>
+<p>In order to make your software more interoperable, you should:</p>
+<ul><li>Explain the functionality of your software, so others can understand
+how other tools can interoperate with it</li>
 <li>Use standard formats for inputs and outputs</li>
 <li>Communicate with other software via standard protocols and APIs</li>
-</ul></li>
-<li>Reusable
+</ul></div>
+<div class="section level3">
+<h3 id="reusable">Reusable<a class="anchor" aria-label="anchor" href="#reusable"></a></h3>
+<p>In order to make your software more reusable, you should:</p>
 <ul><li>Document your software (including its functionality, and how to
-install and run it)</li>
-<li>Follow best practices for software development (including coding
-conventions, code readability and verifying its correctness)</li>
+install and run it) to make it more understandable by others who may
+wish to reuse or extend it</li>
+<li>Follow best practices for software development (including code
+conventions, structure, readability and correctness)</li>
 <li>Test your software and make sure it works on different
-platforms/operating systems</li>
+platforms/operating systems to make it more reusable</li>
 <li>Give a licence to your software clearly stating how it can be
 reused</li>
-<li>State how to cite your software</li>
-</ul></li>
+<li>State how to cite your software, so people can give you credit when
+they reuse it</li>
+<li>Include a contributor policy so that others can contribute to your
+code and credit for contributions is provided</li>
 </ul><div id="fair-is-a-process-not-a-perfect-metric" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
@@ -498,7 +514,7 @@ <h3 class="callout-title">Motivation</h3>
 <div id="fair-is-a-process-not-a-perfect-metric" class="callout-inner">
 <h3 class="callout-title">FAIR is a process, not a perfect metric</h3>
 <div class="callout-content">
-<p>FAIR is not a binary metric - there is no such thing as “FAIR or not
+<p>FAIR is not a binary metric - there is no such thing as “FAIR or”not
 FAIR”.</p>
 <p>FAIR is not a perfect metric, nor does it provide a full and
 exhaustive software quality checklist. Software may be FAIR but still
@@ -540,13 +556,15 @@ <h3 class="callout-title">Challenge</h3>
 </ul></div>
 </div>
 </div>
+</div>
 </section><section><h2 class="section-heading" id="software-and-data-used-in-this-course">Software and data used in this course<a class="anchor" aria-label="anchor" href="#software-and-data-used-in-this-course"></a></h2>
 <hr class="half-width"><p>We are going to follow a fairly typical experience of a new PhD or
 postdoc joining a research group. They were emailed some data and
 analysis code bundled in a <code>.zip</code> archive and written by
-another group member who works on similar things. They need to be able
-to install and run this code on their machine, check they understand it
-and then adapt it to their own project.</p>
+another group member who worked on similar things but has since left the
+group. They need to be able to install and run this code on their
+machine, check they can understand it and then adapt it to their own
+project.</p>
 <p>As part of the <a href="./index.html#astronaut-data-and-analysis-code">setup for this
 course</a>, you should have downloaded a <code>.zip</code> archive
 containing the software project the new research team member was given.
@@ -575,10 +593,11 @@ <h3 class="callout-title">Challenge</h3>
 <div class="callout-inner">
 <h3 class="callout-title">Discussion</h3>
 <div class="callout-content">
-<p>Compare this data and code to the software you chose earlier. Do you
-think it is Findable, Accessible, Interoperable and Reusable? Give it a
-score from 1 to 5 in each category, as in the previous exercise, and
-then we will discuss it together.</p>
+<p>Look at our code in VS Code and compare this data and code to the
+software you chose earlier (or assess it on its own). Do you think it is
+Findable, Accessible, Interoperable and Reusable? Give it a score from 1
+to 5 in each category, as in the previous exercise, and then we will
+discuss it together.</p>
 </div>
 </div>
 </div>
@@ -756,7 +775,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -778,8 +797,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/02-fair-research-software.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/02-fair-research-software.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-07-04",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/03-tools.html b/03-tools.html
index dfccb59a..6993096c 100644
--- a/03-tools.html
+++ b/03-tools.html
@@ -234,16 +234,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 
     <div id="flush-collapsecurrent" class="accordion-collapse collapse show" aria-labelledby="flush-headingcurrent" data-bs-parent="#accordionFlushcurrent">
       <div class="accordion-body">
-        <ul><li><a href="#development-environment">Development environment</a></li>
-<li><a href="#command-line-toolshell">Command line tool/shell</a></li>
-<li><a href="#version-control">Version control</a></li>
-<li><a href="#code-structure-and-style-guidelines">Code structure and style guidelines</a></li>
-<li><a href="#code-correctness">Code correctness</a></li>
-<li><a href="#documentation">Documentation</a></li>
-<li><a href="#licences-and-citation">Licences and citation</a></li>
-<li><a href="#code-repositories-and-registries">Code repositories and registries</a></li>
-<li><a href="#summary-of-tools-practices">Summary of tools &amp; practices</a></li>
-<li><a href="#checking-your-setup">Checking your setup</a></li>
+        <ul><li><a href="#checking-your-setup">Checking your setup</a></li>
 <li><a href="#further-reading">Further reading</a></li>
         </ul></div><!--/div.accordion-body-->
     </div><!--/div.accordion-collapse-->
@@ -308,7 +299,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -381,7 +372,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Tools and practices for FAIR research software development</h1>
-        <p>Last updated on 2024-09-24 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/03-tools.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -422,221 +413,210 @@ <h3 class="card-title">Objectives</h3>
 <p>In this course we will introduce you to a group of tools and
 practices that are commonly used in research to help you develop
 software in a FAIR way. You should already have these tools installed on
-your machine following the setup instructions. Here we will give an
-overview of the tools, how they help you achieve the aims of FAIR
-research software and how they work together. In later episodes we will
-describe some of these tools in more detail.</p>
-<section><h2 class="section-heading" id="development-environment">Development environment<a class="anchor" aria-label="anchor" href="#development-environment"></a></h2>
-<hr class="half-width"><p>One of the first choices we make when writing code is what tool to
-use to do the writing. You can use a simple text editor such as Notepad,
-a terminal based editor with syntax highlighting such as Vim or Emacs,
-or one of many Integrated Development Environments (IDEs) which give you
-the tools to write, run and debug your code and inspect the output all
-in one place. Note that you should not use word processing software such
-as Microsoft Word or Apple Pages to write code - these tools are
-designed to create nicely formatted text for humans to read, so they may
-add or change formatting, or insert invisible characters that the
-programming language cannot interpret. Try opening a Word document in
-Notepad to see an example.</p>
-<p>This is mostly a personal choice as an experienced user of any of
-these tools can write good, FAIR software efficiently, but IDEs are
-popular because they are designed specifically for writing and running
-code. There are some language specific IDEs such as PyCharm, and some
-that can work with many languages like VS Code (Visual Studio Code).
-IDEs also have add-ons that provide extra functionality, such as
-checking your code as you type (similar to a spell-checker in Word),
-highlighting when you are not following best practice, or even
-automatically generating bits of code for you.</p>
-
-<p>In this course we will use VS Code IDE, as it is free, available on
-Windows, Mac and Linux operating systems, and can be used with many
-programming languages. It is a single tool in which we can:</p>
-<ul><li>view our file system</li>
-<li>open many kinds of files</li>
-<li>edit, compile, run and debug code</li>
-<li>open a terminal to run command line tools (including version control
-tool Git) or view code outputs</li>
-</ul><p>Use VS Code to open the Python script and the data file from our
-project.</p>
-</section><section><h2 class="section-heading" id="command-line-toolshell">Command line tool/shell<a class="anchor" aria-label="anchor" href="#command-line-toolshell"></a></h2>
-<hr class="half-width"><p>In VS Code and similar IDEs you can often run the code by clicking a
-button or pressing some keyboard shortcut. If you gave your code to a
-colleague or collaborator they might use the same IDE or something
-different, so you cannot guarantee that they will have the same buttons
-and shortcuts as you.</p>
-<p>In the previous episode we mentioned that interoperable software
-should use standard protocols so that it can integrate with other tools.
-One of these standard protocols/tools is using the inputs and outputs
-via the command line terminal or shell. Command line terminal provides
-one of the oldest ways of interacting with operating system so many
-programs will have command line interfaces. Command line terminals, such
-as Bash and Zsh, have their own language syntax that allow you to write
-scripts and/or group and chain commands together to build up complex
-workflows using several programs in different steps. They also use less
-resources than a graphical user interface tool like an IDE, so are
-commonly used on high-performance computers and other shared systems
-where time, memory and processing power are expensive or in high
-demand.</p>
-<p>In this course we will use the Bash shell, which is one of the most
-common and comes already installed on Mac and Linux operating systems.
-You can create a command line interface to your program which will allow
-it to be run on any system that has a Bash shell, and allow users to
-change things like input and output files or choose different settings
-or parameters without editing your code. With a command line interface,
-your code can be built into automated workflows so that the whole
-process from data gathering to analysis to saving publication-quality
-results can be written in one Bash script and saved and reused.</p>
-</section><section><h2 class="section-heading" id="version-control">Version control<a class="anchor" aria-label="anchor" href="#version-control"></a></h2>
-<hr class="half-width"><p>Version control means knowing what changes were made to your code and
-when. Many people who have worked on large documents such as essays
-start doing this by saving files called <code>essay_draft</code>,
-<code>essay_version1.doc</code>, <code>essay_version2.doc</code>, and so
-on. This can work on a small scale but most people find it quickly gets
-confusing which version a certain change was made, or which version is
-the one that you got feedback from a supervisor on. Using a version
-control system helps you keep track of changes, including when you might
-be working on shared code being edited by more than one person at a
-time.</p>
-<p>It also lets you assign version numbers or tags to particular
-versions so you can then use those to refer back to them later. For
-example, you can run your code and output some results and add a comment
-to your output that those results were produced by version 2.4 of your
-code, so if you try to run the same thing later and find it is
-different, you can check if it is a change in the code due to using a
-newer version, or a change in the data, or something else.</p>
-<p>We will be using the Git version control system, which can be used
-through the command line terminal, in a browser or in a desktop
-application.</p>
-</section><section><h2 class="section-heading" id="code-structure-and-style-guidelines">Code structure and style guidelines<a class="anchor" aria-label="anchor" href="#code-structure-and-style-guidelines"></a></h2>
-<hr class="half-width"><p>TODO</p>
-</section><section><h2 class="section-heading" id="code-correctness">Code correctness<a class="anchor" aria-label="anchor" href="#code-correctness"></a></h2>
-<hr class="half-width"><p>Testing ensures that your code is correct and does what it is set out
+your machine following the <a href="./index.html#astronaut-data-and-analysis-code">setup
+instructions</a>. Here we will give an overview of the tools, how they
+help you achieve the aims of FAIR research software and how they work
+together. In later episodes we will describe some of these tools in more
+detail.</p>
+<div class="section level3">
+<h3 id="development-environments">Development environments<a class="anchor" aria-label="anchor" href="#development-environments"></a></h3>
+<p>Virtual and integrated development environments (IDEs), such as VS
+Code or PyCharm, help with running, testing, and debugging code. Virtual
+environments further enable us to share our working environments with
+others, making it easier to access, reuse and extend our code. IDEs
+often provide integrations with other tools, e.g. version control and
+command line terminals, enabling you to do many tasks from a single
+environment, saving time in switching between different tools.</p>
+</div>
+<div class="section level3">
+<h3 id="command-line-terminals">Command line terminals<a class="anchor" aria-label="anchor" href="#command-line-terminals"></a></h3>
+<p>Command line terminals (e.g. Bash, GitBash) enable us to run and test
+our code without graphical user interfaces (GUI) afforded to us by IDEs
+- this is sometimes needed for accessing and running our code remotely
+on servers and high-performance systems without a GUI provision, where
+time, memory and processing power are expensive or in high demand.</p>
+<p>Version control systems are typically provided as command line tools,
+making them often only accessible from command line terminals to enter
+commands and access remote version control servers to backing up and
+sharing our work.</p>
+<p>Finally, command line tools use standard protocols for passing
+parameters, inputs and outputs. This makes it easier to integrate ours
+with other command line tools, allowing us to chain them and build up
+complex and reproducible workflows and analysis pipelines using several
+programs in different steps. If we write our software in a way which
+provides such an interoperable command line interface - we will be able
+to integrate it with other command line tools to automate and speed up
+our work.</p>
+</div>
+<div class="section level3">
+<h3 id="standard-inputoutput-formats-and-communication-protocols">Standard input/output formats and communication protocols<a class="anchor" aria-label="anchor" href="#standard-inputoutput-formats-and-communication-protocols"></a></h3>
+<p>Using standard data exchange, input and output formats and
+communication protocols helps create interoperable software that can
+more readily integrate with other tools into more complex pipelines -
+increasing its interoperability and reusability.</p>
+</div>
+<div class="section level3">
+<h3 id="version-control-tools">Version control tools<a class="anchor" aria-label="anchor" href="#version-control-tools"></a></h3>
+<p>Version control means knowing what changes were made to your code,
+when and by whom - promoting code ownership, responsibility and credit.
+When combined with software sharing and collaborative platforms such as
+GitHub or GitLab, it facilitates code publication, sharing and
+findability, teamwork and discussions about software and design
+decisions, provides backup facilities for your code and speeds up
+collaboration on shared code by allowing edits by more than one person
+at a time.</p>
+</div>
+<div class="section level3">
+<h3 id="code-style-and-structure-conventions">Code style and structure conventions<a class="anchor" aria-label="anchor" href="#code-style-and-structure-conventions"></a></h3>
+<p>Following code style conventions for your programming language and
+standard code structure patterns that are agreed upon by the community
+and other programmers are important practices to ensure that others find
+it easy to read your code, reuse or extend it in their own examples and
+applications.</p>
+</div>
+<div class="section level3">
+<h3 id="code-testing">Code testing<a class="anchor" aria-label="anchor" href="#code-testing"></a></h3>
+<p>Testing ensures that your code is correct and does what it is set out
 to do. When you write code you often feel very confident that it is
 perfect, but when writing bigger codes or code that is meant to do
 complex operations it is very hard to consider all possible edge cases
 or notice every single typing mistake. Testing also gives other people
 confidence in your code as they can see an example of how it is meant to
-run and be assured that it does work correctly on their machine.</p>
-<p>We will show different ways to test your code for different purposes.
-You need to think about what it is that is important to you and any
-future users or collaborators to decide what kind of testing is most
-useful for you.</p>
-</section><section><h2 class="section-heading" id="documentation">Documentation<a class="anchor" aria-label="anchor" href="#documentation"></a></h2>
-<hr class="half-width"><p>Documentation comes in many forms - from the names of variables and
-functions in your code, additional comments that explain some lines, up
-to a whole website full of documentation with function definitions,
-usage examples, tutorials and guides. You many not need as much
-documentation as a large commercial software product, but making your
-code reusable relies on other people being able to understand what your
-code does and how to use it.</p>
-</section><section><h2 class="section-heading" id="licences-and-citation">Licences and citation<a class="anchor" aria-label="anchor" href="#licences-and-citation"></a></h2>
-<hr class="half-width"><p>A licence states what people can legally do with your code, and what
-restrictions you have placed on it. Whenever you want to use someone
-else’s code you should check what license they have and make sure your
-use is legal. You may be restricted by your institution, your grant
-funding, or by other tools you use that require certain licenses for you
-to be compatible with them.</p>
-<p>Having a citation instructions is not a legal requirement but if you
-want to get academic credit for your work, you can make other people’s
-life much easier by telling them how you would like to be credited.
-Similarly, follow citation instructions ensures that when you use
-others’ code in your research they will be credited accordingly.</p>
-<p>Both licensing law and citation procedures can vary depending on your
-country and institution, so remember to check with a local team where
-you are. Your local research IT support or library teams would be a good
-place to start.</p>
-</section><section><h2 class="section-heading" id="code-repositories-and-registries">Code repositories and registries<a class="anchor" aria-label="anchor" href="#code-repositories-and-registries"></a></h2>
-<hr class="half-width"><p>Having somewhere to share your code is fundamental to making it
-Findable. Your institution might have a code repository, your research
-field may have a practice of sharing code via a specific website or
-journal, or your version control system might include an online
-component that makes sharing different versions of your code easy.
-Again, remember to check the rules of your institution and grant on
-publishing code, and any licenses for code you depend on or reuse.</p>
-<p>We will discuss later how to share your code on GitHub and make it
-easy for others to find and use.</p>
-</section><section><h2 class="section-heading" id="summary-of-tools-practices">Summary of tools &amp; practices<a class="anchor" aria-label="anchor" href="#summary-of-tools-practices"></a></h2>
-<hr class="half-width"><p>The table below summarises some tools and practices that can help
-with each of the FAIR software principles.</p>
-<table class="table"><colgroup><col width="67%"><col width="6%"><col width="8%"><col width="10%"><col width="6%"></colgroup><thead><tr class="header"><th>Tools and practices</th>
+run and be assured that it does work correctly on their machine -
+helping with code understanding and reusability.</p>
+</div>
+<div class="section level3">
+<h3 id="software--and-project--level-documentation">Software- and project- level documentation<a class="anchor" aria-label="anchor" href="#software--and-project--level-documentation"></a></h3>
+<p>Documentation comes in many forms - from <strong>software-level
+documentation</strong> including docstrings describing functions and
+classes and in-line comments that explain lines of your code, to
+<strong>project-level documentation</strong> and
+<strong>metadata</strong> (including README, LICENCE, CITATION,
+CONTRIBUTING, etc. files) that help to discover it, explain the legal
+terms of reusing it, describe its functionality and how to install, run
+and contribute to it, to whole websites full of documentation with
+function definitions, usage examples, tutorials and guides. You many not
+need as much documentation as a large commercial software product, but
+making your code reusable relies on other people being able to
+understand what your code does and how to use it.</p>
+</div>
+<div class="section level3">
+<h3 id="software-repositories-and-registries">Software repositories and registries<a class="anchor" aria-label="anchor" href="#software-repositories-and-registries"></a></h3>
+<p>Having somewhere to share your code is fundamental to making it
+findable and accessible. Your institution might have a code repository,
+your research field may have a practice of sharing code via a specific
+website, archive or journal, or your version control system might
+include an online component that makes sharing different versions of
+your code easy. You should check the rules or guidelines of your
+institution, grant or domain on publishing code, as well as any licenses
+of the code your software depends on or reuses.</p>
+<p>Some examples of commonly used software repositories and registries
+include:</p>
+<ul><li>general-purpose software repositories, such as <a href="https://github.com" class="external-link">GitHub</a> and <a href="https://about.gitlab.com/" class="external-link">GitLab</a>
+</li>
+<li>programming language-specific software repositories, such as <a href="https://pypi.org/" class="external-link">PyPi</a> (for Python) and <a href="https://cran.r-project.org/web/packages/" class="external-link">CRAN</a> (for R)</li>
+<li>software registries, such as <a href="https://biotools.us/" class="external-link">BioTools</a> (for biosciences) and <a href="https://github.com/NLeSC/awesome-research-software-registries" class="external-link">Awesome
+Research Software Registries</a> (providing a list of research software
+registries by country, organisation, domain and programming language)
+where research software can be registered to help promote its
+discovery</li>
+</ul></div>
+<div class="section level3">
+<h3 id="persistent-identifiers">Persistent identifiers<a class="anchor" aria-label="anchor" href="#persistent-identifiers"></a></h3>
+<p>Unique persistent identifiers, such as Digital Object Identifiers
+(DOIs) provided by <a href="https://zenodo.org/" class="external-link">Zenodo</a>, <a href="https://figshare.com/" class="external-link">FigShare</a> and similar digital archiving
+services, and commits/tags/releases used by GitHub and similar code
+sharing platforms, help with findability and accessibility of your
+software, and can help you get credit for your work by providing citable
+references.</p>
+</div>
+<div class="section level3">
+<h3 id="tools-and-practices-summary">Tools and practices summary<a class="anchor" aria-label="anchor" href="#tools-and-practices-summary"></a></h3>
+<p>The table below provides a summary of how different tools and
+practices help with the FAIR software principles.</p>
+<table class="table"><colgroup><col width="71%"><col width="5%"><col width="7%"><col width="9%"><col width="5%"></colgroup><thead><tr class="header"><th>Tools and practices</th>
 <th>Findable</th>
 <th>Accessible</th>
 <th>Interoperable</th>
 <th>Reusable</th>
-</tr></thead><tbody><tr class="odd"><td>Virtual development environments, programming language and
-dependencies - run, test, debug, share</td>
+</tr></thead><tbody><tr class="odd"><td>Virtual development environments</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
-</tr><tr class="even"><td>Integrated development environments/IDEs (e.g. VS Code, PyCharm) -
-run, test, debug</td>
+</tr><tr class="even"><td>Integrated development environments/IDEs</td>
 <td></td>
 <td></td>
 <td></td>
 <td>x</td>
-</tr><tr class="odd"><td>Command line terminal (e.g. Bash, GitBash) - reproducible
-workflows/pipelines</td>
+</tr><tr class="odd"><td>Command line terminals - automated and reproducible pipelines</td>
 <td></td>
 <td></td>
 <td>x</td>
 <td>x</td>
-</tr><tr class="even"><td>Version control tools</td>
+</tr><tr class="even"><td>Standard formats - e.g. for data exchange (CSV, YAML)</td>
+<td></td>
+<td>x</td>
+<td>x</td>
 <td>x</td>
+</tr><tr class="odd"><td>Communication protocols - Command Line Interface (CLI) or
+Application Programming Interface (API)</td>
 <td></td>
+<td>x</td>
+<td>x</td>
+<td>x</td>
+</tr><tr class="even"><td>Version control tools</td>
+<td>x</td>
 <td></td>
 <td></td>
-</tr><tr class="odd"><td>Testing - code correctness and reproducibility</td>
 <td></td>
-<td>x</td>
+</tr><tr class="odd"><td>Code testing and correctness</td>
 <td></td>
 <td>x</td>
-</tr><tr class="even"><td>Coding conventions and documentation</td>
 <td></td>
 <td>x</td>
-<td>x</td>
-<td>x</td>
-</tr><tr class="odd"><td>Explaining functionality/installation/running - README, inline
-comments and documentation</td>
+</tr><tr class="even"><td>Code style conventions</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
-</tr><tr class="even"><td>Standard formats - e.g. for data exchange (CSV, YAML)</td>
+</tr><tr class="odd"><td>Software-level documentation (comments and docstrings, explaining
+functionality)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
-</tr><tr class="odd"><td>Communication protocols - Command Line Interface (CLI) or
-Application Programming Interface (API)</td>
+</tr><tr class="even"><td>Project-level documentation (READMEs, explaining
+functionality/installation/running)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
-</tr><tr class="even"><td>License</td>
+</tr><tr class="odd"><td>License - code sharing and reuse</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
-</tr><tr class="odd"><td>Citation</td>
+</tr><tr class="even"><td>Citation - code reuse and credit</td>
 <td>x</td>
 <td></td>
 <td></td>
 <td>x</td>
-</tr><tr class="even"><td>Software repositories (e.g. GitHub, PyPi) or registries
-(e.g. BioTools)</td>
+</tr><tr class="odd"><td>Software repositories and registries - code sharing</td>
 <td>x</td>
 <td>x</td>
 <td></td>
 <td></td>
-</tr><tr class="odd"><td>Unique persistent identifier (e.g. DOIs, commits/tags/releases) -
-Zenodo, FigShare GitHub</td>
+</tr><tr class="even"><td>Unique persistent identifiers - finding and citing software</td>
 <td>x</td>
 <td>x</td>
 <td></td>
 <td></td>
-</tr></tbody></table></section><section><h2 class="section-heading" id="checking-your-setup">Checking your setup<a class="anchor" aria-label="anchor" href="#checking-your-setup"></a></h2>
-<hr class="half-width"><div id="checking-your-setup-1" class="callout challenge">
+</tr></tbody></table></div>
+<section><h2 class="section-heading" id="checking-your-setup">Checking your setup<a class="anchor" aria-label="anchor" href="#checking-your-setup"></a></h2>
+<hr class="half-width"><p>Let’s check your setup now to make sure you are ready for the rest of
+this course.</p>
+<div id="checking-your-setup-1" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
 </div>
@@ -809,7 +789,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -831,8 +811,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/03-tools.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/03-tools.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-24",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/04-version-control.html b/04-version-control.html
index 00e6936b..5bfe7df3 100644
--- a/04-version-control.html
+++ b/04-version-control.html
@@ -302,7 +302,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -375,7 +375,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Version control</h1>
-        <p>Last updated on 2024-09-24 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/04-version-control.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -808,14 +808,13 @@ <h3 id="rename-our-data-and-output-files">Rename our data and output files<a cla
 <ol style="list-style-type: lower-roman"><li>give our input data file and script more meaningful names and</li>
 <li>choose informative file names for our output data file and
 plot.</li>
-</ol><p>First let’s update file names in our script.</p>
+</ol><p>First let’s update file names in our script using VS Code.</p>
 <div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb26-2"><a href="#cb26-2" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb26-3"><a href="#cb26-3" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
-<span id="cb26-4"><a href="#cb26-4" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>   </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb26-2"><a href="#cb26-2" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
+<span id="cb26-3"><a href="#cb26-3" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>   </span></code></pre>
 </div>
 <p>Now, let’s actually rename our files on the file system using git and
 commit our changes.</p>
@@ -1252,7 +1251,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1274,8 +1273,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/04-version-control.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/04-version-control.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-24",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/05-code-environment.html b/05-code-environment.html
index c5086e33..03f9a001 100644
--- a/05-code-environment.html
+++ b/05-code-environment.html
@@ -257,6 +257,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <li><a href="#creating-virtual-environments">Creating virtual environments</a></li>
 <li><a href="#installing-external-packages">Installing external packages</a></li>
 <li><a href="#sharing-virtual-environments">Sharing virtual environments</a></li>
+<li><a href="#running-the-code">Running the code</a></li>
 <li><a href="#further-reading">Further reading</a></li>
         </ul></div><!--/div.accordion-body-->
     </div><!--/div.accordion-collapse-->
@@ -303,7 +304,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -376,7 +377,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Reproducible development environment</h1>
-        <p>Last updated on 2024-09-24 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/05-code-environment.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -785,6 +786,16 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 file accordingly by re-issuing <code>pip freeze</code> command and
 propagate the updated <code>requirements.txt</code> file to your
 collaborators via your code sharing platform.</p>
+</section><section><h2 class="section-heading" id="running-the-code">Running the code<a class="anchor" aria-label="anchor" href="#running-the-code"></a></h2>
+<hr class="half-width"><p>We are now setup to run our code from the newly created virtual
+environment:</p>
+<div class="codewrapper sourceCode" id="cb25">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py</span></code></pre>
+</div>
+<p>You should get a pop up window with a graph. Let’s inspect the code
+in a more detail, see if we can understand and improve it.</p>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a></h2>
 <hr class="half-width"><p>We recommend the following resources for some additional reading on
 the topic of this episode:</p>
@@ -852,7 +863,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -874,8 +885,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/05-code-environment.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/05-code-environment.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-24",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/06-code-readability.html b/06-code-readability.html
index 644f7cb8..0f7d294c 100644
--- a/06-code-readability.html
+++ b/06-code-readability.html
@@ -304,7 +304,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -377,7 +377,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code readability</h1>
-        <p>Last updated on 2024-09-26 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/06-code-readability.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -471,69 +471,67 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="codewrapper sourceCode" id="cb2">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a></span>
-<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb2-3"><a href="#cb2-3" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb2-4"><a href="#cb2-4" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
-<span id="cb2-5"><a href="#cb2-5" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>  </span>
-<span id="cb2-6"><a href="#cb2-6" tabindex="-1"></a></span>
-<span id="cb2-7"><a href="#cb2-7" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
-<span id="cb2-8"><a href="#cb2-8" tabindex="-1"></a></span>
-<span id="cb2-9"><a href="#cb2-9" tabindex="-1"></a>data<span class="op">=</span>[]</span>
-<span id="cb2-10"><a href="#cb2-10" tabindex="-1"></a><span class="im">import</span> json</span>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="im">import</span> json</span>
+<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="im">import</span> csv</span>
+<span id="cb2-3"><a href="#cb2-3" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
+<span id="cb2-4"><a href="#cb2-4" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb2-5"><a href="#cb2-5" tabindex="-1"></a></span>
+<span id="cb2-6"><a href="#cb2-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb2-7"><a href="#cb2-7" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb2-8"><a href="#cb2-8" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
+<span id="cb2-9"><a href="#cb2-9" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span> </span>
+<span id="cb2-10"><a href="#cb2-10" tabindex="-1"></a></span>
 <span id="cb2-11"><a href="#cb2-11" tabindex="-1"></a></span>
-<span id="cb2-12"><a href="#cb2-12" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> <span class="bu">range</span>(<span class="dv">374</span>):</span>
-<span id="cb2-13"><a href="#cb2-13" tabindex="-1"></a>    line<span class="op">=</span>data_f.readline()</span>
-<span id="cb2-14"><a href="#cb2-14" tabindex="-1"></a>    <span class="bu">print</span>(line)</span>
-<span id="cb2-15"><a href="#cb2-15" tabindex="-1"></a>    data.append(json.loads(line[<span class="dv">1</span>:<span class="op">-</span><span class="dv">1</span>]))</span>
-<span id="cb2-16"><a href="#cb2-16" tabindex="-1"></a><span class="co">#data.pop(0)</span></span>
-<span id="cb2-17"><a href="#cb2-17" tabindex="-1"></a><span class="co">## Comment out this bit if you don't want the spreadsheet</span></span>
-<span id="cb2-18"><a href="#cb2-18" tabindex="-1"></a><span class="im">import</span> csv</span>
-<span id="cb2-19"><a href="#cb2-19" tabindex="-1"></a></span>
-<span id="cb2-20"><a href="#cb2-20" tabindex="-1"></a>w<span class="op">=</span>csv.writer(data_t)</span>
-<span id="cb2-21"><a href="#cb2-21" tabindex="-1"></a></span>
-<span id="cb2-22"><a href="#cb2-22" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
-<span id="cb2-23"><a href="#cb2-23" tabindex="-1"></a></span>
-<span id="cb2-24"><a href="#cb2-24" tabindex="-1"></a>time <span class="op">=</span> []</span>
-<span id="cb2-25"><a href="#cb2-25" tabindex="-1"></a>date <span class="op">=</span>[]</span>
-<span id="cb2-26"><a href="#cb2-26" tabindex="-1"></a></span>
-<span id="cb2-27"><a href="#cb2-27" tabindex="-1"></a>j<span class="op">=</span><span class="dv">0</span></span>
-<span id="cb2-28"><a href="#cb2-28" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> data:</span>
-<span id="cb2-29"><a href="#cb2-29" tabindex="-1"></a>    <span class="bu">print</span>(data[j])</span>
-<span id="cb2-30"><a href="#cb2-30" tabindex="-1"></a>    <span class="co"># and this bit</span></span>
-<span id="cb2-31"><a href="#cb2-31" tabindex="-1"></a>    w.writerow(data[j].values())</span>
-<span id="cb2-32"><a href="#cb2-32" tabindex="-1"></a>    <span class="cf">if</span> <span class="st">'duration'</span> <span class="kw">in</span> data[j].keys():</span>
-<span id="cb2-33"><a href="#cb2-33" tabindex="-1"></a>        tt<span class="op">=</span>data[j][<span class="st">'duration'</span>]</span>
-<span id="cb2-34"><a href="#cb2-34" tabindex="-1"></a>        <span class="cf">if</span> tt <span class="op">==</span> <span class="st">''</span>:</span>
-<span id="cb2-35"><a href="#cb2-35" tabindex="-1"></a>            <span class="cf">pass</span></span>
-<span id="cb2-36"><a href="#cb2-36" tabindex="-1"></a>        <span class="cf">else</span>:</span>
-<span id="cb2-37"><a href="#cb2-37" tabindex="-1"></a>            t<span class="op">=</span>dt.datetime.strptime(tt,<span class="st">'%H:%M'</span>)</span>
-<span id="cb2-38"><a href="#cb2-38" tabindex="-1"></a>            ttt <span class="op">=</span> dt.timedelta(hours<span class="op">=</span>t.hour, minutes<span class="op">=</span>t.minute, seconds<span class="op">=</span>t.second).total_seconds()<span class="op">/</span>(<span class="dv">60</span><span class="op">*</span><span class="dv">60</span>)</span>
-<span id="cb2-39"><a href="#cb2-39" tabindex="-1"></a>            <span class="bu">print</span>(t,ttt)</span>
-<span id="cb2-40"><a href="#cb2-40" tabindex="-1"></a>            time.append(ttt)</span>
-<span id="cb2-41"><a href="#cb2-41" tabindex="-1"></a>            <span class="cf">if</span> <span class="st">'date'</span> <span class="kw">in</span> data[j].keys():</span>
-<span id="cb2-42"><a href="#cb2-42" tabindex="-1"></a>                date.append(dt.datetime.strptime(data[j][<span class="st">'date'</span>][<span class="dv">0</span>:<span class="dv">10</span>], <span class="st">'%Y-%m-</span><span class="sc">%d</span><span class="st">'</span>))</span>
-<span id="cb2-43"><a href="#cb2-43" tabindex="-1"></a>                <span class="co">#date.append(data[j]['date'][0:10])</span></span>
-<span id="cb2-44"><a href="#cb2-44" tabindex="-1"></a></span>
-<span id="cb2-45"><a href="#cb2-45" tabindex="-1"></a>            <span class="cf">else</span>:</span>
-<span id="cb2-46"><a href="#cb2-46" tabindex="-1"></a>                time.pop(<span class="dv">0</span>)</span>
-<span id="cb2-47"><a href="#cb2-47" tabindex="-1"></a>    j<span class="op">+=</span><span class="dv">1</span></span>
-<span id="cb2-48"><a href="#cb2-48" tabindex="-1"></a></span>
-<span id="cb2-49"><a href="#cb2-49" tabindex="-1"></a>t<span class="op">=</span>[<span class="dv">0</span>]</span>
-<span id="cb2-50"><a href="#cb2-50" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> time:</span>
-<span id="cb2-51"><a href="#cb2-51" tabindex="-1"></a>    t.append(t[<span class="op">-</span><span class="dv">1</span>]<span class="op">+</span>i)</span>
-<span id="cb2-52"><a href="#cb2-52" tabindex="-1"></a></span>
-<span id="cb2-53"><a href="#cb2-53" tabindex="-1"></a>date,time <span class="op">=</span> <span class="bu">zip</span>(<span class="op">*</span><span class="bu">sorted</span>(<span class="bu">zip</span>(date, time)))</span>
-<span id="cb2-54"><a href="#cb2-54" tabindex="-1"></a></span>
-<span id="cb2-55"><a href="#cb2-55" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb2-56"><a href="#cb2-56" tabindex="-1"></a></span>
-<span id="cb2-57"><a href="#cb2-57" tabindex="-1"></a>plt.plot(date,t[<span class="dv">1</span>:], <span class="st">'ko-'</span>)</span>
-<span id="cb2-58"><a href="#cb2-58" tabindex="-1"></a>plt.xlabel(<span class="st">'Year'</span>)</span>
-<span id="cb2-59"><a href="#cb2-59" tabindex="-1"></a>plt.ylabel(<span class="st">'Total time spent in space to date (hours)'</span>)</span>
-<span id="cb2-60"><a href="#cb2-60" tabindex="-1"></a>plt.tight_layout()</span>
-<span id="cb2-61"><a href="#cb2-61" tabindex="-1"></a>plt.savefig(g_file)</span>
-<span id="cb2-62"><a href="#cb2-62" tabindex="-1"></a>plt.show()</span>
-<span id="cb2-63"><a href="#cb2-63" tabindex="-1"></a></span></code></pre>
+<span id="cb2-12"><a href="#cb2-12" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
+<span id="cb2-13"><a href="#cb2-13" tabindex="-1"></a></span>
+<span id="cb2-14"><a href="#cb2-14" tabindex="-1"></a>data<span class="op">=</span>[]</span>
+<span id="cb2-15"><a href="#cb2-15" tabindex="-1"></a></span>
+<span id="cb2-16"><a href="#cb2-16" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> <span class="bu">range</span>(<span class="dv">374</span>):</span>
+<span id="cb2-17"><a href="#cb2-17" tabindex="-1"></a>    line<span class="op">=</span>data_f.readline()</span>
+<span id="cb2-18"><a href="#cb2-18" tabindex="-1"></a>    <span class="bu">print</span>(line)</span>
+<span id="cb2-19"><a href="#cb2-19" tabindex="-1"></a>    data.append(json.loads(line[<span class="dv">1</span>:<span class="op">-</span><span class="dv">1</span>]))</span>
+<span id="cb2-20"><a href="#cb2-20" tabindex="-1"></a><span class="co">#data.pop(0)</span></span>
+<span id="cb2-21"><a href="#cb2-21" tabindex="-1"></a><span class="co">## Comment out this bit if you don't want the spreadsheet</span></span>
+<span id="cb2-22"><a href="#cb2-22" tabindex="-1"></a></span>
+<span id="cb2-23"><a href="#cb2-23" tabindex="-1"></a>w<span class="op">=</span>csv.writer(data_t)</span>
+<span id="cb2-24"><a href="#cb2-24" tabindex="-1"></a></span>
+<span id="cb2-25"><a href="#cb2-25" tabindex="-1"></a>time <span class="op">=</span> []</span>
+<span id="cb2-26"><a href="#cb2-26" tabindex="-1"></a>date <span class="op">=</span>[]</span>
+<span id="cb2-27"><a href="#cb2-27" tabindex="-1"></a></span>
+<span id="cb2-28"><a href="#cb2-28" tabindex="-1"></a>j<span class="op">=</span><span class="dv">0</span></span>
+<span id="cb2-29"><a href="#cb2-29" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> data:</span>
+<span id="cb2-30"><a href="#cb2-30" tabindex="-1"></a>    <span class="bu">print</span>(data[j])</span>
+<span id="cb2-31"><a href="#cb2-31" tabindex="-1"></a>    <span class="co"># and this bit</span></span>
+<span id="cb2-32"><a href="#cb2-32" tabindex="-1"></a>    w.writerow(data[j].values())</span>
+<span id="cb2-33"><a href="#cb2-33" tabindex="-1"></a>    <span class="cf">if</span> <span class="st">'duration'</span> <span class="kw">in</span> data[j].keys():</span>
+<span id="cb2-34"><a href="#cb2-34" tabindex="-1"></a>        tt<span class="op">=</span>data[j][<span class="st">'duration'</span>]</span>
+<span id="cb2-35"><a href="#cb2-35" tabindex="-1"></a>        <span class="cf">if</span> tt <span class="op">==</span> <span class="st">''</span>:</span>
+<span id="cb2-36"><a href="#cb2-36" tabindex="-1"></a>            <span class="cf">pass</span></span>
+<span id="cb2-37"><a href="#cb2-37" tabindex="-1"></a>        <span class="cf">else</span>:</span>
+<span id="cb2-38"><a href="#cb2-38" tabindex="-1"></a>            t<span class="op">=</span>dt.datetime.strptime(tt,<span class="st">'%H:%M'</span>)</span>
+<span id="cb2-39"><a href="#cb2-39" tabindex="-1"></a>            ttt <span class="op">=</span> dt.timedelta(hours<span class="op">=</span>t.hour, minutes<span class="op">=</span>t.minute, seconds<span class="op">=</span>t.second).total_seconds()<span class="op">/</span>(<span class="dv">60</span><span class="op">*</span><span class="dv">60</span>)</span>
+<span id="cb2-40"><a href="#cb2-40" tabindex="-1"></a>            <span class="bu">print</span>(t,ttt)</span>
+<span id="cb2-41"><a href="#cb2-41" tabindex="-1"></a>            time.append(ttt)</span>
+<span id="cb2-42"><a href="#cb2-42" tabindex="-1"></a>            <span class="cf">if</span> <span class="st">'date'</span> <span class="kw">in</span> data[j].keys():</span>
+<span id="cb2-43"><a href="#cb2-43" tabindex="-1"></a>                date.append(dt.datetime.strptime(data[j][<span class="st">'date'</span>][<span class="dv">0</span>:<span class="dv">10</span>], <span class="st">'%Y-%m-</span><span class="sc">%d</span><span class="st">'</span>))</span>
+<span id="cb2-44"><a href="#cb2-44" tabindex="-1"></a>                <span class="co">#date.append(data[j]['date'][0:10])</span></span>
+<span id="cb2-45"><a href="#cb2-45" tabindex="-1"></a></span>
+<span id="cb2-46"><a href="#cb2-46" tabindex="-1"></a>            <span class="cf">else</span>:</span>
+<span id="cb2-47"><a href="#cb2-47" tabindex="-1"></a>                time.pop(<span class="dv">0</span>)</span>
+<span id="cb2-48"><a href="#cb2-48" tabindex="-1"></a>    j<span class="op">+=</span><span class="dv">1</span></span>
+<span id="cb2-49"><a href="#cb2-49" tabindex="-1"></a></span>
+<span id="cb2-50"><a href="#cb2-50" tabindex="-1"></a>t<span class="op">=</span>[<span class="dv">0</span>]</span>
+<span id="cb2-51"><a href="#cb2-51" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> time:</span>
+<span id="cb2-52"><a href="#cb2-52" tabindex="-1"></a>    t.append(t[<span class="op">-</span><span class="dv">1</span>]<span class="op">+</span>i)</span>
+<span id="cb2-53"><a href="#cb2-53" tabindex="-1"></a></span>
+<span id="cb2-54"><a href="#cb2-54" tabindex="-1"></a>date,time <span class="op">=</span> <span class="bu">zip</span>(<span class="op">*</span><span class="bu">sorted</span>(<span class="bu">zip</span>(date, time)))</span>
+<span id="cb2-55"><a href="#cb2-55" tabindex="-1"></a></span>
+<span id="cb2-56"><a href="#cb2-56" tabindex="-1"></a>plt.plot(date,t[<span class="dv">1</span>:], <span class="st">'ko-'</span>)</span>
+<span id="cb2-57"><a href="#cb2-57" tabindex="-1"></a>plt.xlabel(<span class="st">'Year'</span>)</span>
+<span id="cb2-58"><a href="#cb2-58" tabindex="-1"></a>plt.ylabel(<span class="st">'Total time spent in space to date (hours)'</span>)</span>
+<span id="cb2-59"><a href="#cb2-59" tabindex="-1"></a>plt.tight_layout()</span>
+<span id="cb2-60"><a href="#cb2-60" tabindex="-1"></a>plt.savefig(g_file)</span>
+<span id="cb2-61"><a href="#cb2-61" tabindex="-1"></a>plt.show()</span></code></pre>
 </div>
 <p>Let’s make sure we commit our changes.</p>
 <div class="codewrapper sourceCode" id="cb3">
@@ -615,7 +613,7 @@ <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
 <div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
 <div class="accordion-body">
-<p>Yes, <span class="math display">\[9.81 m/s^2 \]</span> is the <a href="https://en.wikipedia.org/wiki/Gravity_of_Earth" class="external-link">gravitational
+<p><span class="math display">\[ 9.81 m/s^2 \]</span> is the <a href="https://en.wikipedia.org/wiki/Gravity_of_Earth" class="external-link">gravitational
 force exerted by the Earth</a>. It is often referred to as “little g” to
 distinguish it from “big G” which is the <a href="https://en.wikipedia.org/wiki/Gravitational_constant" class="external-link">Gravitational
 Constant</a>. A more descriptive name for this variable therefore might
@@ -629,12 +627,12 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 </div>
 </div>
-<div id="challenge2" class="callout challenge">
+<div id="rename-our-variables-to-be-more-descriptive" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
 </div>
-<div class="callout-inner">
-<h3 class="callout-title">Challenge</h3>
+<div id="rename-our-variables-to-be-more-descriptive" class="callout-inner">
+<h3 class="callout-title">Rename our variables to be more descriptive</h3>
 <div class="callout-content">
 <p>Let’s apply this to <code>eva_data_analysis.py</code>.</p>
 <ol style="list-style-type: lower-alpha"><li>
@@ -661,16 +659,16 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <div class="codewrapper sourceCode" id="cb6">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a></span>
-<span id="cb6-2"><a href="#cb6-2" tabindex="-1"></a><span class="im">import</span> json</span>
-<span id="cb6-3"><a href="#cb6-3" tabindex="-1"></a><span class="im">import</span> csv</span>
-<span id="cb6-4"><a href="#cb6-4" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
-<span id="cb6-5"><a href="#cb6-5" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb6-6"><a href="#cb6-6" tabindex="-1"></a></span>
-<span id="cb6-7"><a href="#cb6-7" tabindex="-1"></a><span class="co"># Data source: https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb6-8"><a href="#cb6-8" tabindex="-1"></a>input_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb6-9"><a href="#cb6-9" tabindex="-1"></a>output_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>, <span class="st">'w'</span>)</span>
-<span id="cb6-10"><a href="#cb6-10" tabindex="-1"></a>graph_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span></span>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a><span class="im">import</span> json</span>
+<span id="cb6-2"><a href="#cb6-2" tabindex="-1"></a><span class="im">import</span> csv</span>
+<span id="cb6-3"><a href="#cb6-3" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
+<span id="cb6-4"><a href="#cb6-4" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb6-5"><a href="#cb6-5" tabindex="-1"></a></span>
+<span id="cb6-6"><a href="#cb6-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb6-7"><a href="#cb6-7" tabindex="-1"></a>input_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb6-8"><a href="#cb6-8" tabindex="-1"></a>output_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>, <span class="st">'w'</span>)</span>
+<span id="cb6-9"><a href="#cb6-9" tabindex="-1"></a>graph_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span></span>
+<span id="cb6-10"><a href="#cb6-10" tabindex="-1"></a></span>
 <span id="cb6-11"><a href="#cb6-11" tabindex="-1"></a></span>
 <span id="cb6-12"><a href="#cb6-12" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
 <span id="cb6-13"><a href="#cb6-13" tabindex="-1"></a></span>
@@ -973,18 +971,19 @@ <h3 class="callout-title">Callout</h3>
 <p>Looking at our code, you may notice it contains different pieces of
 functionality:</p>
 <ol style="list-style-type: decimal"><li>reading the data from a JSON file</li>
+<li>converting and saving the data in the CSV format</li>
 <li>processing/cleaning the data and preparing it for analysis</li>
 <li>data analysis and visualising the results</li>
-<li>converting and saving the data in the CSV format</li>
 </ol><p>Let’s refactor our code so that reading the data in JSON format into
 a dataframe (step 1.) and converting it and saving to the CSV format
-(step 4.) are extracted into separate functions. Let’s name those
+(step 2.) are extracted into separate functions. Let’s name those
 functions <code>read_json_to_dataframe</code> and
 <code>write_dataframe_to_csv</code> respectively. The main part of the
 script should then be simplified to invoke these new functions, while
 the functions themselves contain the complexity of each of these two
-steps.</p>
-<p>Our code may look something like the following.</p>
+steps. We will continue to work on steps 3. and 4. above later on.</p>
+<p>After the initial refactoring, our code may look something like the
+following.</p>
 <div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -1036,17 +1035,21 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <span id="cb17-46"><a href="#cb17-46" tabindex="-1"></a></span>
 <span id="cb17-47"><a href="#cb17-47" tabindex="-1"></a><span class="bu">print</span>(<span class="st">"--END--"</span>)</span></code></pre>
 </div>
-<p>We have chosen to create function for reading in and writing out data
-files since this is a very common task within research software. While
-these functions do not contain that many lines of code due to using the
-<code>pandas</code> in-built methods that do all the complex data
-reading, converting and writing operations, it can be useful to package
-these steps together into reusable functions if you need to read in or
-write out a lot of similarly structured files and process them in the
-same way.</p>
+<p>We have chosen to create functions for reading in and writing out
+data files since this is a very common task within research software.
+While these functions do not contain that many lines of code due to
+using the <code>pandas</code> in-built methods that do all the complex
+data reading, converting and writing operations, it can be useful to
+package these steps together into reusable functions if you need to read
+in or write out a lot of similarly structured files and process them in
+the same way.</p>
 </section><section><h2 class="section-heading" id="use-docstrings-to-document-functions">Use docstrings to document functions<a class="anchor" aria-label="anchor" href="#use-docstrings-to-document-functions"></a></h2>
-<hr class="half-width"><p>Docstrings are a specific type of documentation that are provided
-within functions and <a href="https://docs.python.org/3/tutorial/classes.html" class="external-link">Python
+<hr class="half-width"><p>Now that we have written some functions, it is time to document them
+so that we can quickly recall (and others looking at our code in the
+future can understand) what the functions doe without having to read the
+code.</p>
+<p><em>Docstrings</em> are a specific type of documentation that are
+provided within functions and <a href="https://docs.python.org/3/tutorial/classes.html" class="external-link">Python
 classes</a>. A function docstring should explain what that particular
 code is doing, what parameters the function needs (inputs) and what form
 they should take, what the function outputs (you may see words like
@@ -1344,7 +1347,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1366,8 +1369,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/06-code-readability.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/06-code-readability.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/07-code-structure.html b/07-code-structure.html
index 4d973c66..ce1e03ad 100644
--- a/07-code-structure.html
+++ b/07-code-structure.html
@@ -301,7 +301,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -374,7 +374,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code structure</h1>
-        <p>Last updated on 2024-09-26 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/07-code-structure.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -393,7 +393,7 @@ <h2 class="card-header">Overview</h2>
 <div class="card-body">
 <div class="inner">
 <h3 class="card-title">Questions</h3>
-<ul><li>How can we bests structure code?</li>
+<ul><li>How can we best structure code?</li>
 <li>What is a common code structure (pattern) for creating software that
 can read input from command line?</li>
 <li>What are conventional places to store data, code, results, tests,
@@ -645,7 +645,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 set by the Python interpreter before the execution of any code in the
 source file. What value is given by the interpreter to
 <code>__name__</code> is determined by the manner in which the script is
-loaded.</p>
+invoked.</p>
 <p>If we run the source file directly using the Python interpreter,
 e.g.:</p>
 <div class="codewrapper sourceCode" id="cb5">
@@ -670,7 +670,8 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="im">import</span> eva_data_analysis</span></code></pre>
 </div>
 <p>then the Python interpreter will assign the name “eva_data_analysis”
-from the import statement to the <code>__name__</code> variable:</p>
+from the import statement to the <code>__name__</code> variable (note
+that import statement matches our script’s name):</p>
 <div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -687,7 +688,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 another script, there are a number of situations in which you would want
 to do this:</p>
 <ul><li>for testing of your code, you can have your testing framework import
-the main script, and run special test functions which then call the
+your script, and run special test functions which then call the
 <code>main</code> function directly;</li>
 <li>where you want to not only be able to run your script from the
 command-line, but also provide a programmer-friendly application
@@ -828,7 +829,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python eva_data_analysis.py eva_data.json eva_data.csv</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python eva_data_analysis.py eva-data.json eva-data.csv</span></code></pre>
 </div>
 <p>Remember to commit our changes.</p>
 <div class="codewrapper sourceCode" id="cb11">
@@ -881,7 +882,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <ul><li>Code and data should be version controlled; you can also version
 control manuscripts, results, etc.</li>
 <li>If data files are too large (or contain sensitive information) to
-track by version control, untrack them using .gitignore</li>
+track by version control, untrack them using
+<code>.gitignore</code>
+</li>
 <li>Use tags/releases to mark specific versions of results (a version
 submitted to a journal, dissertation version, poster version, etc.) so
 as to avoid using version numbers in file names and proliferation of
@@ -921,7 +924,8 @@ <h3 class="callout-title">Challenge</h3>
 <div class="callout-content">
 <p>Refactor your software project so that input data is stored in
 <code>data/</code> directory and results (the graph and CSV data files)
-saved in <code>results/</code> directory.</p>
+saved in <code>results/</code> directory. Remember to create the
+<code>results/</code> directory or your code will fail.</p>
 </div>
 </div>
 </div>
@@ -1062,20 +1066,13 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 </div>
 </div>
-<p>After the above exercise, you will be invoking your script from
-command line as:</p>
-<div class="codewrapper sourceCode" id="cb14">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python data/eva_data_analysis.py eva_data.json results/eva_data.csv</span></code></pre>
-</div>
 <p>Remember to commit your latest changes:</p>
-<div class="codewrapper sourceCode" id="cb15">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git status</span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add eva_data_analysis.py data results</span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Update project's directory structure"</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git status</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add eva_data_analysis.py data results</span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Update project's directory structure"</span></span></code></pre>
 </div>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a></h2>
 <hr class="half-width"><p>We recommend the following resources for some additional reading on
@@ -1141,7 +1138,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1163,8 +1160,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/07-code-structure.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/07-code-structure.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/08-code-correctness.html b/08-code-correctness.html
index a4108979..3ad9373d 100644
--- a/08-code-correctness.html
+++ b/08-code-correctness.html
@@ -306,7 +306,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -379,7 +379,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code correctness</h1>
-        <p>Last updated on 2024-09-26 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/08-code-correctness.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -537,7 +537,7 @@ <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </div>
 </section><section><h2 class="section-heading" id="informal-testing">Informal testing<a class="anchor" aria-label="anchor" href="#informal-testing"></a></h2>
 <hr class="half-width"><p>How should we test our code? One approach is to copy/paste the code
-or a function into a Python terminal (different from command line
+or a function into a Python terminal (different from a command line
 terminal), which allows you to interact with the Python interpreter more
 directly.<br>
 From the Python terminal we can then run one function or a piece of code
@@ -672,35 +672,29 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <li>Are recorded in a test script that can be re-run on demand.</li>
 </ul><p>Let’s explore this process by writing some formal tests for our
 <code>text_to_duration</code> function.</p>
-<p>Let’s create a new Python file <code>test_code.py</code> in the root
-of our project directory to store our tests.</p>
-<div class="codewrapper sourceCode" id="cb7">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> cd spacewalks</span>
-<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch test_code.py</span></code></pre>
-</div>
+<p>In VS Code, create a new Python file <code>test_code.py</code> in the
+root of our project directory to store our tests.</p>
 <p>Like before in the Python terminal, we need to import
 <code>text_to_duration</code> into our test script. Then, we add our
 first test function:</p>
-<div class="codewrapper sourceCode" id="cb8">
+<div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a></span>
-<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a></span>
-<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a>    input_value <span class="op">=</span> <span class="st">"10:00"</span></span>
-<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a>    test_result <span class="op">=</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>    <span class="bu">print</span>(<span class="ss">f"text_to_duration('10:00') == 10? </span><span class="sc">{</span>test_result<span class="sc">}</span><span class="ss">"</span>)</span>
-<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a></span>
-<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a>test_text_to_duration()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a></span>
+<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb7-3"><a href="#cb7-3" tabindex="-1"></a></span>
+<span id="cb7-4"><a href="#cb7-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb7-5"><a href="#cb7-5" tabindex="-1"></a>    input_value <span class="op">=</span> <span class="st">"10:00"</span></span>
+<span id="cb7-6"><a href="#cb7-6" tabindex="-1"></a>    test_result <span class="op">=</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb7-7"><a href="#cb7-7" tabindex="-1"></a>    <span class="bu">print</span>(<span class="ss">f"text_to_duration('10:00') == 10? </span><span class="sc">{</span>test_result<span class="sc">}</span><span class="ss">"</span>)</span>
+<span id="cb7-8"><a href="#cb7-8" tabindex="-1"></a></span>
+<span id="cb7-9"><a href="#cb7-9" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <p>We can run this code from the command line terminal as:</p>
-<div class="codewrapper sourceCode" id="cb9">
+<div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span><span class="ex">$</span> python3 test_code.py </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span><span class="ex">$</span> python3 test_code.py </span></code></pre>
 </div>
 <p>This test checks that when we apply <code>text_to_duration</code> to
 input value <code>10:00</code>, the output matches the expected value of
@@ -721,16 +715,16 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <code>False</code>, <code>assert</code> raises an
 <code>AssertError</code>.</p>
 <p>Let’s rewrite our test with an <code>assert</code> statement:</p>
-<div class="codewrapper sourceCode" id="cb10">
+<div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a></span>
-<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a></span>
-<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a></span>
-<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a></span>
+<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a></span>
+<span id="cb9-4"><a href="#cb9-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb9-5"><a href="#cb9-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb9-6"><a href="#cb9-6" tabindex="-1"></a></span>
+<span id="cb9-7"><a href="#cb9-7" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <p>Notice that when we run <code>test_text_to_duration_integer()</code>,
 nothing happens - there is no output. That is because our function is
@@ -738,75 +732,78 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <p>Let’s add another test to check what happens when duration is not an
 integer number and if our function can handle durations with a non-zero
 minute component, and rerun our test code.</p>
-<div class="codewrapper sourceCode" id="cb11">
+<div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb11-2"><a href="#cb11-2" tabindex="-1"></a></span>
-<span id="cb11-3"><a href="#cb11-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb11-4"><a href="#cb11-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:15"</span>) <span class="op">==</span> <span class="fl">10.25</span></span>
-<span id="cb11-5"><a href="#cb11-5" tabindex="-1"></a></span>
-<span id="cb11-6"><a href="#cb11-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb11-7"><a href="#cb11-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb11-8"><a href="#cb11-8" tabindex="-1"></a></span>
-<span id="cb11-9"><a href="#cb11-9" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb11-10"><a href="#cb11-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a></span>
+<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:15"</span>) <span class="op">==</span> <span class="fl">10.25</span></span>
+<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a></span>
+<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb10-8"><a href="#cb10-8" tabindex="-1"></a></span>
+<span id="cb10-9"><a href="#cb10-9" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb10-10"><a href="#cb10-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="error" tabindex="0"><code>(venv_spacewalks) $ python3 test_code.py
 Traceback (most recent call last):
-  File "/Users/user/work/SSI/lessons/astronaut-data-analysis/test_code.py", line 12, in &lt;module&gt;
+  File "/Users/user/Desktop/spacewalks/test_code.py", line 9, in &lt;module&gt;
     test_text_to_duration_float()
-  File "/Users/user/work/SSI/lessons/astronaut-data-analysis/test_code.py", line 5, in test_text_to_duration_float
+  File "/Users/user/Desktop/spacewalks/test_code.py", line 4, in test_text_to_duration_float
     assert text_to_duration("10:15") == 10.25
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-AssertionError
-</code></pre>
+AssertionError</code></pre>
 </div>
 <p>Notice that this time, our test
 <code>test_text_to_duration_float</code> fails. Our assert statement has
 raised an <code>AssertionError</code> - a clear signal that there is a
-problem in our code that we need to fix. Python helpfully tells us which
-line of our code is problematic:</p>
-<div class="codewrapper sourceCode" id="cb13">
+problem in our code that we need to fix. We know that duration
+<code>10:15</code> should be converted to number <code>10.25</code>.
+What is wrong with our code? If we look at our
+<code>text_to_duration</code> function, we may identify the following
+line of our code as problematic:</p>
+<div class="codewrapper sourceCode" id="cb12">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a>...</span>
-<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span> </span>
-<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="kw">def</span> text_to_duration(duration):</span>
+<span id="cb12-2"><a href="#cb12-2" tabindex="-1"></a>    ...</span>
+<span id="cb12-3"><a href="#cb12-3" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span> </span>
+<span id="cb12-4"><a href="#cb12-4" tabindex="-1"></a>    ...</span></code></pre>
 </div>
 <p>You may notice that our conversion code is wrong - the minutes
 component should have been divided by 60 and not 6. We were able to spot
 this tiny bug by testing our code.</p>
 <p>Let’s fix the problematic line and rerun out tests.</p>
-<div class="codewrapper sourceCode" id="cb14">
+<div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a>...</span>
-<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">60</span> </span>
-<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a>...</span>
+<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">60</span> </span>
+<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a>...</span></code></pre>
 </div>
 <p>This time our tests run without problem.</p>
 <p>Should we add more tests or the tests we have so far are enough? What
-happens if our duration value is <code>01:20</code> (one hour and 20
-minutes) and our result is not a rational floating point number like
-<code>10.25</code> but an irrational number such as
+happens if our duration value is <code>10:20</code> (ten hours and 20
+minutes) and our result is not a rational floating point number (like
+<code>10.25</code>) but an irrational number such as
 <code>10.333333333</code>? Let’s tests for this.</p>
-<div class="codewrapper sourceCode" id="cb15">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a></span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> <span class="fl">10.333333</span></span>
-<span id="cb15-5"><a href="#cb15-5" tabindex="-1"></a></span>
-<span id="cb15-6"><a href="#cb15-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb15-7"><a href="#cb15-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb15-8"><a href="#cb15-8" tabindex="-1"></a></span>
-<span id="cb15-9"><a href="#cb15-9" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb15-10"><a href="#cb15-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a></span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb14-4"><a href="#cb14-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> <span class="fl">10.333333</span></span>
+<span id="cb14-5"><a href="#cb14-5" tabindex="-1"></a></span>
+<span id="cb14-6"><a href="#cb14-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb14-7"><a href="#cb14-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb14-8"><a href="#cb14-8" tabindex="-1"></a></span>
+<span id="cb14-9"><a href="#cb14-9" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb14-10"><a href="#cb14-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -826,13 +823,13 @@ <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></
 (<code>==</code>) to compare the equality of floating point numbers.
 Instead, we check that our floating point numbers are equal within a
 very small tolerance (e.g. 1e-5). Hence, our code should look like:</p>
-<div class="codewrapper sourceCode" id="cb17">
+<div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a>...</span>
-<span id="cb17-2"><a href="#cb17-2" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb17-3"><a href="#cb17-3" tabindex="-1"></a>    <span class="cf">assert</span> <span class="bu">abs</span>(text_to_duration(<span class="st">"10:20"</span>) <span class="op">-</span> <span class="fl">10.33333333</span>) <span class="op">&lt;</span> <span class="fl">1e-5</span></span>
-<span id="cb17-4"><a href="#cb17-4" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a>...</span>
+<span id="cb16-2"><a href="#cb16-2" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb16-3"><a href="#cb16-3" tabindex="-1"></a>    <span class="cf">assert</span> <span class="bu">abs</span>(text_to_duration(<span class="st">"10:20"</span>) <span class="op">-</span> <span class="fl">10.33333333</span>) <span class="op">&lt;</span> <span class="fl">1e-5</span></span>
+<span id="cb16-4"><a href="#cb16-4" tabindex="-1"></a>...</span></code></pre>
 </div>
 <p>You may have noticed that we have to repeat a lot of code to add each
 individual test for each test case. You may also have noticed that our
@@ -851,10 +848,10 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 code coverage extension <code>pytest-cov</code>. To install these
 libraries into our virtual environment, from the command line terminal
 do:</p>
-<div class="codewrapper sourceCode" id="cb18">
+<div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip install pytest pytest-cov</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip install pytest pytest-cov</span></code></pre>
 </div>
 <p>Let’s make sure that our tests are ready to work with
 <code>pytest</code>.</p>
@@ -866,12 +863,12 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 requirements, so there is nothing to do here. However, our script does
 contain lines to run each of our test functions. These are no-longer
 required as pytest will run our tests so we can remove them:</p>
-<div class="codewrapper sourceCode" id="cb19">
+<div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="co"># Delete these 2 lines</span></span>
-<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="co"># Delete these 2 lines</span></span>
+<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 </li>
 <li><p>It is also conventional when working with a testing framework to
@@ -883,55 +880,57 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 test suite is currently located in the root folder of our project. Let’s
 move it to a dedicated test folder and rename our
 <code>test_code.py</code> file to <code>test_eva_analysis.py</code>.</p>
-<div class="codewrapper sourceCode" id="cb20">
+<p>You can do it from VS Code or by typing the following commands in the
+command line terminal:</p>
+<div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir tests</span>
-<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mv test_code.py tests/test_eva_analysis.py</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir tests</span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mv test_code.py tests/test_eva_analysis.py</span></code></pre>
 </div>
 <p>Before we re-run our tests using <code>pytest</code>, let’s update
 our second test to use <code>pytest</code>’s function
 <code>approx()</code> which is specifically intended for comparing
 floating point numbers within a tolerance.</p>
-<div class="codewrapper sourceCode" id="cb21">
+<div class="codewrapper sourceCode" id="cb20">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a></span>
-<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> pytest.approx(<span class="fl">10.33333333</span>)</span>
-<span id="cb21-6"><a href="#cb21-6" tabindex="-1"></a></span>
-<span id="cb21-7"><a href="#cb21-7" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb21-8"><a href="#cb21-8" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb20-3"><a href="#cb20-3" tabindex="-1"></a></span>
+<span id="cb20-4"><a href="#cb20-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb20-5"><a href="#cb20-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> pytest.approx(<span class="fl">10.33333333</span>)</span>
+<span id="cb20-6"><a href="#cb20-6" tabindex="-1"></a></span>
+<span id="cb20-7"><a href="#cb20-7" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb20-8"><a href="#cb20-8" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span></code></pre>
 </div>
 <p>Let’s also add some inline comments to clarify what each test is
 doing and expand our syntax to highlight the logic behind our
 approach:</p>
-<div class="codewrapper sourceCode" id="cb22">
+<div class="codewrapper sourceCode" id="cb21">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a></span>
-<span id="cb22-4"><a href="#cb22-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb22-5"><a href="#cb22-5" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb22-6"><a href="#cb22-6" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
-<span id="cb22-7"><a href="#cb22-7" tabindex="-1"></a><span class="co">    for typical durations with a non-zero minute component</span></span>
-<span id="cb22-8"><a href="#cb22-8" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb22-9"><a href="#cb22-9" tabindex="-1"></a>    actual_result <span class="op">=</span> text_to_duration(<span class="st">"10:20"</span>) </span>
-<span id="cb22-10"><a href="#cb22-10" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="fl">10.33333333</span></span>
-<span id="cb22-11"><a href="#cb22-11" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> pytest.approx(expected_result)</span>
-<span id="cb22-12"><a href="#cb22-12" tabindex="-1"></a>    </span>
-<span id="cb22-13"><a href="#cb22-13" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb22-14"><a href="#cb22-14" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb22-15"><a href="#cb22-15" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
-<span id="cb22-16"><a href="#cb22-16" tabindex="-1"></a><span class="co">    for typical whole hour durations </span></span>
-<span id="cb22-17"><a href="#cb22-17" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb22-18"><a href="#cb22-18" tabindex="-1"></a>    actual_result <span class="op">=</span>  text_to_duration(<span class="st">"10:00"</span>)</span>
-<span id="cb22-19"><a href="#cb22-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">10</span></span>
-<span id="cb22-20"><a href="#cb22-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb22-21"><a href="#cb22-21" tabindex="-1"></a>    </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a></span>
+<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb21-6"><a href="#cb21-6" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
+<span id="cb21-7"><a href="#cb21-7" tabindex="-1"></a><span class="co">    for typical durations with a non-zero minute component</span></span>
+<span id="cb21-8"><a href="#cb21-8" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb21-9"><a href="#cb21-9" tabindex="-1"></a>    actual_result <span class="op">=</span> text_to_duration(<span class="st">"10:20"</span>) </span>
+<span id="cb21-10"><a href="#cb21-10" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="fl">10.33333333</span></span>
+<span id="cb21-11"><a href="#cb21-11" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> pytest.approx(expected_result)</span>
+<span id="cb21-12"><a href="#cb21-12" tabindex="-1"></a>    </span>
+<span id="cb21-13"><a href="#cb21-13" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb21-14"><a href="#cb21-14" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb21-15"><a href="#cb21-15" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
+<span id="cb21-16"><a href="#cb21-16" tabindex="-1"></a><span class="co">    for typical whole hour durations </span></span>
+<span id="cb21-17"><a href="#cb21-17" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb21-18"><a href="#cb21-18" tabindex="-1"></a>    actual_result <span class="op">=</span>  text_to_duration(<span class="st">"10:00"</span>)</span>
+<span id="cb21-19"><a href="#cb21-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">10</span></span>
+<span id="cb21-20"><a href="#cb21-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb21-21"><a href="#cb21-21" tabindex="-1"></a>    </span></code></pre>
 </div>
 <p>Writing our tests this way highlights the key idea that each test
 should compare the actual results returned by our function with expected
@@ -939,23 +938,23 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <p>Similarly, writing inline comments for our tests that complete the
 sentence “Test that …” helps us to understand what each test is doing
 and why it is needed.</p>
-<p>Before running out tests with <code>putest</code>, let’s reintroduce
+<p>Before running out tests with <code>pytest</code>, let’s reintroduce
 our old bug in function <code>text_to_duration</code> that affects the
 durations with a non-zero minute component like “10:20” but not those
 that are whole hours, e.g. “10:00”:</p>
-<div class="codewrapper sourceCode" id="cb23">
+<div class="codewrapper sourceCode" id="cb22">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a>    ...</span>
-<span id="cb23-2"><a href="#cb23-2" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span>  <span class="co"># Divide by 6 instead of 60</span></span>
-<span id="cb23-3"><a href="#cb23-3" tabindex="-1"></a>    ...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a>    ...</span>
+<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span>  <span class="co"># Divide by 6 instead of 60</span></span>
+<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a>    ...</span></code></pre>
 </div>
 <p>Finally, let’s run our tests with <code>pytest</code> from our
 project’s root directory (and not <code>tests</code> directory):</p>
-<div class="codewrapper sourceCode" id="cb24">
+<div class="codewrapper sourceCode" id="cb23">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest </span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1008,6 +1007,7 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 
 =========================================== 2 passed in 0.63s =============================================</code></pre>
 </div>
+<p>This time, all out tests passed.</p>
 <div id="interpreting-pytest-output" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
@@ -1120,70 +1120,70 @@ <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 that alone is not enough to properly test code. We will now look into
 what makes a good test suite and good practices for testing code.</p>
 <p>Let’s start by considering the following scenario. A collaborator on
-our project has sent us the following code which adds a new column to
-our data containing the <code>crew_size</code> values capturing the
-number of astronauts participating in any given spacewalk. How do we
-know that it works as intended and that it will not break the rest of
-our code? For this, we need to write a test suite with a comprehensive
-coverage of the new code.</p>
-<div class="codewrapper sourceCode" id="cb28">
+our project has sent us the following code which adds a new column
+called <code>crew_size</code> to our data containing the number of
+astronauts participating in any given spacewalk. How do we know that it
+works as intended and that it will not break the rest of our code? For
+this, we need to write a test suite with a comprehensive coverage of the
+new code.</p>
+<div class="codewrapper sourceCode" id="cb27">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb28-1"><a href="#cb28-1" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb28-2"><a href="#cb28-2" tabindex="-1"></a><span class="im">import</span> pandas <span class="im">as</span> pd</span>
-<span id="cb28-3"><a href="#cb28-3" tabindex="-1"></a><span class="im">import</span> sys</span>
-<span id="cb28-4"><a href="#cb28-4" tabindex="-1"></a><span class="im">import</span> re <span class="co"># added this line</span></span>
-<span id="cb28-5"><a href="#cb28-5" tabindex="-1"></a></span>
-<span id="cb28-6"><a href="#cb28-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb28-7"><a href="#cb28-7" tabindex="-1"></a></span>
-<span id="cb28-8"><a href="#cb28-8" tabindex="-1"></a><span class="kw">def</span> main(input_file, output_file, graph_file):</span>
-<span id="cb28-9"><a href="#cb28-9" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--START--"</span>)</span>
-<span id="cb28-10"><a href="#cb28-10" tabindex="-1"></a></span>
-<span id="cb28-11"><a href="#cb28-11" tabindex="-1"></a>    eva_data <span class="op">=</span> read_json_to_dataframe(input_file)</span>
-<span id="cb28-12"><a href="#cb28-12" tabindex="-1"></a></span>
-<span id="cb28-13"><a href="#cb28-13" tabindex="-1"></a>    eva_data <span class="op">=</span> add_crew_size_column(eva_data) <span class="co"># added this line</span></span>
-<span id="cb28-14"><a href="#cb28-14" tabindex="-1"></a></span>
-<span id="cb28-15"><a href="#cb28-15" tabindex="-1"></a>    write_dataframe_to_csv(eva_data, output_file)</span>
-<span id="cb28-16"><a href="#cb28-16" tabindex="-1"></a></span>
-<span id="cb28-17"><a href="#cb28-17" tabindex="-1"></a>    plot_cumulative_time_in_space(eva_data, graph_file)</span>
-<span id="cb28-18"><a href="#cb28-18" tabindex="-1"></a></span>
-<span id="cb28-19"><a href="#cb28-19" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--END--"</span>)</span>
-<span id="cb28-20"><a href="#cb28-20" tabindex="-1"></a></span>
-<span id="cb28-21"><a href="#cb28-21" tabindex="-1"></a>... </span>
-<span id="cb28-22"><a href="#cb28-22" tabindex="-1"></a></span>
-<span id="cb28-23"><a href="#cb28-23" tabindex="-1"></a><span class="kw">def</span> calculate_crew_size(crew):</span>
-<span id="cb28-24"><a href="#cb28-24" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb28-25"><a href="#cb28-25" tabindex="-1"></a><span class="co">    Calculate the size of the crew for a single crew entry</span></span>
-<span id="cb28-26"><a href="#cb28-26" tabindex="-1"></a></span>
-<span id="cb28-27"><a href="#cb28-27" tabindex="-1"></a><span class="co">    Args:</span></span>
-<span id="cb28-28"><a href="#cb28-28" tabindex="-1"></a><span class="co">        crew (str): The text entry in the crew column containing a list of crew member names</span></span>
-<span id="cb28-29"><a href="#cb28-29" tabindex="-1"></a></span>
-<span id="cb28-30"><a href="#cb28-30" tabindex="-1"></a><span class="co">    Returns:</span></span>
-<span id="cb28-31"><a href="#cb28-31" tabindex="-1"></a><span class="co">        int: The crew size</span></span>
-<span id="cb28-32"><a href="#cb28-32" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb28-33"><a href="#cb28-33" tabindex="-1"></a>    <span class="cf">if</span> crew.split() <span class="op">==</span> []:</span>
-<span id="cb28-34"><a href="#cb28-34" tabindex="-1"></a>        <span class="cf">return</span> <span class="va">None</span></span>
-<span id="cb28-35"><a href="#cb28-35" tabindex="-1"></a>    <span class="cf">else</span>:</span>
-<span id="cb28-36"><a href="#cb28-36" tabindex="-1"></a>        <span class="cf">return</span> <span class="bu">len</span>(re.split(<span class="vs">r';'</span>, crew))<span class="op">-</span><span class="dv">1</span></span>
-<span id="cb28-37"><a href="#cb28-37" tabindex="-1"></a></span>
-<span id="cb28-38"><a href="#cb28-38" tabindex="-1"></a><span class="kw">def</span> add_crew_size_column(df):</span>
-<span id="cb28-39"><a href="#cb28-39" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb28-40"><a href="#cb28-40" tabindex="-1"></a><span class="co">    Add crew_size column to the dataset containing the value of the crew size</span></span>
-<span id="cb28-41"><a href="#cb28-41" tabindex="-1"></a></span>
-<span id="cb28-42"><a href="#cb28-42" tabindex="-1"></a><span class="co">    Args:</span></span>
-<span id="cb28-43"><a href="#cb28-43" tabindex="-1"></a><span class="co">        df (pd.DataFrame): The input data frame.</span></span>
-<span id="cb28-44"><a href="#cb28-44" tabindex="-1"></a></span>
-<span id="cb28-45"><a href="#cb28-45" tabindex="-1"></a><span class="co">    Returns:</span></span>
-<span id="cb28-46"><a href="#cb28-46" tabindex="-1"></a><span class="co">        df_copy (pd.DataFrame): A copy of df with the new crew_size variable added</span></span>
-<span id="cb28-47"><a href="#cb28-47" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb28-48"><a href="#cb28-48" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">'Adding crew size variable (crew_size) to dataset'</span>)</span>
-<span id="cb28-49"><a href="#cb28-49" tabindex="-1"></a>    df_copy <span class="op">=</span> df.copy()</span>
-<span id="cb28-50"><a href="#cb28-50" tabindex="-1"></a>    df_copy[<span class="st">"crew_size"</span>] <span class="op">=</span> df_copy[<span class="st">"crew"</span>].<span class="bu">apply</span>(</span>
-<span id="cb28-51"><a href="#cb28-51" tabindex="-1"></a>        calculate_crew_size</span>
-<span id="cb28-52"><a href="#cb28-52" tabindex="-1"></a>    )</span>
-<span id="cb28-53"><a href="#cb28-53" tabindex="-1"></a>    <span class="cf">return</span> df_copy</span>
-<span id="cb28-54"><a href="#cb28-54" tabindex="-1"></a>...</span>
-<span id="cb28-55"><a href="#cb28-55" tabindex="-1"></a>    </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb27-2"><a href="#cb27-2" tabindex="-1"></a><span class="im">import</span> pandas <span class="im">as</span> pd</span>
+<span id="cb27-3"><a href="#cb27-3" tabindex="-1"></a><span class="im">import</span> sys</span>
+<span id="cb27-4"><a href="#cb27-4" tabindex="-1"></a><span class="im">import</span> re <span class="co"># added this line</span></span>
+<span id="cb27-5"><a href="#cb27-5" tabindex="-1"></a></span>
+<span id="cb27-6"><a href="#cb27-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb27-7"><a href="#cb27-7" tabindex="-1"></a></span>
+<span id="cb27-8"><a href="#cb27-8" tabindex="-1"></a><span class="kw">def</span> main(input_file, output_file, graph_file):</span>
+<span id="cb27-9"><a href="#cb27-9" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--START--"</span>)</span>
+<span id="cb27-10"><a href="#cb27-10" tabindex="-1"></a></span>
+<span id="cb27-11"><a href="#cb27-11" tabindex="-1"></a>    eva_data <span class="op">=</span> read_json_to_dataframe(input_file)</span>
+<span id="cb27-12"><a href="#cb27-12" tabindex="-1"></a></span>
+<span id="cb27-13"><a href="#cb27-13" tabindex="-1"></a>    eva_data <span class="op">=</span> add_crew_size_column(eva_data) <span class="co"># added this line</span></span>
+<span id="cb27-14"><a href="#cb27-14" tabindex="-1"></a></span>
+<span id="cb27-15"><a href="#cb27-15" tabindex="-1"></a>    write_dataframe_to_csv(eva_data, output_file)</span>
+<span id="cb27-16"><a href="#cb27-16" tabindex="-1"></a></span>
+<span id="cb27-17"><a href="#cb27-17" tabindex="-1"></a>    plot_cumulative_time_in_space(eva_data, graph_file)</span>
+<span id="cb27-18"><a href="#cb27-18" tabindex="-1"></a></span>
+<span id="cb27-19"><a href="#cb27-19" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--END--"</span>)</span>
+<span id="cb27-20"><a href="#cb27-20" tabindex="-1"></a></span>
+<span id="cb27-21"><a href="#cb27-21" tabindex="-1"></a>... </span>
+<span id="cb27-22"><a href="#cb27-22" tabindex="-1"></a></span>
+<span id="cb27-23"><a href="#cb27-23" tabindex="-1"></a><span class="kw">def</span> calculate_crew_size(crew):</span>
+<span id="cb27-24"><a href="#cb27-24" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb27-25"><a href="#cb27-25" tabindex="-1"></a><span class="co">    Calculate the size of the crew for a single crew entry</span></span>
+<span id="cb27-26"><a href="#cb27-26" tabindex="-1"></a></span>
+<span id="cb27-27"><a href="#cb27-27" tabindex="-1"></a><span class="co">    Args:</span></span>
+<span id="cb27-28"><a href="#cb27-28" tabindex="-1"></a><span class="co">        crew (str): The text entry in the crew column containing a list of crew member names</span></span>
+<span id="cb27-29"><a href="#cb27-29" tabindex="-1"></a></span>
+<span id="cb27-30"><a href="#cb27-30" tabindex="-1"></a><span class="co">    Returns:</span></span>
+<span id="cb27-31"><a href="#cb27-31" tabindex="-1"></a><span class="co">        int: The crew size</span></span>
+<span id="cb27-32"><a href="#cb27-32" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb27-33"><a href="#cb27-33" tabindex="-1"></a>    <span class="cf">if</span> crew.split() <span class="op">==</span> []:</span>
+<span id="cb27-34"><a href="#cb27-34" tabindex="-1"></a>        <span class="cf">return</span> <span class="va">None</span></span>
+<span id="cb27-35"><a href="#cb27-35" tabindex="-1"></a>    <span class="cf">else</span>:</span>
+<span id="cb27-36"><a href="#cb27-36" tabindex="-1"></a>        <span class="cf">return</span> <span class="bu">len</span>(re.split(<span class="vs">r';'</span>, crew))<span class="op">-</span><span class="dv">1</span></span>
+<span id="cb27-37"><a href="#cb27-37" tabindex="-1"></a></span>
+<span id="cb27-38"><a href="#cb27-38" tabindex="-1"></a><span class="kw">def</span> add_crew_size_column(df):</span>
+<span id="cb27-39"><a href="#cb27-39" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb27-40"><a href="#cb27-40" tabindex="-1"></a><span class="co">    Add crew_size column to the dataset containing the value of the crew size</span></span>
+<span id="cb27-41"><a href="#cb27-41" tabindex="-1"></a></span>
+<span id="cb27-42"><a href="#cb27-42" tabindex="-1"></a><span class="co">    Args:</span></span>
+<span id="cb27-43"><a href="#cb27-43" tabindex="-1"></a><span class="co">        df (pd.DataFrame): The input data frame.</span></span>
+<span id="cb27-44"><a href="#cb27-44" tabindex="-1"></a></span>
+<span id="cb27-45"><a href="#cb27-45" tabindex="-1"></a><span class="co">    Returns:</span></span>
+<span id="cb27-46"><a href="#cb27-46" tabindex="-1"></a><span class="co">        df_copy (pd.DataFrame): A copy of df with the new crew_size variable added</span></span>
+<span id="cb27-47"><a href="#cb27-47" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb27-48"><a href="#cb27-48" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">'Adding crew size variable (crew_size) to dataset'</span>)</span>
+<span id="cb27-49"><a href="#cb27-49" tabindex="-1"></a>    df_copy <span class="op">=</span> df.copy()</span>
+<span id="cb27-50"><a href="#cb27-50" tabindex="-1"></a>    df_copy[<span class="st">"crew_size"</span>] <span class="op">=</span> df_copy[<span class="st">"crew"</span>].<span class="bu">apply</span>(</span>
+<span id="cb27-51"><a href="#cb27-51" tabindex="-1"></a>        calculate_crew_size</span>
+<span id="cb27-52"><a href="#cb27-52" tabindex="-1"></a>    )</span>
+<span id="cb27-53"><a href="#cb27-53" tabindex="-1"></a>    <span class="cf">return</span> df_copy</span>
+<span id="cb27-54"><a href="#cb27-54" tabindex="-1"></a>...</span>
+<span id="cb27-55"><a href="#cb27-55" tabindex="-1"></a>    </span></code></pre>
 </div>
 <div class="section level3">
 <h3 id="writing-good-tests">Writing good tests<a class="anchor" aria-label="anchor" href="#writing-good-tests"></a></h3>
@@ -1234,38 +1234,44 @@ <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
 <div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
 <div class="accordion-body">
 <p>We can add the following test functions to out test suite.</p>
-<div class="codewrapper sourceCode" id="cb30">
+<div class="codewrapper sourceCode" id="cb29">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb30-2"><a href="#cb30-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> (</span>
-<span id="cb30-3"><a href="#cb30-3" tabindex="-1"></a>    text_to_duration,</span>
-<span id="cb30-4"><a href="#cb30-4" tabindex="-1"></a>    calculate_crew_size</span>
-<span id="cb30-5"><a href="#cb30-5" tabindex="-1"></a>)</span>
-<span id="cb30-6"><a href="#cb30-6" tabindex="-1"></a></span>
-<span id="cb30-7"><a href="#cb30-7" tabindex="-1"></a>...</span>
-<span id="cb30-8"><a href="#cb30-8" tabindex="-1"></a></span>
-<span id="cb30-9"><a href="#cb30-9" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size():</span>
-<span id="cb30-10"><a href="#cb30-10" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb30-11"><a href="#cb30-11" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
-<span id="cb30-12"><a href="#cb30-12" tabindex="-1"></a><span class="co">    for typical crew values</span></span>
-<span id="cb30-13"><a href="#cb30-13" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb30-14"><a href="#cb30-14" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Valentina Tereshkova;"</span>)</span>
-<span id="cb30-15"><a href="#cb30-15" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">1</span></span>
-<span id="cb30-16"><a href="#cb30-16" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb30-17"><a href="#cb30-17" tabindex="-1"></a></span>
-<span id="cb30-18"><a href="#cb30-18" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Judith Resnik; Sally Ride;"</span>)</span>
-<span id="cb30-19"><a href="#cb30-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
-<span id="cb30-20"><a href="#cb30-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb30-21"><a href="#cb30-21" tabindex="-1"></a></span>
-<span id="cb30-22"><a href="#cb30-22" tabindex="-1"></a><span class="co"># Edge cases</span></span>
-<span id="cb30-23"><a href="#cb30-23" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size_edge_cases():</span>
-<span id="cb30-24"><a href="#cb30-24" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb30-25"><a href="#cb30-25" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
-<span id="cb30-26"><a href="#cb30-26" tabindex="-1"></a><span class="co">    for edge case where crew is an empty string</span></span>
-<span id="cb30-27"><a href="#cb30-27" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb30-28"><a href="#cb30-28" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">""</span>)</span>
-<span id="cb30-29"><a href="#cb30-29" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="kw">is</span> <span class="va">None</span></span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb29-2"><a href="#cb29-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> (</span>
+<span id="cb29-3"><a href="#cb29-3" tabindex="-1"></a>    text_to_duration,</span>
+<span id="cb29-4"><a href="#cb29-4" tabindex="-1"></a>    calculate_crew_size</span>
+<span id="cb29-5"><a href="#cb29-5" tabindex="-1"></a>)</span>
+<span id="cb29-6"><a href="#cb29-6" tabindex="-1"></a></span>
+<span id="cb29-7"><a href="#cb29-7" tabindex="-1"></a>...</span>
+<span id="cb29-8"><a href="#cb29-8" tabindex="-1"></a></span>
+<span id="cb29-9"><a href="#cb29-9" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size():</span>
+<span id="cb29-10"><a href="#cb29-10" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb29-11"><a href="#cb29-11" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
+<span id="cb29-12"><a href="#cb29-12" tabindex="-1"></a><span class="co">    for typical crew values</span></span>
+<span id="cb29-13"><a href="#cb29-13" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb29-14"><a href="#cb29-14" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Valentina Tereshkova;"</span>)</span>
+<span id="cb29-15"><a href="#cb29-15" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">1</span></span>
+<span id="cb29-16"><a href="#cb29-16" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb29-17"><a href="#cb29-17" tabindex="-1"></a></span>
+<span id="cb29-18"><a href="#cb29-18" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Judith Resnik; Sally Ride;"</span>)</span>
+<span id="cb29-19"><a href="#cb29-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
+<span id="cb29-20"><a href="#cb29-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb29-21"><a href="#cb29-21" tabindex="-1"></a></span>
+<span id="cb29-22"><a href="#cb29-22" tabindex="-1"></a><span class="co"># Edge cases</span></span>
+<span id="cb29-23"><a href="#cb29-23" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size_edge_cases():</span>
+<span id="cb29-24"><a href="#cb29-24" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb29-25"><a href="#cb29-25" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
+<span id="cb29-26"><a href="#cb29-26" tabindex="-1"></a><span class="co">    for edge case where crew is an empty string</span></span>
+<span id="cb29-27"><a href="#cb29-27" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb29-28"><a href="#cb29-28" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">""</span>)</span>
+<span id="cb29-29"><a href="#cb29-29" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="kw">is</span> <span class="va">None</span></span></code></pre>
+</div>
+<p>Let’s run out tests:</p>
+<div class="codewrapper sourceCode" id="cb30">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest</span></code></pre>
 </div>
 </div>
 </div>
@@ -1295,9 +1301,9 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <span id="cb31-11"><a href="#cb31-11" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
 <span id="cb31-12"><a href="#cb31-12" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span></code></pre>
 </div>
-<p>To avoid such repetitions in our test code, we can <strong>test
+<p>To avoid such repetitions in our test code, we use <strong>test
 parameterisation</strong>. This allows us to apply our test function to
-a list of input / expected output pairs without the need for repetition.
+a list of input/expected output pairs without the need for repetition.
 To parameterise the <code>test_calculate_crew_size</code> function, we
 can rewrite is as follows:</p>
 <div class="codewrapper sourceCode" id="cb32">
@@ -1595,7 +1601,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1617,8 +1623,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/08-code-correctness.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/08-code-correctness.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/09-code-documentation.html b/09-code-documentation.html
index b272439a..41ed596f 100644
--- a/09-code-documentation.html
+++ b/09-code-documentation.html
@@ -290,7 +290,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
       <div class="accordion-body">
         <ul><li><a href="#why-document-our-software">Why document our software?</a></li>
 <li><a href="#software-level-documentation">Software-level documentation</a></li>
-<li><a href="#just-enough-documentation">Just enough documentation</a></li>
+<li><a href="#project-level-documentation">Project-level documentation</a></li>
 <li><a href="#documentation-tools">Documentation tools</a></li>
 <li><a href="#documentation-guides">Documentation guides</a></li>
 <li><a href="#further-reading">Further reading</a></li>
@@ -303,7 +303,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -370,13 +370,13 @@ <h2 class="accordion-header" id="flush-headingTwelve">
           Previous: Code correctness
         </a>
         <a class="chapter-link float-end" href="10-open-collaboration.html" rel="next">
-          Next: Open collaboration...
+          Next: Open code &amp;...
           <i aria-hidden="true" class="small-arrow" data-feather="arrow-right"></i>
         </a>
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code documentation</h1>
-        <p>Last updated on 2024-09-26 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/09-code-documentation.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -441,8 +441,8 @@ <h3 class="callout-title">Activate your virtual environment</h3>
 <div class="codewrapper sourceCode" id="cb1">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="ex">$</span> source venv_spacewalks/bin/activate <span class="co"># Mac or Linux</span></span>
-<span id="cb1-2"><a href="#cb1-2" tabindex="-1"></a><span class="ex">$</span> source venv_spacewalks/Scripts/activate <span class="co"># Windows</span></span>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> source venv_spacewalks/bin/activate <span class="co"># Mac or Linux</span></span>
+<span id="cb1-2"><a href="#cb1-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> source venv_spacewalks/Scripts/activate <span class="co"># Windows</span></span>
 <span id="cb1-3"><a href="#cb1-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span></span></code></pre>
 </div>
 </div>
@@ -475,10 +475,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 </ul></section><section><h2 class="section-heading" id="software-level-documentation">Software-level documentation<a class="anchor" aria-label="anchor" href="#software-level-documentation"></a></h2>
 <hr class="half-width"><p>In previous episodes we encountered several different forms of
 in-code documentation aspects, including in-line comments and
-docstrings.</p>
-<p>These are an excellent way to improve the readability of our code,
-but by themselves are insufficient to ensure that our code is easy to
-use, understand and modify - this requires additional software-level
+docstrings. These are an excellent way to improve the readability of our
+code, but by themselves are insufficient to ensure that our code is easy
+to use, understand and modify - this requires additional software-level
 documentation.</p>
 <p>There are many different types of software-level documentation.</p>
 <div class="section level3">
@@ -493,14 +492,19 @@ <h3 id="technical-documentation">Technical documentation<a class="anchor" aria-l
 <li>Explanation - conceptual discussion of the code to help users
 understand implementation decisions</li>
 </ul></div>
+</section><section><h2 class="section-heading" id="project-level-documentation">Project-level documentation<a class="anchor" aria-label="anchor" href="#project-level-documentation"></a></h2>
+<hr class="half-width"><p>Project-level documentation includes various information and metadata
+about software that help to discover it, explain the legal terms of
+reusing it, describe its functionality on a high level and how to
+install, run and contribute to it.</p>
 <div class="section level3">
 <h3 id="repository-metadata-files">Repository metadata files<a class="anchor" aria-label="anchor" href="#repository-metadata-files"></a></h3>
-<p>In addition to software-level technical documentation, it is also
-common to see repository metadata files included in a code repository.
-Many of these files can be described as “social documentation” i.e. they
-indicate how users should “behave” in relation to our software project.
-Some common examples of repository metadata files and their role are
-tabulated below:</p>
+<p>A common way to to provide project-level documentation is to include
+various metadata files in the software repository together with code.
+Many of these files can be described as “social documentation”,
+i.e. they indicate how users should “behave” in relation to our software
+project. Some common examples of repository metadata files and their
+role are explained below:</p>
 <table class="table"><colgroup><col width="7%"><col width="92%"></colgroup><thead><tr class="header"><th>File</th>
 <th>Description</th>
 </tr></thead><tbody><tr class="odd"><td>README</td>
@@ -521,11 +525,20 @@ <h3 id="repository-metadata-files">Repository metadata files<a class="anchor" ar
 </tr><tr class="even"><td>AUTHORS</td>
 <td>Provides information on who authored the code (can also be included
 in CITATION)</td>
-</tr></tbody></table></div>
-</section><section><h2 class="section-heading" id="just-enough-documentation">Just enough documentation<a class="anchor" aria-label="anchor" href="#just-enough-documentation"></a></h2>
-<hr class="half-width"><p>For many small projects the following three pieces of documentation
-may be sufficient: README, LICENSE and CITATION.</p>
+</tr></tbody></table><div id="just-enough-documentation" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="just-enough-documentation" class="callout-inner">
+<h3 class="callout-title">Just enough documentation</h3>
+<div class="callout-content">
+<p>For many small projects the following three pieces of project-level
+documentation may be sufficient: README, LICENSE and CITATION.</p>
+</div>
+</div>
+</div>
 <p>Let’s look at each of these files in turn.</p>
+</div>
 <div class="section level3">
 <h3 id="readme-file">README file<a class="anchor" aria-label="anchor" href="#readme-file"></a></h3>
 <p>A README file acts as a “landing page” for your code repository on
@@ -619,23 +632,20 @@ <h4 id="optional">Optional<a class="anchor" aria-label="anchor" href="#optional"
 </div>
 </div>
 </div>
-<p>Let’s create a simple README for our repository.</p>
-<div class="codewrapper sourceCode" id="cb2">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="ex">$</span> cd ~/Desktop/Spacewalks</span>
-<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="ex">$</span> touch README.md</span></code></pre>
-</div>
-<p>Let’s start by adding a one-liner that explains the purpose of our
+<p>Let’s create a simple README for our repository - from VS Code or
+command line terminal create file <code>README.md</code> (in Markdown
+format) or <code>README.txt</code> (in plain text format).</p>
+<p>We can start by adding a one-liner that explains the purpose of our
 code and who it is for.</p>
 <pre class="code"><code># Spacewalks
 
 ## Overview
-Spacewalks is a python-based analysis tool for researchers to generate visualisations
+Spacewalks is a Python analysis tool for researchers to generate visualisations
 and statistical summaries of NASA's extravehicular activity datasets.</code></pre>
 <p>Now let’s add a list of Spacewalks’ key features:</p>
 <pre class="code"><code>## Features
 Key features of Spacewalks:
+
 - Generates a CSV table of summary statistics of extravehicular activity crew sizes
 - Generates a line plot to show the cumulative duration of space walks over time</code></pre>
 <p>Now let’s tell users about any pre-requisites required to run the
@@ -658,9 +668,10 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div id="spacewalks-readme" class="callout-inner">
 <h3 class="callout-title">Spacewalks README</h3>
 <div class="callout-content">
-<p>Extend the README for Spacewalks by adding a. Installation
-instructions b. A simple usage example</p>
-</div>
+<p>Extend the README for Spacewalks by adding:</p>
+<ol style="list-style-type: decimal"><li>Installation instructions</li>
+<li>A simple usage example</li>
+</ol></div>
 </div>
 </div>
 <div id="accordionSolution2" class="accordion challenge-accordion accordion-flush">
@@ -672,39 +683,40 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <div class="accordion-body">
 <p>Installation instructions:</p>
 <p>NB: In the solution below the back ticks of each code block have been
-escaped to avoid rendering issues.</p>
-<pre class="text"><code># Installation instructions
+escaped to avoid rendering issues (if you are copying and pasting the
+text, make sure you unescape them).</p>
+<pre class="text"><code>## Installation instructions
 
 + Clone the Spacewalks repository to your local machine using Git.
 If you don't have Git installed, you can download it from the official Git website.
 
-\`\`\`bash
+\`\`\`
 git clone https://github.com/your-repository-url/spacewalks.git
 cd spacewalks
 \`\`\`
 
 + Install the necessary dependencies:
-\`\`\`bash
-pip install pandas==2.2.2 matplotlib==3.8.4 numpy==2.0.0 pytest==7.4.2
+\`\`\`
+python3 -m pip install pandas==2.2.2 matplotlib==3.8.4 numpy==2.0.0 pytest==7.4.2
 \`\`\`
 
 + To ensure everything is working correctly, run the tests using pytest.
 
-\`\`\`bash
-python -m pytest
+\`\`\`
+python3 -m pytest
 \`\`\`</code></pre>
 <p>Usage instructions:</p>
-<pre class="text"><code># Usage Example
+<pre class="text"><code>## Usage Example
 
 To run an analysis using the eva_data_analysis.py script from the command line terminal,
 launch the script using Python as follows:
 
-\`\`\`python
+\`\`\`
 # Usage Examples
-python eva_data_analysis.py eva-data.json eva-data.csv
+python3 eva_data_analysis.py eva-data.json eva-data.csv
 \`\`\`
 
-The first argument is path to the Json data file.
+The first argument is path to the JSON data file.
 The second argument is the path the CSV output file.</code></pre>
 </div>
 </div>
@@ -810,146 +822,124 @@ <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 <h3 id="citation-file">CITATION file<a class="anchor" aria-label="anchor" href="#citation-file"></a></h3>
 <p>We can add a citation file to our repository to provide instructions
 on how and when to cite our code. A citation file can be a plain text
-(CITATION.txt) or a Markdown file (CITATION.md), but there are certain
-benefits to use a special file format called the Citation File Format
-(CFF) which provides a way to include richer metadata about software or
-datasets we want to cite, making it easy for both humans and machines to
-use this information.</p>
+(<code>CITATION.txt</code>) or a Markdown file
+(<code>CITATION.md</code>), but there are certain benefits to use a
+special file format called the Citation File Format (CFF) which provides
+a way to include richer metadata about software or datasets we want to
+cite, making it easy for both humans and machines to use this
+information.</p>
 <div class="section level4">
 <h4 id="why-use-cff">Why use CFF?<a class="anchor" aria-label="anchor" href="#why-use-cff"></a></h4>
 <p>For developers, using a CFF file can help to automate the process of
-publishing new releases on Zenodo via GitHub. GitHub also “understands”
-CFF, and will display citation information prominently on the landing
-page of a repository that contains citation info in CFF.</p>
+publishing new releases on <a href="https://zenodo.org/" class="external-link">Zenodo</a> via
+GitHub. GitHub also “understands” CFF, and will display citation
+information prominently on the landing page of a repository that
+contains citation info in CFF.</p>
 <p>For users, having a CFF file makes it easy to cite the software or
 dataset with formatted citation information available for copy-paste and
 direct import from GitHub into reference managers like Zotero.</p>
 </div>
 <div class="section level4">
-<h4 id="creating-a-cff-file">Creating a CFF file<a class="anchor" aria-label="anchor" href="#creating-a-cff-file"></a></h4>
+<h4 id="cff-file-format">CFF file format<a class="anchor" aria-label="anchor" href="#cff-file-format"></a></h4>
 <p>A CFF file is using the <a href="https://yaml.org/" class="external-link">YAML</a>
 key-value pair format. At a minimum a CFF file must contain the title of
 the software/data, the type of asset (software or data) and at least one
 author:</p>
-<div class="codewrapper sourceCode" id="cb8">
+<div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
-<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb8-10"><a href="#cb8-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
-<span id="cb8-11"><a href="#cb8-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
+<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
+<span id="cb7-3"><a href="#cb7-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb7-4"><a href="#cb7-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
+<span id="cb7-5"><a href="#cb7-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb7-6"><a href="#cb7-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb7-7"><a href="#cb7-7" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb7-8"><a href="#cb7-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb7-9"><a href="#cb7-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb7-10"><a href="#cb7-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
+<span id="cb7-11"><a href="#cb7-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span></code></pre>
 </div>
 <p>Additional and optional metadata includes an abstract, repository URL
 and more.</p>
 </div>
 <div class="section level4">
-<h4 id="steps-to-make-your-software-citable">Steps to make your software citable<a class="anchor" aria-label="anchor" href="#steps-to-make-your-software-citable"></a></h4>
-<p>We can create (and update) a CFF file for our software using an
-online application called <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a>.</p>
-<p>Let’s create a dummy citation file for a project called “Spacetravel”
-with Author “Max Hypothesis” by following these steps:</p>
-<ol style="list-style-type: decimal"><li>First, head to <code>cffinit</code> online at <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a>.</li>
-<li>Then, let’s work through the metadata input form to complete the
-minimum information needed to generate a CFF. We’ll also add the
-following abstract:
-<code>"Spacetravel - a simple python script to calculate time spent in Space by individual NASA astronauts"</code>
+<h4 id="creating-cff-file-and-making-your-software-citable">Creating CFF file and making your software citable<a class="anchor" aria-label="anchor" href="#creating-cff-file-and-making-your-software-citable"></a></h4>
+<p>We can create (and later update) a CFF file for our software using an
+online application called <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a> by following
+these steps:</p>
+<ol style="list-style-type: decimal"><li><p>Head to <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code>
+online tool</a>.</p></li>
+<li>
+<p>Then, work through the metadata input form to complete the
+minimum information needed to generate a CFF.</p>
+<p>We can use the following description as an “Abstract”: “A Python
+script to analyse NASA extravehicular activity data”</p>
+<p>Add the URL of the code repository as a “Related Resources”.</p>
+<p>Add at least two key words under the “Keywords” section.</p>
 </li>
-<li>At the end of the process, download the CFF file and inspect it. It
-should look like this:</li>
-</ol><div class="codewrapper sourceCode" id="cb9">
+<li><p>At the end of the process, download the CFF file and inspect it.
+It should look like this:</p></li>
+</ol><div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a></span>
-<span id="cb9-4"><a href="#cb9-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb9-5"><a href="#cb9-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacetravel</span></span>
-<span id="cb9-6"><a href="#cb9-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb9-7"><a href="#cb9-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb9-8"><a href="#cb9-8" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb9-9"><a href="#cb9-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb9-10"><a href="#cb9-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb9-11"><a href="#cb9-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Hypothesis</span></span>
-<span id="cb9-12"><a href="#cb9-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Max</span></span>
-<span id="cb9-13"><a href="#cb9-13" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb9-14"><a href="#cb9-14" tabindex="-1"></a>    A simple python script to calculate time spent in Space by individual NASA astronauts</span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
+<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
+<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a></span>
+<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
+<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb8-10"><a href="#cb8-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb8-11"><a href="#cb8-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
+<span id="cb8-12"><a href="#cb8-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
+<span id="cb8-13"><a href="#cb8-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
+<span id="cb8-14"><a href="#cb8-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
+<span id="cb8-15"><a href="#cb8-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
+<span id="cb8-16"><a href="#cb8-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
+<span id="cb8-17"><a href="#cb8-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-18"><a href="#cb8-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
+<span id="cb8-19"><a href="#cb8-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-20"><a href="#cb8-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
+<span id="cb8-21"><a href="#cb8-21" tabindex="-1"></a>  data</span>
+<span id="cb8-22"><a href="#cb8-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
+<span id="cb8-23"><a href="#cb8-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
+<span id="cb8-24"><a href="#cb8-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span></code></pre>
 </div>
+<p>CFF files can also be updated using the <code>cffinit</code> online
+tool by pasting the previous version of CFF file and working through the
+form to update various fields.</p>
 </div>
 <div class="section level4">
-<h4 id="updating-and-citing">Updating and citing<a class="anchor" aria-label="anchor" href="#updating-and-citing"></a></h4>
-<p>CFF files can also be updated using the <code>cffinit</code> online
-tool.</p>
+<h4 id="citing">Citing<a class="anchor" aria-label="anchor" href="#citing"></a></h4>
 <p>To cite our software (or dataset), once a CFF file has been pushed to
 our remote repository, GitHub’s “Cite this repository” button can be
 used to generate a citation in various formats (APA, BibTeX).</p>
-</div>
-<div class="section level4">
-<h4 id="tools">Tools<a class="anchor" aria-label="anchor" href="#tools"></a></h4>
-<p>Command line tools are also available for creating, validating, and
-converting CFF files. Further information is available from the <a href="https://book.the-turing-way.org/communication/citable/citable-cff.html" class="external-link">Turing
-Way’s guide to software citation</a>.</p>
-<div id="spacewalks-software-citation" class="callout challenge">
+<div id="section" class="callout">
 <div class="callout-square">
-<i class="callout-icon" data-feather="zap"></i>
+<i class="callout-icon" data-feather="bell"></i>
 </div>
-<div id="spacewalks-software-citation" class="callout-inner">
-<h3 class="callout-title">Spacewalks software citation</h3>
+<div id="section" class="callout-inner">
+<h3 class="callout-title"></h3>
 <div class="callout-content">
-<p>Write a software citation file for our Spacewalks software and add it
-to the root folder of our project.</p>
-<ul><li>Add the URL of the code repository as a “Related Resources”</li>
-<li>Add a one-line description of the code under the “Abstract”
-section</li>
-<li>Add at least two key words under the “Keywords” section</li>
-</ul></div>
+<p>Further information is available from the <a href="https://book.the-turing-way.org/communication/citable/citable-cff.html" class="external-link">Turing
+Way’s guide to software citation</a>.</p>
 </div>
 </div>
-<div id="accordionSolution4" class="accordion challenge-accordion accordion-flush">
-<div class="accordion-item">
-<button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution4" aria-expanded="false" aria-controls="collapseSolution4">
-  <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
-</button>
-<div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
-<div class="accordion-body">
-<p>Use <a href="https://citation-file-format.github.io/cff-initializer-javascript/#/version-specific" class="external-link">cffinit</a>,
-a web application to create your citation file using a series of online
-forms.</p>
-<div class="codewrapper sourceCode" id="cb10">
-<h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a></span>
-<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
-<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb10-8"><a href="#cb10-8" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb10-9"><a href="#cb10-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb10-10"><a href="#cb10-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb10-11"><a href="#cb10-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
-<span id="cb10-12"><a href="#cb10-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
-<span id="cb10-13"><a href="#cb10-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
-<span id="cb10-14"><a href="#cb10-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
-<span id="cb10-15"><a href="#cb10-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
-<span id="cb10-16"><a href="#cb10-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
-<span id="cb10-17"><a href="#cb10-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-18"><a href="#cb10-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
-<span id="cb10-19"><a href="#cb10-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-20"><a href="#cb10-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
-<span id="cb10-21"><a href="#cb10-21" tabindex="-1"></a>  data</span>
-<span id="cb10-22"><a href="#cb10-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
-<span id="cb10-23"><a href="#cb10-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
-<span id="cb10-24"><a href="#cb10-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span></code></pre>
 </div>
+<div id="spacewalks-software-citation" class="callout discussion">
+<div class="callout-square">
+<i class="callout-icon" data-feather="message-circle"></i>
 </div>
+<div id="spacewalks-software-citation" class="callout-inner">
+<h3 class="callout-title">Spacewalks software citation</h3>
+<div class="callout-content">
+<p>Add the citation file for our Spacewalks software to the root folder
+of our repository on GitHub. You can either do it directly on GitHub or
+creating the file locally and the committing and pushing to GitHub from
+the command line.</p>
 </div>
 </div>
 </div>
@@ -958,40 +948,33 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 </section><section><h2 class="section-heading" id="documentation-tools">Documentation tools<a class="anchor" aria-label="anchor" href="#documentation-tools"></a></h2>
 <hr class="half-width"><p>Once our project reaches a certain size or level of complexity we may
 want to add additional documentation such as a standalone tutorial or
-“Background” explaining our methodological choices.</p>
+“background” explaining our methodological choices.</p>
 <p>Once we move beyond using a README as our primary source of
 documentation, we need to consider how we will distribute our
-documentation to our users.</p>
-<p>Options include:</p>
-<ul><li>A <code>docs/</code> folder of Markdown files.</li>
-<li>Adding a Wiki to our repository.</li>
+documentation to our users. Options include:</p>
+<ul><li>A <code>docs/</code> folder of Markdown files</li>
+<li>Adding a Wiki to our repository</li>
 <li>Creating a set of web pages for our documentation using a static
-site generator for our documentation such as Sphinx or MkDocs</li>
+site generator for our documentation such as Sphinx or MkDocs.</li>
 </ul><p>Creating a static site is a popular solution as it has the key
 benefit being able to automatically generate a reference manual from any
 docstrings we have added to our code.</p>
 <div class="section level3">
 <h3 id="mkdocs">MkDocs<a class="anchor" aria-label="anchor" href="#mkdocs"></a></h3>
 <p>Let’s setup the static documentation site generator tool MkDocs.</p>
-<div class="codewrapper sourceCode" id="cb11">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install mkdocs</span>
-<span id="cb11-2"><a href="#cb11-2" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install <span class="st">"mkdocstrings[python]"</span></span>
-<span id="cb11-3"><a href="#cb11-3" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install mkdocs-material</span></code></pre>
-</div>
-<p>Let’s check that MkDocs has been setup correctly:</p>
-<div class="codewrapper sourceCode" id="cb12">
+<div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip list</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install mkdocs</span>
+<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install <span class="st">"mkdocstrings[python]"</span></span>
+<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install mkdocs-material</span></code></pre>
 </div>
-<p>Let’s creates a new MkDocs project in the current directory</p>
-<div class="codewrapper sourceCode" id="cb13">
+<p>Let’s creates a new MkDocs project in the current directory:</p>
+<div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="co"># In ~/Desktop/spacewalks</span></span>
-<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a><span class="ex">mkdocs</span> new .    </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="co"># In ~/Desktop/spacewalks</span></span>
+<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="ex">mkdocs</span> new .    </span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1001,72 +984,76 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 <p>This command creates a new MkDocs project in the current directory
 with a <code>docs</code> folder containing an <code>index.md</code> file
-and a <code>mkdocs.yml</code> configuration file.</p>
-<p>Now, let’s fill in the configuration file for our project.</p>
-<div class="codewrapper sourceCode" id="cb15">
+and a <code>mkdocs.yml</code> configuration file in the root of our
+project.</p>
+<p>Now, let’s fill in the <code>mkdocs.yml</code> configuration file for
+our project.</p>
+<div class="codewrapper sourceCode" id="cb12">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a></span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
-<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
-<span id="cb15-5"><a href="#cb15-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
-<span id="cb15-6"><a href="#cb15-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
-<span id="cb15-7"><a href="#cb15-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
-<span id="cb15-8"><a href="#cb15-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
-<span id="cb15-9"><a href="#cb15-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
-<span id="cb15-10"><a href="#cb15-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
-<span id="cb15-11"><a href="#cb15-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span></code></pre>
-</div>
-<p>Note font-false is for GDPR compliance.</p>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
+<span id="cb12-2"><a href="#cb12-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb12-3"><a href="#cb12-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
+<span id="cb12-4"><a href="#cb12-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
+<span id="cb12-5"><a href="#cb12-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb12-6"><a href="#cb12-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
+<span id="cb12-7"><a href="#cb12-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
+<span id="cb12-8"><a href="#cb12-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
+<span id="cb12-9"><a href="#cb12-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
+<span id="cb12-10"><a href="#cb12-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
+<span id="cb12-11"><a href="#cb12-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span></code></pre>
+</div>
+<p>Note <code>font: false</code> variable is for GDPR compliance;
+<code>use_directory_url: false</code> variable tells MKDocs tools how to
+handle URLs for documentation that is served as a website (we will cover
+this in a moment).</p>
 <p>Let’s add support for <code>mkdocstrings</code> - this will allow us
 to automatically our docstrings into our documentation using a simple
 tag.</p>
-<div class="codewrapper sourceCode" id="cb16">
+<div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
-<span id="cb16-2"><a href="#cb16-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
-<span id="cb16-3"><a href="#cb16-3" tabindex="-1"></a></span>
-<span id="cb16-4"><a href="#cb16-4" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
-<span id="cb16-5"><a href="#cb16-5" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
-<span id="cb16-6"><a href="#cb16-6" tabindex="-1"></a></span>
-<span id="cb16-7"><a href="#cb16-7" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
-<span id="cb16-8"><a href="#cb16-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
-<span id="cb16-9"><a href="#cb16-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
-<span id="cb16-10"><a href="#cb16-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
-<span id="cb16-11"><a href="#cb16-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
-<span id="cb16-12"><a href="#cb16-12" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span>
-<span id="cb16-13"><a href="#cb16-13" tabindex="-1"></a></span>
-<span id="cb16-14"><a href="#cb16-14" tabindex="-1"></a><span class="fu">plugins</span><span class="kw">:</span></span>
-<span id="cb16-15"><a href="#cb16-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> mkdocstrings</span></span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
+<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
+<span id="cb13-4"><a href="#cb13-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
+<span id="cb13-5"><a href="#cb13-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb13-6"><a href="#cb13-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
+<span id="cb13-7"><a href="#cb13-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
+<span id="cb13-8"><a href="#cb13-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
+<span id="cb13-9"><a href="#cb13-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
+<span id="cb13-10"><a href="#cb13-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
+<span id="cb13-11"><a href="#cb13-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span>
+<span id="cb13-12"><a href="#cb13-12" tabindex="-1"></a></span>
+<span id="cb13-13"><a href="#cb13-13" tabindex="-1"></a><span class="fu">plugins</span><span class="kw">:</span></span>
+<span id="cb13-14"><a href="#cb13-14" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> mkdocstrings</span></span></code></pre>
 </div>
 <p>Let’s populate our <code>docs/</code> folder to match our
 configuration file.</p>
-<div class="codewrapper sourceCode" id="cb17">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="fu">touch</span> docs/tutorials.md</span>
-<span id="cb17-2"><a href="#cb17-2" tabindex="-1"></a><span class="fu">touch</span> docs/how-to-guides.md</span>
-<span id="cb17-3"><a href="#cb17-3" tabindex="-1"></a><span class="fu">touch</span> docs/reference.md</span>
-<span id="cb17-4"><a href="#cb17-4" tabindex="-1"></a><span class="fu">touch</span> docs/explanation.md</span></code></pre>
-</div>
-<p>Let’s populate our reference file with some preamble to include
-before the reference manual that will be generated from the docstrings
-we created.</p>
-<div class="codewrapper sourceCode" id="cb18">
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/tutorials.md</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/how-to-guides.md</span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/reference.md</span>
+<span id="cb14-4"><a href="#cb14-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/explanation.md</span></code></pre>
+</div>
+<p>Let’s populate our reference file <code>reference.md</code> with some
+preamble to include before the reference manual that will be generated
+from the docstrings we created.</p>
+<div class="codewrapper sourceCode" id="cb15">
 <h3 class="code-label">MARKDOWN<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode markdown" tabindex="0"><code class="sourceCode markdown"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a>This file documents the key functions in the Spacewalks tool.</span>
-<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a>It is provided as a reference manual.</span>
-<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a></span>
-<span id="cb18-4"><a href="#cb18-4" tabindex="-1"></a>::: eva_data_analysis</span></code></pre>
+<pre class="sourceCode markdown" tabindex="0"><code class="sourceCode markdown"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a>This file documents the key functions in the Spacewalks tool.</span>
+<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a>It is provided as a reference manual.</span>
+<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a></span>
+<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a>::: eva_data_analysis</span></code></pre>
 </div>
 <p>Finally, let’s build our documentation.</p>
-<div class="codewrapper sourceCode" id="cb19">
+<div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="ex">mkdocs</span> build</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs build</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1079,25 +1066,43 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 INFO    -  Documentation built in 0.31 seconds</code></pre>
 </div>
 <p>Once the build step is completed, our documentation site is saved to
-a <code>site</code> folder in the root of our project folder.</p>
-<p>These files will be distributed with our code. We can either direct
-users to read these files locally on their own device using their
-browser, or we can choose to host our documentation as a website that
-our uses can navigate to.</p>
+a <code>site</code> folder in the root of our project folder. These
+files will be distributed with our code. We can either direct users to
+read these files locally on their own device using their browser, or we
+can choose to host our documentation as a website that our uses can
+navigate to.</p>
 <p>Note that we used the setting <code>use_directory_urls: false</code>
 in the <code>mkdocs.yml</code> file. This setting ensures that the
 documentation site is generated with URLs that are easy to navigate
 locally on a user’s device.</p>
-<p>Finally let us commit our documentation to the main branch of our git
-repository and push the changes to GitHub</p>
-<div class="codewrapper sourceCode" id="cb21">
+<div id="explore-your-documentation" class="callout discussion">
+<div class="callout-square">
+<i class="callout-icon" data-feather="message-circle"></i>
+</div>
+<div id="explore-your-documentation" class="callout-inner">
+<h3 class="callout-title">Explore your documentation</h3>
+<div class="callout-content">
+<p>Explore documentation in <code>site/</code> folder built with MkDocs
+for your project, starting from <code>index.html</code> file.</p>
+<p>For example, check <code>site/reference.html</code> to see how
+docstrings from your functions are provided here as a reference
+manual.</p>
+</div>
+</div>
+</div>
+<p>Finally, let us commit our documentation to the main branch of our
+git repository and push the changes to GitHub.</p>
+<div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="fu">git</span> add mkdocs.yml </span>
-<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="fu">git</span> add docs/</span>
-<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a><span class="fu">git</span> add site/</span>
-<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
-<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add mkdocs.yml </span>
+<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add docs/</span>
+<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add site/</span>
+<span id="cb18-4"><a href="#cb18-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
+<span id="cb18-5"><a href="#cb18-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip freeze <span class="op">&gt;</span> requirements.txt</span>
+<span id="cb18-6"><a href="#cb18-6" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add requirements.txt </span>
+<span id="cb18-7"><a href="#cb18-7" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Added mkdocs plugin"</span></span>
+<span id="cb18-8"><a href="#cb18-8" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 <div id="hosting-documentation" class="callout">
 <div class="callout-square">
@@ -1106,9 +1111,8 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div id="hosting-documentation" class="callout-inner">
 <h3 class="callout-title">Hosting documentation</h3>
 <div class="callout-content">
-<p>In the previous section, we saw how Mkdocs documentation can be
-distributed with our repository and viewed “offline” using a
-browser.</p>
+<p>We saw how MkDocs documentation can be distributed with our
+repository and viewed “offline” using a browser.</p>
 <p>We can also make our documentation available as a live website by
 deploying our documentation to a hosting service.</p>
 <div id="accordionSpoiler1" class="accordion spoiler-accordion accordion-flush">
@@ -1126,10 +1130,11 @@ <h3 id="github-pages">GitHub Pages<a class="anchor" aria-label="anchor" href="#g
 <p>There are two types of GitHub Pages: project pages and
 user/organization Pages. While similar, they have different deployment
 workflows, and we will only discuss project pages here. For information
-about deploying to user/organisational pages, see [MkDocs Deployment
-pages][mkdocs-deploy].</p>
-<p>Project Pages deploy site files to a branch within the project
-repository (default is gh-pages). To deploy our documentation:</p>
+about deploying to user/organisational pages, see <a href="https://www.mkdocs.org/user-guide/deploying-your-docs/" class="external-link">MkDocs
+Deployment pages</a>.</p>
+<p>Project Pages deploy site files to a branch (by default the
+<code>gh-pages</code> branch, but it can be any other branch) within the
+project repository. To deploy our documentation:</p>
 <blockquote>
 <p><strong>Warning!</strong> Before we proceed to the next step, we MUST
 ensure that there are no uncommitted changes or untracked files in our
@@ -1138,25 +1143,26 @@ <h3 id="github-pages">GitHub Pages<a class="anchor" aria-label="anchor" href="#g
 them in our documentation!</p>
 </blockquote>
 <ol style="list-style-type: decimal"><li>(If not done already), let us commit our documentation to the main
-branch of our git repository and push the changes to GitHub</li>
-</ol><div class="codewrapper sourceCode" id="cb22">
+branch of our git repository and push the changes to GitHub.</li>
+</ol><div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="fu">git</span> add mkdocs.yml </span>
-<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a><span class="fu">git</span> add docs/</span>
-<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a><span class="fu">git</span> add site/</span>
-<span id="cb22-4"><a href="#cb22-4" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
-<span id="cb22-5"><a href="#cb22-5" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add mkdocs.yml </span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add docs/</span>
+<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add site/</span>
+<span id="cb19-4"><a href="#cb19-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
+<span id="cb19-5"><a href="#cb19-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 <ol start="2" style="list-style-type: decimal"><li>Once we are on the main branch and all our changes are up to date,
-run the following command to deploy our documentation to GitHub.</li>
-</ol><div class="codewrapper sourceCode" id="cb23">
+run the following command from the command line termindal to deploy our
+documentation to GitHub.</li>
+</ol><div class="codewrapper sourceCode" id="cb20">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="co"># Important: </span></span>
-<span id="cb23-2"><a href="#cb23-2" tabindex="-1"></a><span class="co"># - This command will push the documentation to the gh-pages branch of your repository</span></span>
-<span id="cb23-3"><a href="#cb23-3" tabindex="-1"></a><span class="co"># - It will ALSO include uncommitted changes and untracked files (read the warning above!!) &lt;- VERY IMPORTANT!!</span></span>
-<span id="cb23-4"><a href="#cb23-4" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="co"># Important: </span></span>
+<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="co"># - This command will push the documentation to the gh-pages branch of your repository</span></span>
+<span id="cb20-3"><a href="#cb20-3" tabindex="-1"></a><span class="co"># - It will ALSO include uncommitted changes and untracked files (read the warning above!!) &lt;- VERY IMPORTANT!!</span></span>
+<span id="cb20-4"><a href="#cb20-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs gh-deploy</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1186,13 +1192,14 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 INFO    -  Your documentation should shortly be available at: https://kkh451.github.io/spacewalks/</code></pre>
 </div>
 <p>This command will build our documentation with MkDocs, then commit
-and push the files to the gh-pages branch using the GitHub ghp-import
-tool which is installed as a dependency of MkDocs.</p>
+and push the files to the <code>gh-pages</code> branch using the GitHub
+<code>ghp-import</code> tool which is installed as a dependency of
+MkDocs.</p>
 <p>For more options, use:</p>
-<div class="codewrapper sourceCode" id="cb25">
+<div class="codewrapper sourceCode" id="cb22">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy <span class="at">--help</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy <span class="at">--help</span></span></code></pre>
 </div>
 <p>Notice that the deploy command did not allow us to preview the site
 before it was pushed to GitHub; so, it is a good idea to check changes
@@ -1201,8 +1208,8 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="section level3">
 <h3 id="other-options">Other options<a class="anchor" aria-label="anchor" href="#other-options"></a></h3>
 <p>You can find out about other deployment options including free
-documentation hosting service ReadTheDocs on the [MkDocs deployment
-pages][mkdocs-deploy].</p>
+documentation hosting service ReadTheDocs on the <a href="https://www.mkdocs.org/user-guide/deploying-your-docs/" class="external-link">MkDocs
+deployment pages</a>.</p>
 </div>
 </div>
 </div>
@@ -1214,8 +1221,8 @@ <h3 id="other-options">Other options<a class="anchor" aria-label="anchor" href="
 </div>
 </section><section><h2 class="section-heading" id="documentation-guides">Documentation guides<a class="anchor" aria-label="anchor" href="#documentation-guides"></a></h2>
 <hr class="half-width"><p>Once we start to consider other forms of documentation beyond the
-README, we can also increase the re-usability of our code by ensuring
-that the content and style of our documentation matches its purpose.</p>
+README, we can also increase reusability of our code by ensuring that
+the content and style of our documentation matches its purpose.</p>
 <p>Documentation guides such as <a href="https://www.writethedocs.org/" class="external-link">Write the Docs</a>, <a href="https://www.thegooddocsproject.dev/" class="external-link">The Good Docs Project</a> and
 the <a href="https://diataxis.fr/" class="external-link">Diataxis framework</a> provide a
 range of resources including documentation templates to help to help us
@@ -1230,8 +1237,9 @@ <h3 class="callout-title">Spacewalks how-to guide</h3>
 <ol style="list-style-type: lower-alpha"><li><p>Review the Diataxis guidance page on writing a How-to guide.
 Identify three features of an effective how-to guide.</p></li>
 <li><p>Following the Diataxis guidelines, add a how-to guide to the
-<code>docs</code> folder that show users how to change the destination
-filename for the output dataset generated by Spacewalks.</p></li>
+<code>docs/how-to-guides.md</code> file in your documentation folder to
+show users how to change the destination filename for the output CSV
+dataset generated by the Spacewalks software.</p></li>
 </ol><div id="accordionSpoiler2" class="accordion spoiler-accordion accordion-flush">
 <div class="accordion-item">
 <button class="accordion-button spoiler-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSpoiler2" aria-expanded="false" aria-controls="collapseSpoiler2">
@@ -1244,21 +1252,30 @@ <h3 class="accordion-header" id="headingSpoiler2">  <div class="note-square"><i
 <li>avoid teaching or explanation</li>
 <li>use appropriate language e.g. conditional imperatives</li>
 <li>have an informative title</li>
-</ul><p>An example how-to guide:</p>
+</ul><p>An example how-to guide for our project to the file
+<code>docs/how-to-guides.md</code>:</p>
 <pre><code># How to change the file path of Spacewalk's output dataset
 
 This guide shows you how to set the file path for Spacewalk's output
 data set to a location of your choice.
 
-By default, the cleaned data set generated by Spacewalk is saved to the current
-working directory with file name `eva-data.csv`.
+By default, the cleaned data set in CSV format, generated by the Spacewalk software, is saved to the `results/`
+folder within the working directory with file name `eva-data.csv`.
 
 If you would like to modify the name or location of the output dataset, set the
 second command line argument to your chosen file path.
+For example, if you want to save the output data set to the subfolder `data/clean/` you can
+invoke the script as:
 
-`python eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv`
+`(venv_spacewalks) $ python3 eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv`
 
-The specified destination folder must exist before running spacewalks analysis script.</code></pre>
+The specified destination folder `data/clean/` must exist before running spacewalks analysis script.</code></pre>
+<p>Remember to rebuild your documentation:</p>
+<div class="codewrapper sourceCode" id="cb24">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs build</span></code></pre>
+</div>
 </div>
 </div>
 </div>
@@ -1291,8 +1308,9 @@ <h3 class="accordion-header" id="headingSpoiler3">  <div class="note-square"><i
 <div class="section level4">
 <h4 id="introduction">Introduction<a class="anchor" aria-label="anchor" href="#introduction"></a></h4>
 <p>In this tutorial, we will learn how to change the file path for the
-output dataset generated by Spacewalk. By the end of this tutorial, you
-will be able to specify a custom file path for the cleaned dataset.</p>
+output dataset generated by the Spacewalk software. By the end of this
+tutorial, you will be able to specify a custom file path for the cleaned
+dataset.</p>
 </div>
 <div class="section level4">
 <h4 id="prerequisites">Prerequisites<a class="anchor" aria-label="anchor" href="#prerequisites"></a></h4>
@@ -1303,34 +1321,35 @@ <h4 id="prerequisites">Prerequisites<a class="anchor" aria-label="anchor" href="
 </ul></div>
 <div class="section level4">
 <h4 id="prepare-the-destination-directory">Prepare the destination directory<a class="anchor" aria-label="anchor" href="#prepare-the-destination-directory"></a></h4>
-<p>First, let us decide where we want to save the cleaned dataset. and
+<p>First, let us decide where we want to save the cleaned dataset and
 make sure the directory exists.</p>
-<p>For this tutorial, we will use data/clean as the destination
-folder.</p>
-<p>Let’s create the directory if it does not exist:</p>
-<div class="codewrapper sourceCode" id="cb27">
+<p>For this tutorial, we will use <code>data/clean/</code> as the
+destination folder.</p>
+<p>Let’s create the directory if it does not exist - e.g. from the
+command line do:</p>
+<div class="codewrapper sourceCode" id="cb25">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="fu">mkdir</span> <span class="at">-p</span> data/clean</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir <span class="at">-p</span> data/clean</span></code></pre>
 </div>
 </div>
 <div class="section level4">
-<h4 id="run-the-analysis-script-with-custom-path">Run the analysis script with custom path<a class="anchor" aria-label="anchor" href="#run-the-analysis-script-with-custom-path"></a></h4>
+<h4 id="run-the-analysis-script-with-a-custom-path">Run the analysis script with a custom path<a class="anchor" aria-label="anchor" href="#run-the-analysis-script-with-a-custom-path"></a></h4>
 <p>Next, execute the Spacewalk script and specify the custom file path
 for the output dataset:</p>
-<div class="codewrapper sourceCode" id="cb28">
+<div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb28-1"><a href="#cb28-1" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py <span class="op">&lt;</span>input-file<span class="op">&gt;</span> <span class="op">&lt;</span>output-file<span class="op">&gt;</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py <span class="op">&lt;</span>input-file<span class="op">&gt;</span> <span class="op">&lt;</span>output-file<span class="op">&gt;</span></span></code></pre>
 </div>
-<p>Replace <input-file> with your input dataset (eva-data.json) and
-<output-file> with your desired output path
-(data/clean/eva-data-clean.csv).</output-file></input-file></p>
+<p>Replace <input-file> with your input dataset
+(<code>data/eva-data.json</code>) and <output-file> with your desired
+output path (<code>data/clean/eva-data-clean.csv</code>).</output-file></input-file></p>
 <p>Here is the complete command:</p>
-<div class="codewrapper sourceCode" id="cb29">
+<div class="codewrapper sourceCode" id="cb27">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py data/eva-data.json data/clean/eva-data-clean.csv</span></code></pre>
 </div>
 <p>Notice how the output to the command line clearly indicates that we
 are using a custom output file path.</p>
@@ -1338,44 +1357,45 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="output" tabindex="0"><code>Using custom input and output filenames
-Reading JSON file eva-data.json
+Reading JSON file data/eva-data.json
 Saving to CSV file data/clean/eva-data-clean.csv
 Adding crew size variable (crew_size) to dataset
 Saving to CSV file data/clean/eva-data-clean.csv
-Plotting cumulative spacewalk duration and saving to ./cumulative_eva_graph.png</code></pre>
+Plotting cumulative spacewalk duration and saving to results/cumulative_eva_graph.png</code></pre>
 </div>
-<p>After running the script, let us check the data/clean directory to
-ensure the cleaned dataset has been saved correctly.</p>
-<div class="codewrapper sourceCode" id="cb31">
+<p>After running the script, let us check the <code>data/clean</code>
+directory to ensure the cleaned dataset has been saved correctly.</p>
+<div class="codewrapper sourceCode" id="cb29">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" tabindex="-1"></a><span class="fu">ls</span> data/clean</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> ls data/clean</span></code></pre>
 </div>
-<p>You should see eva-data-clean.csv listed in the data/clean folder</p>
+<p>You should see <code>eva-data-clean.csv</code> file listed in the
+<code>data/clean</code> folder.</p>
 </div>
 <div class="section level4">
 <h4 id="exercise-custom-output-path">Exercise: custom output path<a class="anchor" aria-label="anchor" href="#exercise-custom-output-path"></a></h4>
-<ul><li>Create a new directory named output/data in your working
-directory.</li>
+<ul><li>Create a new directory named <code>output/data</code> in your
+working directory.</li>
 <li>Run the Spacewalk script to save the cleaned dataset in the newly
-created output/data directory with the filename
-cleaned-eva-data.csv.</li>
+created <code>output/data</code> directory with the filename
+<code>cleaned-eva-data.csv</code>.</li>
 <li>Verify that the dataset has been saved correctly.</li>
 </ul><div class="section level5">
 <h5 id="solution-1">Solution<a class="anchor" aria-label="anchor" href="#solution-1"></a></h5>
-<div class="codewrapper sourceCode" id="cb32">
+<div class="codewrapper sourceCode" id="cb30">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb32-1"><a href="#cb32-1" tabindex="-1"></a><span class="co"># Create the directory:</span></span>
-<span id="cb32-2"><a href="#cb32-2" tabindex="-1"></a><span class="fu">mkdir</span> <span class="at">-p</span> output/data</span>
-<span id="cb32-3"><a href="#cb32-3" tabindex="-1"></a></span>
-<span id="cb32-4"><a href="#cb32-4" tabindex="-1"></a><span class="co"># Run the script:</span></span>
-<span id="cb32-5"><a href="#cb32-5" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py eva-data.json output/data/cleaned-eva-data.csv</span>
-<span id="cb32-6"><a href="#cb32-6" tabindex="-1"></a></span>
-<span id="cb32-7"><a href="#cb32-7" tabindex="-1"></a><span class="co"># Verify the output:</span></span>
-<span id="cb32-8"><a href="#cb32-8" tabindex="-1"></a><span class="fu">ls</span> output/data</span>
-<span id="cb32-9"><a href="#cb32-9" tabindex="-1"></a></span>
-<span id="cb32-10"><a href="#cb32-10" tabindex="-1"></a><span class="co"># You should see cleaned-eva-data.csv listed</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="co"># Create the directory:</span></span>
+<span id="cb30-2"><a href="#cb30-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir <span class="at">-p</span> output/data</span>
+<span id="cb30-3"><a href="#cb30-3" tabindex="-1"></a></span>
+<span id="cb30-4"><a href="#cb30-4" tabindex="-1"></a><span class="co"># Run the script:</span></span>
+<span id="cb30-5"><a href="#cb30-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py data/eva-data.json output/data/cleaned-eva-data.csv</span>
+<span id="cb30-6"><a href="#cb30-6" tabindex="-1"></a></span>
+<span id="cb30-7"><a href="#cb30-7" tabindex="-1"></a><span class="co"># Verify the output:</span></span>
+<span id="cb30-8"><a href="#cb30-8" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> ls output/data</span>
+<span id="cb30-9"><a href="#cb30-9" tabindex="-1"></a></span>
+<span id="cb30-10"><a href="#cb30-10" tabindex="-1"></a><span class="co"># You should see cleaned-eva-data.csv listed</span></span></code></pre>
 </div>
 <p>Congratulations! You have successfully changed the file path for
 Spacewalks output dataset and completed an exercise to practice the
@@ -1430,24 +1450,14 @@ <h4 id="language">Language<a class="anchor" aria-label="anchor" href="#language"
 </div>
 </div>
 </div>
-<div id="commit-and-push-your-changes" class="callout">
-<div class="callout-square">
-<i class="callout-icon" data-feather="bell"></i>
-</div>
-<div id="commit-and-push-your-changes" class="callout-inner">
-<h3 class="callout-title">Commit and push your changes</h3>
-<div class="callout-content">
-<p>Do not forget to commit any uncommited changes you may have and then
+<p>Do not forget to commit any uncommitted changes you may have and then
 push your work to GitHub.</p>
-<div class="codewrapper sourceCode" id="cb33">
+<div class="codewrapper sourceCode" id="cb31">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb33-1"><a href="#cb33-1" tabindex="-1"></a><span class="fu">git</span> add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
-<span id="cb33-2"><a href="#cb33-2" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
-<span id="cb33-3"><a href="#cb33-3" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
-</div>
-</div>
-</div>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
+<span id="cb31-2"><a href="#cb31-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
+<span id="cb31-3"><a href="#cb31-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a></h2>
 <hr class="half-width"><p>We recommend the following resources for some additional reading on
@@ -1511,7 +1521,7 @@ <h3 class="callout-title">Key Points</h3>
           Previous: Code correctness
         </a>
         <a class="chapter-link float-end" href="10-open-collaboration.html" rel="next">
-          Next: Open collaboration...
+          Next: Open code &amp;...
           <i aria-hidden="true" class="small-arrow" data-feather="arrow-right"></i>
         </a>
       </div>
@@ -1535,7 +1545,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1557,8 +1567,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/09-code-documentation.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/09-code-documentation.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/10-open-collaboration.html b/10-open-collaboration.html
index 04de1b44..077ba5a5 100644
--- a/10-open-collaboration.html
+++ b/10-open-collaboration.html
@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- START: inst/pkgdown/templates/layout.html --><!-- Generated by pkgdown: do not edit by hand --><html lang="en" data-bs-theme="auto"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="utf-8"><title>Tools and practices for FAIR research software: Open collaboration on code</title><meta name="viewport" content="width=device-width, initial-scale=1"><script src="assets/themetoggle.js"></script><link rel="stylesheet" type="text/css" href="assets/styles.css"><script src="assets/scripts.js" type="text/javascript"></script><!-- mathjax --><script type="text/x-mathjax-config">
+<!-- START: inst/pkgdown/templates/layout.html --><!-- Generated by pkgdown: do not edit by hand --><html lang="en" data-bs-theme="auto"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="utf-8"><title>Tools and practices for FAIR research software: Open code &amp; collaboration</title><meta name="viewport" content="width=device-width, initial-scale=1"><script src="assets/themetoggle.js"></script><link rel="stylesheet" type="text/css" href="assets/styles.css"><script src="assets/scripts.js" type="text/javascript"></script><!-- mathjax --><script type="text/x-mathjax-config">
     MathJax.Hub.Config({
       config: ["MMLorHTML.js"],
       jax: ["input/TeX","input/MathML","output/HTML-CSS","output/NativeMML", "output/PreviewHTML"],
@@ -290,7 +290,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
       <button class="accordion-button" type="button" data-bs-toggle="collapse" data-bs-target="#flush-collapsecurrent" aria-expanded="true" aria-controls="flush-collapsecurrent">
         <span class="visually-hidden">Current Chapter</span>
         <span class="current-chapter">
-        10. Open collaboration on code
+        10. Open code &amp; collaboration
         </span>
       </button>
     </div><!--/div.accordion-header-->
@@ -372,8 +372,8 @@ <h2 class="accordion-header" id="flush-headingTwelve">
         </a>
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
-        <h1>Open collaboration on code</h1>
-        <p>Last updated on 2024-09-24 |
+        <h1>Open code &amp; collaboration</h1>
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/10-open-collaboration.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -417,9 +417,16 @@ <h3 class="card-title">Objectives</h3>
 </div>
 </div>
 </div>
-<p>In addition to adding a license and other metadata to our code
-(covered in previous episode) there are several other important steps to
-consider before sharing the code publicly.</p>
+<p>Sharing code openly promotes collaboration, transparency, and
+innovation by allowing others to review, use, and improve the code. It
+fosters knowledge exchange, accelerates scientific progress, and
+enhances the reproducibility of research. Additionally, open sharing
+encourages community contributions and can lead to better-maintained,
+more reliable software.</p>
+<p>Adding a <a href="licensing.html">license</a> and other metadata to
+our code (covered in the previous episode) are the first steps towards
+sharing the code publicly. There are several other important steps to
+consider which we will cover here.</p>
 <div id="activate-your-virtual-environment" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
@@ -439,85 +446,87 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 </div>
 </div>
 </div>
+
 <section><h2 class="section-heading" id="sharing-code-to-encourage-collaboration">Sharing code to encourage collaboration<a class="anchor" aria-label="anchor" href="#sharing-code-to-encourage-collaboration"></a></h2>
 <hr class="half-width"><div class="section level3">
 <h3 id="making-the-code-public">Making the code public<a class="anchor" aria-label="anchor" href="#making-the-code-public"></a></h3>
-<p>By default repositories created on Github are private and only their
-creator can see them. If we’re going to be adding an open source license
-to our repository we probably want to make sure people can actually
-access it too!</p>
-<p>Go to the Github webpage of your repository
-(<code>https://github.com/&lt;yourusername&gt;/&lt;yourrepsoitoryname&gt;</code>)
-and click on the Settings link near the top right corner. Then scroll
-down to the bottom of the page and the “Danger Zone” settings. Click on
-“Change Visibility” and you should see a message saying “Change to
-public”, if it says “Change to private” then the repository is already
-public. You’ll then be asked to confirm that you want to make the
-repository public and agree to the warning that the code will now be
-publicly visible. As a security measure you’ll then have to put in your
-Github password.</p>
+<p>By default repositories created on GitHub are private and only their
+creator can see them. Since we added an open source license to our
+repository we probably want to make sure people can actually access
+it.</p>
+<p>To make your repository public, if it is not already, go to your
+repository on GitHub and click on the <code>Settings</code> link near
+the top right corner. Then scroll down to the bottom of the page and the
+“Danger Zone” settings. Click on “Change Visibility” and you should see
+a message saying “Change to public”. If it says “Change to private” then
+the repository is already public. You will then be asked to confirm that
+you indeed want to make the repository public and agree to the warning
+that the code will now be publicly visible. As a security measure, you
+will then have to put in your GitHub password.</p>
 </div>
 <div class="section level3">
 <h3 id="transferring-to-an-organisation">Transferring to an organisation<a class="anchor" aria-label="anchor" href="#transferring-to-an-organisation"></a></h3>
-<p>Currently our repository is under the Github “namespace” of our
-individual user. This is ok for individual projects where we are the
-sole or at least main author, but for bigger and more complex projects
-it is common to use a Github organisation named after our project. If we
-are a member of an organisation and have the appropriate permissions
-then we can transfer a repository from our personal namespace to the
-organisation’s. This can be done with another option in the “Danger
-Zone” settings, the “Transfer ownership” button. Pressing this will then
-prompt us as to which organisation we want to transfer the repository
-to.</p>
+<p>Currently our repository is under the GitHub “namespace” of our
+individual user. This is OK for individual projects where we are the
+sole or at least the main code author, but for bigger and more complex
+projects it is common to use a GitHub organisation named after our
+project. If we are a member of an organisation and have the appropriate
+permissions then we can transfer a repository from our personal
+namespace to the organisation’s. This can be done with another option in
+the “Danger Zone” settings, the “Transfer ownership” button. Pressing
+this will then prompt us as to which organisation we want to transfer
+the repository to.</p>
 </div>
 <div class="section level3">
-<h3 id="archiving-to-zenodo-and-obtaining-a-doi">Archiving to Zenodo and obtaining a DOI<a class="anchor" aria-label="anchor" href="#archiving-to-zenodo-and-obtaining-a-doi"></a></h3>
-<p>Zenodo is a data archive run by CERN. Anybody can upload datasets up
-to 50GB to it and receive a Digital Object Identifier (DOI). Zenodo’s
-definition of a dataset is quite broad and can include code. This gives
-us a way to obtain a DOI for our code. We can archive our Github
-repository to Zenodo by doing the following:</p>
+<h3 id="archiving-code-to-zenodo-and-obtaining-a-doi">Archiving code to Zenodo and obtaining a DOI<a class="anchor" aria-label="anchor" href="#archiving-code-to-zenodo-and-obtaining-a-doi"></a></h3>
+<p><a href="https://zenodo.org/" class="external-link">Zenodo</a> is a data archive run by
+CERN. Anybody can upload datasets up to 50GB to it and receive a Digital
+Object Identifier (DOI). Zenodo’s definition of a dataset is quite broad
+and can include code - which gives us a way to obtain a DOI for our
+software. We can archive our GitHub repository to Zenodo by doing the
+following:</p>
 <ol style="list-style-type: decimal"><li>Go to the <a href="https://zenodo.org/login" class="external-link">Zenodo Login page</a>
-and choose to login with Github.</li>
-<li>Authorise Zenodo to connect to Github.</li>
-<li>Go to the <a href="https://zenodo.org/account/settings/github/" class="external-link">Github page</a> in
+and choose to login with GitHub.</li>
+<li>Authorise Zenodo to connect to GitHub.</li>
+<li>Go to the <a href="https://zenodo.org/account/settings/github/" class="external-link">GitHub page</a> in
 your Zenodo account. This can be found in the pull down menu with your
 user name in the top right corner of the screen.</li>
-<li>You’ll now have a list of all of your Github repositories. Next to
+<li>You’ll now have a list of all of your GitHub repositories. Next to
 each will be an “On” button. If you have created a new repository you
 might need to press the “Sync” button to update the list of repositories
 Zenodo knows about.</li>
 <li>Press the “On” button for the repository you want to archive. If
-this was successful you’ll be told to refresh the page.</li>
-<li>The repository should now appear in the list of Enabled repositories
-at the top of the screen. But it doesn’t yet have a DOI. To get one we
-have to make a release on Github. Click on the repository and then press
-the green button to create a release. This will take you to Github’s
-release page where you’ll be asked to give a title and description of
-the release. You will also have to create a tag, this is a way of having
-a friendly name for the version of some code in Git instead of using a
-long hash code. Often we’ll create a sequential version number for each
-release of the software and have the tag name match this, for example
-v1.0 or just 1.0.</li>
+this was successful you will be told to refresh the page.</li>
+<li>The repository should now appear in the list of “Enabled”
+repositories at the top of the screen, but it does not yet have a DOI.
+To get one we have to make a “release” on GitHub. Click on the
+repository and then press the green button to create a release. This
+will take you to GitHub’s release page where you will be asked to give a
+title and description of the release. You will also have to create a
+“tag” for your release - a way of having a friendly name for the version
+of some code in Git instead of using a long hash code. Often we will
+create a sequential version number for each release of the software and
+have the tag name match this, for example v1.0 or just 1.0.</li>
 <li>If we now refresh the Zenodo page for this repository we will see
 that it has been assigned a DOI.</li>
-</ol><p>The DOI doesn’t just link to Github, Zenodo will have taken a copy of
-our repository at the point where we tagged the release. This means that
-even if we delete it from Github or even if Github were ever to go away
-or remove it, they’ll still be a copy on Zenodo. Zenodo will allow
-people to download the entire repository as a single Zip file.</p>
+</ol><p>The DOI does not just link to GitHub, Zenodo will have taken a copy
+(a snapshot) of our repository at the point where we tagged the release.
+This means that even if we delete it from GitHub or even if GitHub were
+ever to go away or remove it, there will still be a copy on Zenodo.
+Zenodo will allow people to download the entire repository as a single
+<code>zip</code> file.</p>
 <p>Zenodo will have actually created two DOIs for you. One represents
 the latest version of the software and will always represent the latest
-if you make more releases. The other is specfic to the release you made
+if you make more releases. The other is specific to the release you made
 and will always point to that version. We can see both of these by
-clicking on the DOI link in the Zenodo page for the repository. One of
-the things which is displayed on this page is a badge image that you can
-copy the link for and add to the README file in your Git repository so
-that people can find the Zenodo version of the repository. If you click
-on the DOI image in the Details section of the Zenodo page then you will
-be shown instructions for obtaining a link to the DOI badge in various
-formats including Markdown. Here is the badge for this repository and
-the corresponding Markdown:</p>
+clicking on the DOI link in the Zenodo page for the repository.</p>
+<p>One of the things which is displayed on this page is a badge image
+that you can copy the link for and add to the README file in your GitHub
+repository so that people can find the Zenodo version of the repository.
+If you click on the DOI image in the Details section of the Zenodo page
+then you will be shown instructions for obtaining a link to the DOI
+badge in various formats including Markdown. Here is the badge for this
+repository and the corresponding Markdown:</p>
 <p><a href="https://doi.org/10.5281/zenodo.11869450" class="external-link"><img src="https://zenodo.org/badge/DOI/10.5281/zenodo.11869450.svg" alt="DOI" class="figure"></a></p>
 <pre class="text"><code>[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.11869450.svg)](https://doi.org/10.5281/zenodo.11869450)</code></pre>
 <div id="archive-your-repository-to-zenodo" class="callout discussion">
@@ -527,7 +536,11 @@ <h3 id="archiving-to-zenodo-and-obtaining-a-doi">Archiving to Zenodo and obtaini
 <div id="archive-your-repository-to-zenodo" class="callout-inner">
 <h3 class="callout-title">Archive your repository to Zenodo</h3>
 <div class="callout-content">
-<ul><li>Create an account on Zenodo that is linked to your Github
+<p>Note: for this exercise, you should use the <a href="https://sandbox.zenodo.org/" class="external-link">Sandbox Zenodo</a> (which is a
+version of Zenodo for testing and playing with before minting a real
+DOI) to avoid polluting the DOI space with test repositories we use for
+this course.</p>
+<ul><li>Create an account on Zenodo that is linked to your GitHub
 account.</li>
 <li>Use Zenodo to create a release for your repository and obtain a DOI
 for it.</li>
@@ -543,12 +556,12 @@ <h3 class="callout-title">Archive your repository to Zenodo</h3>
 <i class="callout-icon" data-feather="bell"></i>
 </div>
 <div id="problems-with-github-and-zenodo-integration" class="callout-inner">
-<h3 class="callout-title">Problems with Github and Zenodo integration</h3>
+<h3 class="callout-title">Problems with GitHub and Zenodo integration</h3>
 <div class="callout-content">
-<p>The integration between Github and Zenodo does not interact well with
+<p>The integration between GitHub and Zenodo does not interact well with
 some browser privacy features and extensions. Firefox can be
 particularly problematic with this and might open new tabs to login to
-Github and then give an error saying:
+GitHub and then give an error saying:
 <code>Your browser did something unexpected.  Please try again. If the error continues, try disabling all browser extensions.</code>
 If this happens try disabling the extra privacy features/extensions or
 using another browser such as Chrome.</p>
@@ -559,35 +572,49 @@ <h3 class="callout-title">Problems with Github and Zenodo integration</h3>
 <div class="section level3">
 <h3 id="adding-a-doi-and-orcid-to-the-citation-file">Adding a DOI and ORCID to the citation file<a class="anchor" aria-label="anchor" href="#adding-a-doi-and-orcid-to-the-citation-file"></a></h3>
 <p>Now that we have our DOI it is good practice to include this
-information in our citation file. In the previous part of this lesson we
-created a <code>CITATION.cff</code> file with information about how to
-cite our code. There are a few fields we can add which are related to
-the DOI, one of these is the <code>version</code> file which covers the
+information in our citation file. Earlier we created a
+<code>CITATION.cff</code> file with information about how to cite our
+code. There are a few fields we can add now which are related to the
+DOI; one of these is the <code>version</code> file which covers the
 version number of the software. We can add a DOI to the file in the
 <code>identifiers</code> section with a type of <code>doi</code> and
-<code>value</code> with the URL. Optionally we can also add a
+<code>value</code> of the Zenodo URL. Optionally we can also add a
 <code>date-released</code> field indicating the date we released this
-software. Here is an updated version of our CITATION.cff from the
-previous episode with a version number, DOI and release date added.</p>
+software. Here is an updated version of our <code>CITATION.cff</code>
+from the previous episode with a version number, DOI and release date
+added.</p>
 <div class="codewrapper sourceCode" id="cb3">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb3-1"><a href="#cb3-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
 <span id="cb3-2"><a href="#cb3-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb3-3"><a href="#cb3-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb3-4"><a href="#cb3-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
-<span id="cb3-5"><a href="#cb3-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb3-6"><a href="#cb3-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb3-7"><a href="#cb3-7" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb3-8"><a href="#cb3-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb3-9"><a href="#cb3-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb3-10"><a href="#cb3-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
-<span id="cb3-11"><a href="#cb3-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span>
-<span id="cb3-12"><a href="#cb3-12" tabindex="-1"></a><span class="fu">version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.0.1</span></span>
-<span id="cb3-13"><a href="#cb3-13" tabindex="-1"></a><span class="fu">identifiers</span><span class="kw">:</span></span>
-<span id="cb3-14"><a href="#cb3-14" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> doi</span></span>
-<span id="cb3-15"><a href="#cb3-15" tabindex="-1"></a><span class="at">    </span><span class="fu">value</span><span class="kw">:</span><span class="at"> 10.5281/zenodo.1234</span></span>
-<span id="cb3-16"><a href="#cb3-16" tabindex="-1"></a><span class="fu">date-released</span><span class="kw">:</span><span class="at"> 2024-06-01</span></span></code></pre>
+<span id="cb3-3"><a href="#cb3-3" tabindex="-1"></a></span>
+<span id="cb3-4"><a href="#cb3-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb3-5"><a href="#cb3-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
+<span id="cb3-6"><a href="#cb3-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-7"><a href="#cb3-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb3-8"><a href="#cb3-8" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb3-9"><a href="#cb3-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb3-10"><a href="#cb3-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb3-11"><a href="#cb3-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
+<span id="cb3-12"><a href="#cb3-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
+<span id="cb3-13"><a href="#cb3-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
+<span id="cb3-14"><a href="#cb3-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
+<span id="cb3-15"><a href="#cb3-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
+<span id="cb3-16"><a href="#cb3-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
+<span id="cb3-17"><a href="#cb3-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-18"><a href="#cb3-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
+<span id="cb3-19"><a href="#cb3-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-20"><a href="#cb3-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
+<span id="cb3-21"><a href="#cb3-21" tabindex="-1"></a>  data</span>
+<span id="cb3-22"><a href="#cb3-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
+<span id="cb3-23"><a href="#cb3-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
+<span id="cb3-24"><a href="#cb3-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span>
+<span id="cb3-25"><a href="#cb3-25" tabindex="-1"></a><span class="fu">version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.0.1</span></span>
+<span id="cb3-26"><a href="#cb3-26" tabindex="-1"></a><span class="fu">identifiers</span><span class="kw">:</span></span>
+<span id="cb3-27"><a href="#cb3-27" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> doi</span></span>
+<span id="cb3-28"><a href="#cb3-28" tabindex="-1"></a><span class="at">    </span><span class="fu">value</span><span class="kw">:</span><span class="at"> 10.5281/zenodo.1234</span></span>
+<span id="cb3-29"><a href="#cb3-29" tabindex="-1"></a><span class="fu">date-released</span><span class="kw">:</span><span class="at"> 2024-06-01</span></span></code></pre>
 </div>
 <div id="add-a-doi-to-your-citation-file" class="callout discussion">
 <div class="callout-square">
@@ -597,10 +624,11 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="callout-title">Add a DOI to your citation file</h3>
 <div class="callout-content">
 <p>Add the DOI you were allocated in the previous exercise to your
-CITATION.cff file and commit/push the updated version to your Github
-repository. You can remove the <code>commit</code> field from the
-CITATION.cff file as the DOI is a better way to point to given version
-of the code.</p>
+<code>CITATION.cff</code> file and then commit and push the updated
+version to your GitHub repository. If you used the <code>commit</code>
+field in your <code>CITATION.cff</code> file before to point to a given
+version of the code - you can now remove it as using the DOI field is
+better for this job.</p>
 </div>
 </div>
 </div>
@@ -629,24 +657,24 @@ <h3 class="callout-title">Going further with publishing code</h3>
 </div>
 </div>
 </section><section><h2 class="section-heading" id="working-with-collaborators">Working with collaborators<a class="anchor" aria-label="anchor" href="#working-with-collaborators"></a></h2>
-<hr class="half-width"><p>The strength of online collaboration tools such as Github doesn’t
-just lie in the ability to share code. They also allow us to track
+<hr class="half-width"><p>The strength of online collaboration platforms such as GitHub does
+not just lie in the ability to share code. They also allow us to track
 problems with that code, for multiple developers to work on it
 independently and bring their changes together and to review those
 changes before they are accepted.</p>
 <div class="section level3">
 <h3 id="tracking-issues-with-code">Tracking issues with code<a class="anchor" aria-label="anchor" href="#tracking-issues-with-code"></a></h3>
-<p>A key feature of Github (as opposed to Git itself) is the issue
+<p>A key feature of GitHub (as opposed to Git itself) is the issue
 tracker. This provides us with a place to keep track of any problems or
 bugs in the code and to discuss them with other developers. Sometimes
 advanced users will also use issue trackers of public projects to report
 problems they are having (and sometimes this is misused by users seeking
 help using documented features of the program).</p>
 <p>The code from the testing chapter earlier has a bug with an extra
-bracket in eva_data_analysis.py (and if you’ve fixed that a missing
+bracket in eva_data_analysis.py (and if you have fixed that a missing
 import of summarise_categorical in the test). Let’s go ahead and create
-a new issue in our Github repository to describe this problem. We can
-find the issue tracker on the “Issues” tab in the top left of the Github
+a new issue in our GitHub repository to describe this problem. We can
+find the issue tracker on the “Issues” tab in the top left of the GitHub
 page for the repository. Click on this and then click on the green “New
 Issue” button on the right hand side of the screen. We can then enter a
 title and description of our issue.</p>
@@ -669,7 +697,7 @@ <h3 class="callout-title">Write an issue to describe our bug</h3>
 <div class="callout-content">
 <p>Create a new issue in your repository’s issue tracker by doing the
 following:</p>
-<ul><li>Go to the Github webpage for your code</li>
+<ul><li>Go to the GitHub webpage for your code</li>
 <li>Click on the Issues tab</li>
 <li>Click on the “New issue” button</li>
 <li>Enter a title and description for the issue</li>
@@ -690,7 +718,7 @@ <h3 id="discussing-an-issue">Discussing an issue<a class="anchor" aria-label="an
 <div class="section level3">
 <h3 id="closing-an-issue">Closing an issue<a class="anchor" aria-label="anchor" href="#closing-an-issue"></a></h3>
 <p>Once an issue is solved then it can be closed. This can be done
-either by pressing the “Close” button in the Github web interface or by
+either by pressing the “Close” button in the GitHub web interface or by
 making a commit which includes the word “fixes”, “fixed”, “close”,
 “closed” or “closes” followed by a # symbol and the issue number.</p>
 </div>
@@ -701,36 +729,37 @@ <h3 id="working-in-parallel-with-git-branches">Working in parallel with Git bran
 with another. Branches are commonly used as a way for one developer to
 work on a new feature or a bug fix while other developers work on other
 features. When those new features or bug fixes are complete, the branch
-will be merged back with the main (sometimes called master) branch.</p>
+will be merged back with the <code>main</code> (sometimes called the
+<code>master</code>) branch.</p>
 <div class="section level4">
 <h4 id="creating-a-new-branch">Creating a new branch<a class="anchor" aria-label="anchor" href="#creating-a-new-branch"></a></h4>
-<p>New git branches are created with the <code>git branch</code>
+<p>New Git branches are created with the <code>git branch</code>
 command. This should be followed by the name of the branch to create. It
 is common practice when the bug we are fixing has a corresponding issue
 to name the branch after the issue number and name. For example, we
-might call the branch <code>01-extra-brakcet-bug</code> instead of
+might call the branch <code>01-extra-bracket-bug</code> instead of
 something less descriptive like <code>bugfix</code>.</p>
 <p>For example, the command:</p>
 <div class="codewrapper sourceCode" id="cb4">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="fu">git</span> branch 01-extra-brakcet-bug</span></code></pre>
-</div>
-<p>will create a new branch called <code>01-extra-brakcet-bug</code>. We
-can view the names of all the branches, by default there should be one
-branch called <code>main</code> or perhaps <code>master</code> and our
-new <code>01-extra-brakcet-bug</code> branch. by running
-<code>git branch</code> with no parameters. This will put <code>*</code>
-next to the currently active branch.</p>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git branch 01-extra-bracket-bug</span></code></pre>
+</div>
+<p>will create a new branch called <code>01-extra-bracket-bug</code>. We
+can view the names of all the branches by running
+<code>git branch</code> with no parameters. By default there should be
+one branch called <code>main</code> (formerly <code>master</code>) and
+our new <code>01-extra-bracket-bug</code> branch. The command will put
+<code>*</code> next to the currently active branch.</p>
 <div class="codewrapper sourceCode" id="cb5">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" tabindex="-1"></a><span class="fu">git</span> branch</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git branch</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="output" tabindex="0"><code>  01-extra-brakcet-bug
+<pre class="output" tabindex="0"><code>  01-extra-bracket-bug
 * main</code></pre>
 </div>
 <p>We can see that creating a new branch has not activated that branch.
@@ -740,27 +769,27 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="fu">git</span> switch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch 01-extra-bracket-bug</span></code></pre>
 </div>
 <p>To create a branch and change to it in a single command we can use
 <code>git switch</code> with the <code>-c</code> option (or
-<code>git checkout</code> with the <code>-b</code> option,
-<code>git switch</code> is only found in more recent versions of
-Git).</p>
+<code>git checkout</code> with the <code>-b</code> option). Note that
+<code>git switch</code> command is only available in more recent
+versions of Git.</p>
 <div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="fu">git</span> switch <span class="at">-c</span> 02-another-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch <span class="at">-c</span> 02-another-bug</span></code></pre>
 </div>
 </div>
 <div class="section level4">
 <h4 id="committing-to-a-branch">Committing to a branch<a class="anchor" aria-label="anchor" href="#committing-to-a-branch"></a></h4>
 <p>Once we have switched to a branch any further commits that are made
-will go to that branch. When we run a <code>git commit</code> command
-we’ll see the name of the branch we’re committing to in the output of
+will go to that branch. When we run a <code>git commit</code> command we
+will see the name of the branch we are committing to in the output of
 <code>git commit</code>. Let’s edit our code and fix the lack of default
 values bug that we entered into the issue tracker earlier on.</p>
-<p>Change your code from</p>
+<p>Change your code from:</p>
 <div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -776,7 +805,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb11">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"fixed bug"</span> eva_data_analysis.py</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"fixed bug"</span> eva_data_analysis.py</span></code></pre>
 </div>
 <p>In the output of <code>git commit -m</code> the first part of the
 output line will show the name of the branch we just made the commit
@@ -792,14 +821,14 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">git</span> switch main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch main</span></code></pre>
 </div>
-<p>And if we go back to the <code>01-extra-brakcet-bug</code> branch it
+<p>And if we go back to the <code>01-extra-bracket-bug</code> branch it
 will re-appear.</p>
 <div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="fu">git</span> switch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch 01-extra-bracket-bug</span></code></pre>
 </div>
 <p>If we want to push our changes to a remote such as GitHub we have to
 tell the <code>git push</code> command which branch to push to. If the
@@ -808,18 +837,18 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="codewrapper sourceCode" id="cb15">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">git</span> push origin 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin 01-extra-bracket-bug</span></code></pre>
 </div>
-<p>If we now refresh the Github webpage for this repository we should
+<p>If we now refresh the GitHub webpage for this repository we should
 see the bugfix branch has appeared in the list of branches.</p>
 <p>If we needed to pull changes from a branch on a remote (for example
-if we’ve made changes on another computer or via Github’s web based
+if we have made changes on another computer or via GitHub’s web based
 editor), then we can specify a branch on a <code>git pull</code>
 command.</p>
 <div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">git</span> pull origin 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">git</span> pull origin 01-extra-bracket-bug</span></code></pre>
 </div>
 </div>
 </div>
@@ -828,19 +857,19 @@ <h3 id="merging-branches">Merging branches<a class="anchor" aria-label="anchor"
 <p>When we have completed working on a branch (for example fixing a bug)
 then we can merge our branch back into the main one (or any other
 branch). This is done with the <code>git merge</code> command.</p>
-<p>This must be run on the <em>TARGET</em> branch of the merge, so we’ll
-have to use a <code>git switch</code> command to set this.</p>
+<p>This must be run on the <em>TARGET</em> branch of the merge, so we
+will have to use a <code>git switch</code> command to set this.</p>
 <div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="fu">git</span> switch main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch main</span></code></pre>
 </div>
-<p>Now we’re back on the main branch we can go ahead and merge the
+<p>Now we are back on the main branch we can go ahead and merge the
 changes from the bugfix branch:</p>
 <div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="fu">git</span> merge 01-extra-bracket-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git merge 01-extra-bracket-bug</span></code></pre>
 </div>
 </div>
 <div class="section level3">
@@ -848,25 +877,26 @@ <h3 id="pull-requests">Pull requests<a class="anchor" aria-label="anchor" href="
 <p>On larger projects we might need to have a code review process before
 changes are merged, especially before they are merged onto the main
 branch that might be what is being released as the public version of the
-software. Github has a process for this that it calls a “Pull Request”,
-other Git services such as GitLab have different names for this, GitLab
-calls them “Merge Requests”. Pull requests are where one developer
-requests that another merge code from a branch (or “pull” it from
-another copy of the repository). The person receiving the request then
-has the chance to review the code, write comments suggesting changes or
-even change the code themselves before merging it. It is also very
-common for automated checks of code to be run on a pull request to
-ensure the code is of good quality and is passing automated tests.</p>
+software. GitHub has a process for this that is called a <strong>pull
+request</strong>. Other Git services such as GitLab have different names
+for this; GitLab calls them <strong>merge requests</strong>. Pull
+requests are situations where one developer requests that another merges
+code from a branch (or “pull” it from another copy of the repository).
+The person receiving the request then has the chance to review the code,
+write comments suggesting changes or even change the code themselves
+before merging it. It is also very common for automated checks of code
+to be run on a pull request to ensure the code is of good quality and is
+passing automated tests.</p>
 <p>As a simple example of a pull request, we can now create a pull
 request for the changes we made on our <code>01-extra-bracket-bug</code>
-branch and pushed to Github earlier on. The Github webpage for our
-repository will now be saying something like “bugfix had recent pushes n
-minutes ago - Compare &amp; Pull request”. Click on this button and
-create a new pull request.</p>
+branch and pushed to GitHub earlier on. The GitHub webpage for our
+repository will now be saying something like “bugfix had recent pushes
+<code>n</code> minutes ago - Compare &amp; Pull request”. Click on this
+button and create a new pull request.</p>
 <p>Give the pull request a title and write a brief description of it,
-then click the green “Create pull request” button. Github will then
-check if we can merge this pull request without any problems. We’ll look
-at what to do when this isn’t possible later on.</p>
+then click the green “Create pull request” button. GitHub will then
+check if we can merge this pull request without any problems. We will
+look at what to do when this is not possible later on.</p>
 <p>There should be a green “Merge pull request” button, but if we click
 on the down arrow inside this button there are three options on how to
 handle this request:</p>
@@ -888,66 +918,57 @@ <h3 id="pull-requests">Pull requests<a class="anchor" aria-label="anchor" href="
 kind of merge they will prefer. For the purposes of this exercise we’ll
 stick with the default merge commit.</p>
 <p>Go ahead and click on “Merge pull request”, then “Confirm merge”. The
-changes will now be merged together. Github gives us the option to
-delete the branch we were working on, since it’s history is preserved in
-the main branch there isn’t any reason to keep it.</p>
+changes will now be merged together. GitHub gives us the option to
+delete the branch we were working on, since its history is preserved in
+the main branch there is no reason to keep it.</p>
 <div class="section level4">
 <h4 id="using-forks-instead-of-branches">Using forks instead of branches<a class="anchor" aria-label="anchor" href="#using-forks-instead-of-branches"></a></h4>
 <p>A fork is similar to a branch, but instead of it being part of the
 same repository it is a entirely new copy of the repository. Forks are
-commonly used by Github users who wish to work on a project that they’re
-not a member of. Typically forking will copy the repository to our own
-namespace (e.g. github.com/username/reponame instead of
+commonly used by Github users who wish to work on a project that they
+are not a member of. Typically forking will copy the repository to our
+own namespace (e.g. github.com/username/reponame instead of
 github.com/projectname/reponame)</p>
 <p>To create a fork on github use the “Fork” button to the right of the
 repository name. After we create our fork we can make some changes and
 these could even be on the main branch inside our forked repository.
-Github will track that a fork has been made displays a “Contribute”
+GitHub will track that a fork has been made displays a “Contribute”
 button to create a pull request back to the original repository. Using
 this we can request that the changes on our fork are incorporated by the
 upstream project.</p>
-<div id="pull-request-exercise" class="callout discussion">
+<div id="practice-pull-requests" class="callout discussion">
 <div class="callout-square">
 <i class="callout-icon" data-feather="message-circle"></i>
 </div>
-<div id="pull-request-exercise" class="callout-inner">
-<h3 class="callout-title">Pull request exercise</h3>
+<div id="practice-pull-requests" class="callout-inner">
+<h3 class="callout-title">Practice pull requests</h3>
 <div class="callout-content">
-<p>Q: Work in pairs for this exercise. Share the Github link of your
+<p>Q: Work in pairs for this exercise. Share the GitHub link of your
 repository with your partner. If you have set your repository to
-private, you’ll need to add them as a collaborator. Go to the settings
-page on your Github repository’s webpage, click on Collaborators from
+private, you will need to add them as a collaborator. Go to the settings
+page on your GitHub repository’s webpage, click on Collaborators from
 the left hand menu and then click the green “Add People” button and
-enter the Github username or email address of your partner. They will
-get an email and an alert within Github to accept your invitation to
+enter the GitHub username or email address of your partner. They will
+get an email and an alert within GitHub to accept your invitation to
 work on this repository, without doing this they won’t be able to access
 it.</p>
 <ul><li>Now make a fork of your partners repository.</li>
-<li>Edit the CITATION.cff file and add your name to it.</li>
+<li>Edit the <code>CITATION.cff</code> file and add your name to
+it.</li>
 <li>Commit these changes to your fork</li>
 <li>Create a pull request back to the original repository</li>
 <li>Your partner will now receive your pull request and can review</li>
 </ul></div>
 </div>
 </div>
-<div id="commit-and-push-your-changes" class="callout">
-<div class="callout-square">
-<i class="callout-icon" data-feather="bell"></i>
-</div>
-<div id="commit-and-push-your-changes" class="callout-inner">
-<h3 class="callout-title">Commit and push your changes</h3>
-<div class="callout-content">
-<p>Do not forget to commit any uncommited changes you may have and then
+<p>Do not forget to commit any uncommitted changes you may have and then
 push your work to GitHub.</p>
 <div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="fu">git</span> add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
-<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
-<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
-</div>
-</div>
-</div>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
+<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 </div>
 </div>
@@ -957,7 +978,7 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <ul><li>Licencing and citation episodes from the <a href="https://swcarpentry.github.io/git-novice" class="external-link">Software Carpentry’s Git
 Novice lesson</a>
 </li>
-<li>Carpentries Github Skill ups for <a href="https://carpentries-incubator.github.io/github-skill-up-instructors/" class="external-link">instructors</a>
+<li>Carpentries GitHub Skill ups for <a href="https://carpentries-incubator.github.io/github-skill-up-instructors/" class="external-link">instructors</a>
 and <a href="https://carpentries.github.io/github-skill-up-maintainers/" class="external-link">maintainers</a>
 </li>
 <li>
@@ -980,26 +1001,13 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="callout-inner">
 <h3 class="callout-title">Key Points</h3>
 <div class="callout-content">
-<ul><li>Open source applies Copyright licenses permitting others to reuse
-and adapt your code or data.</li>
-<li>Permissive licenses allow code to be used in other products
-providing the copyright statement is displayed.</li>
-<li>Copyleft licenses require the source code of any modifications to be
-released under a copyleft license.</li>
-<li>Creative commons licenses are suitable for non-code files such as
-documentation and images.</li>
-<li>Open source software can be sold, but you must supply the source
-code and the people you sell it to can give it away to somebody
-else.</li>
-<li>Add license file to your repository and add a license to each file
-in case it gets detached.</li>
-<li>Zenodo can be used to archive a Github repository and obtain a DOI
+<ul><li>Zenodo can be used to archive a GitHub repository and obtain a DOI
 for it.</li>
-<li>We can include a CITATION file to tell people how to cite our
-code.</li>
-<li>Github can track bugs or issues with a program.</li>
+<li>We include a CITATION file with our code to tell people how to cite
+it.</li>
+<li>GitHub can help us track bugs or issues with software.</li>
 <li>Git branches can be used to allow multiple developers to work on the
-same part of a program in parallel.</li>
+same part of code in parallel.</li>
 <li>The <code>git branch</code> command shows the list of branches and
 can create new branches.</li>
 <li>The <code>git switch</code> command changes which branch we are
@@ -1052,7 +1060,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1069,13 +1077,13 @@ <h3 class="callout-title">Key Points</h3>
   "dct:conformsTo": "https://bioschemas.org/profiles/TrainingMaterial/1.0-RELEASE",
   "description": "A Carpentries Lesson teaching foundational data and coding skills to researchers worldwide",
   "keywords": "software, FAIR, reproducibility, sustainability, open, research, lesson, The Carpentries",
-  "name": "Open collaboration on code",
+  "name": "Open code &amp;amp; collaboration",
   "creativeWorkStatus": "active",
   "url": "https://softwaresaved.github.io/fair-research-software/10-open-collaboration.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/10-open-collaboration.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-24",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/11-wrap-up.html b/11-wrap-up.html
index abba5586..496a95bf 100644
--- a/11-wrap-up.html
+++ b/11-wrap-up.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -363,7 +363,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       <div class="d-none d-sm-none d-md-block">
         <a class="chapter-link" href="10-open-collaboration.html" rel="prev">
           <i aria-hidden="true" class="small-arrow" data-feather="arrow-left"></i>
-          Previous: Open collaboration
+          Previous: Open code &amp;
         </a>
         <a class="chapter-link float-end" href="index.html" rel="next">
           Home
@@ -472,7 +472,7 @@ <h3 class="callout-title">Key Points</h3>
       <div class="d-none d-sm-none d-md-block">
         <a class="chapter-link" href="10-open-collaboration.html" rel="prev">
           <i aria-hidden="true" class="small-arrow" data-feather="arrow-left"></i>
-          Previous: Open collaboration
+          Previous: Open code &amp;
         </a>
         <a class="chapter-link float-end" href="index.html" rel="next">
           Home
@@ -499,7 +499,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -522,7 +522,7 @@ <h3 class="callout-title">Key Points</h3>
   "identifier": "https://softwaresaved.github.io/fair-research-software/11-wrap-up.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-09-17",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/404.html b/404.html
index f2b16251..e5551d70 100644
--- a/404.html
+++ b/404.html
@@ -310,7 +310,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="https://softwaresaved.github.io/fair-research-software/10-open-collaboration.html" class="external-link">10. Open collaboration on code</a>
+        <a href="https://softwaresaved.github.io/fair-research-software/10-open-collaboration.html" class="external-link">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -415,7 +415,7 @@ <h1>Page not found</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -437,8 +437,8 @@ <h1>Page not found</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/404.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/404.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/AUTHORS.html b/AUTHORS.html
index 3d27bde2..82ca285f 100644
--- a/AUTHORS.html
+++ b/AUTHORS.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -416,7 +416,7 @@ <h1>Authors</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -439,7 +439,7 @@ <h1>Authors</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/AUTHORS.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-03-04",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/CODE_OF_CONDUCT.html b/CODE_OF_CONDUCT.html
index 0837bb84..12270e52 100644
--- a/CODE_OF_CONDUCT.html
+++ b/CODE_OF_CONDUCT.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -421,7 +421,7 @@ <h1>Contributor Code of Conduct</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -444,7 +444,7 @@ <h1>Contributor Code of Conduct</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/CODE_OF_CONDUCT.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/LICENSE.html b/LICENSE.html
index 6257a71e..8ac8ade0 100644
--- a/LICENSE.html
+++ b/LICENSE.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -469,7 +469,7 @@ <h1>Licenses</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -492,7 +492,7 @@ <h1>Licenses</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/LICENSE.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/aio.html b/aio.html
index 530d1fea..30628665 100644
--- a/aio.html
+++ b/aio.html
@@ -354,7 +354,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -756,7 +756,7 @@ <h3 class="callout-title">What does open and reproducible research mean
  -->
 </section></section><section id="aio-02-fair-research-software"><p>Content from <a href="02-fair-research-software.html">FAIR research software</a></p>
 <hr>
-<p>Last updated on 2024-07-04 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/02-fair-research-software.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -845,48 +845,66 @@ <h3 class="callout-title">Motivation</h3>
 below is not exhaustive, but any of the practices that you employ in
 your research software workflow will bring you closer to the gold
 standard of a fully reproducible research.</p>
+<div class="section level3">
+<h3 id="findable">Findable<a class="anchor" aria-label="anchor" href="#findable"></a>
+</h3>
+<p>In order to make your software more findable, you should:</p>
 <ul>
-<li>Findable
-<ul>
-<li>Create a description of your software</li>
+<li>Create a description of your software to make it discoverable by
+search engines and other search tools</li>
 <li>Place your software in a public software repository (and ideally
-register it in a <a href="https://github.com/NLeSC/awesome-research-software-registries" class="external-link">software
-registry</a>)</li>
+register it in a [general-purpose or domain-specific software
+registry][software-registries])</li>
 <li>Use a unique and persistent identifier (DOI) for your software
-(e.g. by depositing your code on Zenodo), which is also useful for
+(e.g. by depositing your code on <a href="https://zenodo.org/" class="external-link">Zenodo</a>), which is also useful for
 citations - note that depositing your data/code on GitHub and similar
 software repositories may not be enough as they may change their open
-access model or disappear completely in the future</li>
+access model or disappear completely in the future, so archiving your
+code means it stands a better chance at being preserved</li>
 </ul>
-</li>
-<li>Accessible
+</div>
+<div class="section level3">
+<h3 id="accessible">Accessible<a class="anchor" aria-label="anchor" href="#accessible"></a>
+</h3>
+<p>In order to make your software more accessible, you should:</p>
 <ul>
 <li>Make sure people can freely, legally and easily get a copy your
 software</li>
-<li>Use coding conventions and comments to make your code readable and
-understandable by people (once they get a copy of it)</li>
+<li>Use code style conventions and code structure patterns, use comments
+and create documentation to make your code comprehensible by people
+(once they get a copy of it) - i.e. make your code accessible in the
+<em>intelligible</em> sense</li>
 </ul>
-</li>
-<li>Interoperable
+</div>
+<div class="section level3">
+<h3 id="interoperable">Interoperable<a class="anchor" aria-label="anchor" href="#interoperable"></a>
+</h3>
+<p>In order to make your software more interoperable, you should:</p>
 <ul>
-<li>Explain the functionality of your software</li>
+<li>Explain the functionality of your software, so others can understand
+how other tools can interoperate with it</li>
 <li>Use standard formats for inputs and outputs</li>
 <li>Communicate with other software via standard protocols and APIs</li>
 </ul>
-</li>
-<li>Reusable
+</div>
+<div class="section level3">
+<h3 id="reusable">Reusable<a class="anchor" aria-label="anchor" href="#reusable"></a>
+</h3>
+<p>In order to make your software more reusable, you should:</p>
 <ul>
 <li>Document your software (including its functionality, and how to
-install and run it)</li>
-<li>Follow best practices for software development (including coding
-conventions, code readability and verifying its correctness)</li>
+install and run it) to make it more understandable by others who may
+wish to reuse or extend it</li>
+<li>Follow best practices for software development (including code
+conventions, structure, readability and correctness)</li>
 <li>Test your software and make sure it works on different
-platforms/operating systems</li>
+platforms/operating systems to make it more reusable</li>
 <li>Give a licence to your software clearly stating how it can be
 reused</li>
-<li>State how to cite your software</li>
-</ul>
-</li>
+<li>State how to cite your software, so people can give you credit when
+they reuse it</li>
+<li>Include a contributor policy so that others can contribute to your
+code and credit for contributions is provided</li>
 </ul>
 <div id="fair-is-a-process-not-a-perfect-metric" class="callout">
 <div class="callout-square">
@@ -895,7 +913,7 @@ <h3 class="callout-title">Motivation</h3>
 <div id="fair-is-a-process-not-a-perfect-metric" class="callout-inner">
 <h3 class="callout-title">FAIR is a process, not a perfect metric</h3>
 <div class="callout-content">
-<p>FAIR is not a binary metric - there is no such thing as “FAIR or not
+<p>FAIR is not a binary metric - there is no such thing as “FAIR or”not
 FAIR”.</p>
 <p>FAIR is not a perfect metric, nor does it provide a full and
 exhaustive software quality checklist. Software may be FAIR but still
@@ -940,15 +958,17 @@ <h3 class="callout-title">Challenge</h3>
 </div>
 </div>
 </div>
+</div>
 </section><section><h2 class="section-heading" id="software-and-data-used-in-this-course">Software and data used in this course<a class="anchor" aria-label="anchor" href="#software-and-data-used-in-this-course"></a>
 </h2>
 <hr class="half-width">
 <p>We are going to follow a fairly typical experience of a new PhD or
 postdoc joining a research group. They were emailed some data and
 analysis code bundled in a <code>.zip</code> archive and written by
-another group member who works on similar things. They need to be able
-to install and run this code on their machine, check they understand it
-and then adapt it to their own project.</p>
+another group member who worked on similar things but has since left the
+group. They need to be able to install and run this code on their
+machine, check they can understand it and then adapt it to their own
+project.</p>
 <p>As part of the <a href="./index.html#astronaut-data-and-analysis-code">setup for this
 course</a>, you should have downloaded a <code>.zip</code> archive
 containing the software project the new research team member was given.
@@ -983,10 +1003,11 @@ <h3 class="callout-title">Challenge</h3>
 <div class="callout-inner">
 <h3 class="callout-title">Discussion</h3>
 <div class="callout-content">
-<p>Compare this data and code to the software you chose earlier. Do you
-think it is Findable, Accessible, Interoperable and Reusable? Give it a
-score from 1 to 5 in each category, as in the previous exercise, and
-then we will discuss it together.</p>
+<p>Look at our code in VS Code and compare this data and code to the
+software you chose earlier (or assess it on its own). Do you think it is
+Findable, Accessible, Interoperable and Reusable? Give it a score from 1
+to 5 in each category, as in the previous exercise, and then we will
+discuss it together.</p>
 </div>
 </div>
 </div>
@@ -1160,7 +1181,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-03-tools"><p>Content from <a href="03-tools.html">Tools and practices for FAIR research software development</a></p>
 <hr>
-<p>Last updated on 2024-09-24 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/03-tools.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -1199,169 +1220,146 @@ <h3 class="card-title">Objectives</h3>
 <p>In this course we will introduce you to a group of tools and
 practices that are commonly used in research to help you develop
 software in a FAIR way. You should already have these tools installed on
-your machine following the setup instructions. Here we will give an
-overview of the tools, how they help you achieve the aims of FAIR
-research software and how they work together. In later episodes we will
-describe some of these tools in more detail.</p>
-<section><h2 class="section-heading" id="development-environment">Development environment<a class="anchor" aria-label="anchor" href="#development-environment"></a>
-</h2>
-<hr class="half-width">
-<p>One of the first choices we make when writing code is what tool to
-use to do the writing. You can use a simple text editor such as Notepad,
-a terminal based editor with syntax highlighting such as Vim or Emacs,
-or one of many Integrated Development Environments (IDEs) which give you
-the tools to write, run and debug your code and inspect the output all
-in one place. Note that you should not use word processing software such
-as Microsoft Word or Apple Pages to write code - these tools are
-designed to create nicely formatted text for humans to read, so they may
-add or change formatting, or insert invisible characters that the
-programming language cannot interpret. Try opening a Word document in
-Notepad to see an example.</p>
-<p>This is mostly a personal choice as an experienced user of any of
-these tools can write good, FAIR software efficiently, but IDEs are
-popular because they are designed specifically for writing and running
-code. There are some language specific IDEs such as PyCharm, and some
-that can work with many languages like VS Code (Visual Studio Code).
-IDEs also have add-ons that provide extra functionality, such as
-checking your code as you type (similar to a spell-checker in Word),
-highlighting when you are not following best practice, or even
-automatically generating bits of code for you.</p>
-
-<p>In this course we will use VS Code IDE, as it is free, available on
-Windows, Mac and Linux operating systems, and can be used with many
-programming languages. It is a single tool in which we can:</p>
-<ul>
-<li>view our file system</li>
-<li>open many kinds of files</li>
-<li>edit, compile, run and debug code</li>
-<li>open a terminal to run command line tools (including version control
-tool Git) or view code outputs</li>
-</ul>
-<p>Use VS Code to open the Python script and the data file from our
-project.</p>
-</section><section><h2 class="section-heading" id="command-line-toolshell">Command line tool/shell<a class="anchor" aria-label="anchor" href="#command-line-toolshell"></a>
-</h2>
-<hr class="half-width">
-<p>In VS Code and similar IDEs you can often run the code by clicking a
-button or pressing some keyboard shortcut. If you gave your code to a
-colleague or collaborator they might use the same IDE or something
-different, so you cannot guarantee that they will have the same buttons
-and shortcuts as you.</p>
-<p>In the previous episode we mentioned that interoperable software
-should use standard protocols so that it can integrate with other tools.
-One of these standard protocols/tools is using the inputs and outputs
-via the command line terminal or shell. Command line terminal provides
-one of the oldest ways of interacting with operating system so many
-programs will have command line interfaces. Command line terminals, such
-as Bash and Zsh, have their own language syntax that allow you to write
-scripts and/or group and chain commands together to build up complex
-workflows using several programs in different steps. They also use less
-resources than a graphical user interface tool like an IDE, so are
-commonly used on high-performance computers and other shared systems
-where time, memory and processing power are expensive or in high
-demand.</p>
-<p>In this course we will use the Bash shell, which is one of the most
-common and comes already installed on Mac and Linux operating systems.
-You can create a command line interface to your program which will allow
-it to be run on any system that has a Bash shell, and allow users to
-change things like input and output files or choose different settings
-or parameters without editing your code. With a command line interface,
-your code can be built into automated workflows so that the whole
-process from data gathering to analysis to saving publication-quality
-results can be written in one Bash script and saved and reused.</p>
-</section><section><h2 class="section-heading" id="version-control">Version control<a class="anchor" aria-label="anchor" href="#version-control"></a>
-</h2>
-<hr class="half-width">
-<p>Version control means knowing what changes were made to your code and
-when. Many people who have worked on large documents such as essays
-start doing this by saving files called <code>essay_draft</code>,
-<code>essay_version1.doc</code>, <code>essay_version2.doc</code>, and so
-on. This can work on a small scale but most people find it quickly gets
-confusing which version a certain change was made, or which version is
-the one that you got feedback from a supervisor on. Using a version
-control system helps you keep track of changes, including when you might
-be working on shared code being edited by more than one person at a
-time.</p>
-<p>It also lets you assign version numbers or tags to particular
-versions so you can then use those to refer back to them later. For
-example, you can run your code and output some results and add a comment
-to your output that those results were produced by version 2.4 of your
-code, so if you try to run the same thing later and find it is
-different, you can check if it is a change in the code due to using a
-newer version, or a change in the data, or something else.</p>
-<p>We will be using the Git version control system, which can be used
-through the command line terminal, in a browser or in a desktop
-application.</p>
-</section><section><h2 class="section-heading" id="code-structure-and-style-guidelines">Code structure and style guidelines<a class="anchor" aria-label="anchor" href="#code-structure-and-style-guidelines"></a>
-</h2>
-<hr class="half-width">
-<p>TODO</p>
-</section><section><h2 class="section-heading" id="code-correctness">Code correctness<a class="anchor" aria-label="anchor" href="#code-correctness"></a>
-</h2>
-<hr class="half-width">
+your machine following the <a href="./index.html#astronaut-data-and-analysis-code">setup
+instructions</a>. Here we will give an overview of the tools, how they
+help you achieve the aims of FAIR research software and how they work
+together. In later episodes we will describe some of these tools in more
+detail.</p>
+<div class="section level3">
+<h3 id="development-environments">Development environments<a class="anchor" aria-label="anchor" href="#development-environments"></a>
+</h3>
+<p>Virtual and integrated development environments (IDEs), such as VS
+Code or PyCharm, help with running, testing, and debugging code. Virtual
+environments further enable us to share our working environments with
+others, making it easier to access, reuse and extend our code. IDEs
+often provide integrations with other tools, e.g. version control and
+command line terminals, enabling you to do many tasks from a single
+environment, saving time in switching between different tools.</p>
+</div>
+<div class="section level3">
+<h3 id="command-line-terminals">Command line terminals<a class="anchor" aria-label="anchor" href="#command-line-terminals"></a>
+</h3>
+<p>Command line terminals (e.g. Bash, GitBash) enable us to run and test
+our code without graphical user interfaces (GUI) afforded to us by IDEs
+- this is sometimes needed for accessing and running our code remotely
+on servers and high-performance systems without a GUI provision, where
+time, memory and processing power are expensive or in high demand.</p>
+<p>Version control systems are typically provided as command line tools,
+making them often only accessible from command line terminals to enter
+commands and access remote version control servers to backing up and
+sharing our work.</p>
+<p>Finally, command line tools use standard protocols for passing
+parameters, inputs and outputs. This makes it easier to integrate ours
+with other command line tools, allowing us to chain them and build up
+complex and reproducible workflows and analysis pipelines using several
+programs in different steps. If we write our software in a way which
+provides such an interoperable command line interface - we will be able
+to integrate it with other command line tools to automate and speed up
+our work.</p>
+</div>
+<div class="section level3">
+<h3 id="standard-inputoutput-formats-and-communication-protocols">Standard input/output formats and communication protocols<a class="anchor" aria-label="anchor" href="#standard-inputoutput-formats-and-communication-protocols"></a>
+</h3>
+<p>Using standard data exchange, input and output formats and
+communication protocols helps create interoperable software that can
+more readily integrate with other tools into more complex pipelines -
+increasing its interoperability and reusability.</p>
+</div>
+<div class="section level3">
+<h3 id="version-control-tools">Version control tools<a class="anchor" aria-label="anchor" href="#version-control-tools"></a>
+</h3>
+<p>Version control means knowing what changes were made to your code,
+when and by whom - promoting code ownership, responsibility and credit.
+When combined with software sharing and collaborative platforms such as
+GitHub or GitLab, it facilitates code publication, sharing and
+findability, teamwork and discussions about software and design
+decisions, provides backup facilities for your code and speeds up
+collaboration on shared code by allowing edits by more than one person
+at a time.</p>
+</div>
+<div class="section level3">
+<h3 id="code-style-and-structure-conventions">Code style and structure conventions<a class="anchor" aria-label="anchor" href="#code-style-and-structure-conventions"></a>
+</h3>
+<p>Following code style conventions for your programming language and
+standard code structure patterns that are agreed upon by the community
+and other programmers are important practices to ensure that others find
+it easy to read your code, reuse or extend it in their own examples and
+applications.</p>
+</div>
+<div class="section level3">
+<h3 id="code-testing">Code testing<a class="anchor" aria-label="anchor" href="#code-testing"></a>
+</h3>
 <p>Testing ensures that your code is correct and does what it is set out
 to do. When you write code you often feel very confident that it is
 perfect, but when writing bigger codes or code that is meant to do
 complex operations it is very hard to consider all possible edge cases
 or notice every single typing mistake. Testing also gives other people
 confidence in your code as they can see an example of how it is meant to
-run and be assured that it does work correctly on their machine.</p>
-<p>We will show different ways to test your code for different purposes.
-You need to think about what it is that is important to you and any
-future users or collaborators to decide what kind of testing is most
-useful for you.</p>
-</section><section><h2 class="section-heading" id="documentation">Documentation<a class="anchor" aria-label="anchor" href="#documentation"></a>
-</h2>
-<hr class="half-width">
-<p>Documentation comes in many forms - from the names of variables and
-functions in your code, additional comments that explain some lines, up
-to a whole website full of documentation with function definitions,
-usage examples, tutorials and guides. You many not need as much
-documentation as a large commercial software product, but making your
-code reusable relies on other people being able to understand what your
-code does and how to use it.</p>
-</section><section><h2 class="section-heading" id="licences-and-citation">Licences and citation<a class="anchor" aria-label="anchor" href="#licences-and-citation"></a>
-</h2>
-<hr class="half-width">
-<p>A licence states what people can legally do with your code, and what
-restrictions you have placed on it. Whenever you want to use someone
-else’s code you should check what license they have and make sure your
-use is legal. You may be restricted by your institution, your grant
-funding, or by other tools you use that require certain licenses for you
-to be compatible with them.</p>
-<p>Having a citation instructions is not a legal requirement but if you
-want to get academic credit for your work, you can make other people’s
-life much easier by telling them how you would like to be credited.
-Similarly, follow citation instructions ensures that when you use
-others’ code in your research they will be credited accordingly.</p>
-<p>Both licensing law and citation procedures can vary depending on your
-country and institution, so remember to check with a local team where
-you are. Your local research IT support or library teams would be a good
-place to start.</p>
-</section><section><h2 class="section-heading" id="code-repositories-and-registries">Code repositories and registries<a class="anchor" aria-label="anchor" href="#code-repositories-and-registries"></a>
-</h2>
-<hr class="half-width">
+run and be assured that it does work correctly on their machine -
+helping with code understanding and reusability.</p>
+</div>
+<div class="section level3">
+<h3 id="software--and-project--level-documentation">Software- and project- level documentation<a class="anchor" aria-label="anchor" href="#software--and-project--level-documentation"></a>
+</h3>
+<p>Documentation comes in many forms - from <strong>software-level
+documentation</strong> including docstrings describing functions and
+classes and in-line comments that explain lines of your code, to
+<strong>project-level documentation</strong> and
+<strong>metadata</strong> (including README, LICENCE, CITATION,
+CONTRIBUTING, etc. files) that help to discover it, explain the legal
+terms of reusing it, describe its functionality and how to install, run
+and contribute to it, to whole websites full of documentation with
+function definitions, usage examples, tutorials and guides. You many not
+need as much documentation as a large commercial software product, but
+making your code reusable relies on other people being able to
+understand what your code does and how to use it.</p>
+</div>
+<div class="section level3">
+<h3 id="software-repositories-and-registries">Software repositories and registries<a class="anchor" aria-label="anchor" href="#software-repositories-and-registries"></a>
+</h3>
 <p>Having somewhere to share your code is fundamental to making it
-Findable. Your institution might have a code repository, your research
-field may have a practice of sharing code via a specific website or
-journal, or your version control system might include an online
-component that makes sharing different versions of your code easy.
-Again, remember to check the rules of your institution and grant on
-publishing code, and any licenses for code you depend on or reuse.</p>
-<p>We will discuss later how to share your code on GitHub and make it
-easy for others to find and use.</p>
-</section><section><h2 class="section-heading" id="summary-of-tools-practices">Summary of tools &amp; practices<a class="anchor" aria-label="anchor" href="#summary-of-tools-practices"></a>
-</h2>
-<hr class="half-width">
-<p>The table below summarises some tools and practices that can help
-with each of the FAIR software principles.</p>
+findable and accessible. Your institution might have a code repository,
+your research field may have a practice of sharing code via a specific
+website, archive or journal, or your version control system might
+include an online component that makes sharing different versions of
+your code easy. You should check the rules or guidelines of your
+institution, grant or domain on publishing code, as well as any licenses
+of the code your software depends on or reuses.</p>
+<p>Some examples of commonly used software repositories and registries
+include:</p>
+<ul>
+<li>general-purpose software repositories, such as <a href="https://github.com" class="external-link">GitHub</a> and <a href="https://about.gitlab.com/" class="external-link">GitLab</a>
+</li>
+<li>programming language-specific software repositories, such as <a href="https://pypi.org/" class="external-link">PyPi</a> (for Python) and <a href="https://cran.r-project.org/web/packages/" class="external-link">CRAN</a> (for R)</li>
+<li>software registries, such as <a href="https://biotools.us/" class="external-link">BioTools</a> (for biosciences) and <a href="https://github.com/NLeSC/awesome-research-software-registries" class="external-link">Awesome
+Research Software Registries</a> (providing a list of research software
+registries by country, organisation, domain and programming language)
+where research software can be registered to help promote its
+discovery</li>
+</ul>
+</div>
+<div class="section level3">
+<h3 id="persistent-identifiers">Persistent identifiers<a class="anchor" aria-label="anchor" href="#persistent-identifiers"></a>
+</h3>
+<p>Unique persistent identifiers, such as Digital Object Identifiers
+(DOIs) provided by <a href="https://zenodo.org/" class="external-link">Zenodo</a>, <a href="https://figshare.com/" class="external-link">FigShare</a> and similar digital archiving
+services, and commits/tags/releases used by GitHub and similar code
+sharing platforms, help with findability and accessibility of your
+software, and can help you get credit for your work by providing citable
+references.</p>
+</div>
+<div class="section level3">
+<h3 id="tools-and-practices-summary">Tools and practices summary<a class="anchor" aria-label="anchor" href="#tools-and-practices-summary"></a>
+</h3>
+<p>The table below provides a summary of how different tools and
+practices help with the FAIR software principles.</p>
 <table class="table">
 <colgroup>
-<col width="67%">
-<col width="6%">
-<col width="8%">
-<col width="10%">
-<col width="6%">
+<col width="71%">
+<col width="5%">
+<col width="7%">
+<col width="9%">
+<col width="5%">
 </colgroup>
 <thead><tr class="header">
 <th>Tools and practices</th>
@@ -1372,28 +1370,40 @@ <h3 class="card-title">Objectives</h3>
 </tr></thead>
 <tbody>
 <tr class="odd">
-<td>Virtual development environments, programming language and
-dependencies - run, test, debug, share</td>
+<td>Virtual development environments</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
 </tr>
 <tr class="even">
-<td>Integrated development environments/IDEs (e.g. VS Code, PyCharm) -
-run, test, debug</td>
+<td>Integrated development environments/IDEs</td>
 <td></td>
 <td></td>
 <td></td>
 <td>x</td>
 </tr>
 <tr class="odd">
-<td>Command line terminal (e.g. Bash, GitBash) - reproducible
-workflows/pipelines</td>
+<td>Command line terminals - automated and reproducible pipelines</td>
+<td></td>
+<td></td>
+<td>x</td>
+<td>x</td>
+</tr>
+<tr class="even">
+<td>Standard formats - e.g. for data exchange (CSV, YAML)</td>
 <td></td>
+<td>x</td>
+<td>x</td>
+<td>x</td>
+</tr>
+<tr class="odd">
+<td>Communication protocols - Command Line Interface (CLI) or
+Application Programming Interface (API)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
+<td>x</td>
 </tr>
 <tr class="even">
 <td>Version control tools</td>
@@ -1403,76 +1413,71 @@ <h3 class="card-title">Objectives</h3>
 <td></td>
 </tr>
 <tr class="odd">
-<td>Testing - code correctness and reproducibility</td>
+<td>Code testing and correctness</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
 </tr>
 <tr class="even">
-<td>Coding conventions and documentation</td>
+<td>Code style conventions</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
 </tr>
 <tr class="odd">
-<td>Explaining functionality/installation/running - README, inline
-comments and documentation</td>
+<td>Software-level documentation (comments and docstrings, explaining
+functionality)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
 </tr>
 <tr class="even">
-<td>Standard formats - e.g. for data exchange (CSV, YAML)</td>
+<td>Project-level documentation (READMEs, explaining
+functionality/installation/running)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
 </tr>
 <tr class="odd">
-<td>Communication protocols - Command Line Interface (CLI) or
-Application Programming Interface (API)</td>
-<td></td>
-<td>x</td>
-<td>x</td>
-<td>x</td>
-</tr>
-<tr class="even">
-<td>License</td>
+<td>License - code sharing and reuse</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
 </tr>
-<tr class="odd">
-<td>Citation</td>
+<tr class="even">
+<td>Citation - code reuse and credit</td>
 <td>x</td>
 <td></td>
 <td></td>
 <td>x</td>
 </tr>
-<tr class="even">
-<td>Software repositories (e.g. GitHub, PyPi) or registries
-(e.g. BioTools)</td>
+<tr class="odd">
+<td>Software repositories and registries - code sharing</td>
 <td>x</td>
 <td>x</td>
 <td></td>
 <td></td>
 </tr>
-<tr class="odd">
-<td>Unique persistent identifier (e.g. DOIs, commits/tags/releases) -
-Zenodo, FigShare GitHub</td>
+<tr class="even">
+<td>Unique persistent identifiers - finding and citing software</td>
 <td>x</td>
 <td>x</td>
 <td></td>
 <td></td>
 </tr>
 </tbody>
-</table></section><section><h2 class="section-heading" id="checking-your-setup">Checking your setup<a class="anchor" aria-label="anchor" href="#checking-your-setup"></a>
+</table>
+</div>
+<section><h2 class="section-heading" id="checking-your-setup">Checking your setup<a class="anchor" aria-label="anchor" href="#checking-your-setup"></a>
 </h2>
 <hr class="half-width">
+<p>Let’s check your setup now to make sure you are ready for the rest of
+this course.</p>
 <div id="checking-your-setup-1" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
@@ -1628,7 +1633,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-04-version-control"><p>Content from <a href="04-version-control.html">Version control</a></p>
 <hr>
-<p>Last updated on 2024-09-24 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/04-version-control.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -2075,14 +2080,13 @@ <h3 id="rename-our-data-and-output-files">Rename our data and output files<a cla
 <li>choose informative file names for our output data file and
 plot.</li>
 </ol>
-<p>First let’s update file names in our script.</p>
+<p>First let’s update file names in our script using VS Code.</p>
 <div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb26-2"><a href="#cb26-2" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb26-3"><a href="#cb26-3" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
-<span id="cb26-4"><a href="#cb26-4" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>   </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb26-2"><a href="#cb26-2" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
+<span id="cb26-3"><a href="#cb26-3" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>   </span></code></pre>
 </div>
 <p>Now, let’s actually rename our files on the file system using git and
 commit our changes.</p>
@@ -2512,7 +2516,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-05-code-environment"><p>Content from <a href="05-code-environment.html">Reproducible development environment</a></p>
 <hr>
-<p>Last updated on 2024-09-24 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/05-code-environment.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -2932,6 +2936,18 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 file accordingly by re-issuing <code>pip freeze</code> command and
 propagate the updated <code>requirements.txt</code> file to your
 collaborators via your code sharing platform.</p>
+</section><section><h2 class="section-heading" id="running-the-code">Running the code<a class="anchor" aria-label="anchor" href="#running-the-code"></a>
+</h2>
+<hr class="half-width">
+<p>We are now setup to run our code from the newly created virtual
+environment:</p>
+<div class="codewrapper sourceCode" id="cb25">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py</span></code></pre>
+</div>
+<p>You should get a pop up window with a graph. Let’s inspect the code
+in a more detail, see if we can understand and improve it.</p>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a>
 </h2>
 <hr class="half-width">
@@ -2971,7 +2987,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-06-code-readability"><p>Content from <a href="06-code-readability.html">Code readability</a></p>
 <hr>
-<p>Last updated on 2024-09-26 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/06-code-readability.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -3064,69 +3080,67 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="codewrapper sourceCode" id="cb2">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a></span>
-<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb2-3"><a href="#cb2-3" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb2-4"><a href="#cb2-4" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
-<span id="cb2-5"><a href="#cb2-5" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>  </span>
-<span id="cb2-6"><a href="#cb2-6" tabindex="-1"></a></span>
-<span id="cb2-7"><a href="#cb2-7" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
-<span id="cb2-8"><a href="#cb2-8" tabindex="-1"></a></span>
-<span id="cb2-9"><a href="#cb2-9" tabindex="-1"></a>data<span class="op">=</span>[]</span>
-<span id="cb2-10"><a href="#cb2-10" tabindex="-1"></a><span class="im">import</span> json</span>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="im">import</span> json</span>
+<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="im">import</span> csv</span>
+<span id="cb2-3"><a href="#cb2-3" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
+<span id="cb2-4"><a href="#cb2-4" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb2-5"><a href="#cb2-5" tabindex="-1"></a></span>
+<span id="cb2-6"><a href="#cb2-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb2-7"><a href="#cb2-7" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb2-8"><a href="#cb2-8" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
+<span id="cb2-9"><a href="#cb2-9" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span> </span>
+<span id="cb2-10"><a href="#cb2-10" tabindex="-1"></a></span>
 <span id="cb2-11"><a href="#cb2-11" tabindex="-1"></a></span>
-<span id="cb2-12"><a href="#cb2-12" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> <span class="bu">range</span>(<span class="dv">374</span>):</span>
-<span id="cb2-13"><a href="#cb2-13" tabindex="-1"></a>    line<span class="op">=</span>data_f.readline()</span>
-<span id="cb2-14"><a href="#cb2-14" tabindex="-1"></a>    <span class="bu">print</span>(line)</span>
-<span id="cb2-15"><a href="#cb2-15" tabindex="-1"></a>    data.append(json.loads(line[<span class="dv">1</span>:<span class="op">-</span><span class="dv">1</span>]))</span>
-<span id="cb2-16"><a href="#cb2-16" tabindex="-1"></a><span class="co">#data.pop(0)</span></span>
-<span id="cb2-17"><a href="#cb2-17" tabindex="-1"></a><span class="co">## Comment out this bit if you don't want the spreadsheet</span></span>
-<span id="cb2-18"><a href="#cb2-18" tabindex="-1"></a><span class="im">import</span> csv</span>
-<span id="cb2-19"><a href="#cb2-19" tabindex="-1"></a></span>
-<span id="cb2-20"><a href="#cb2-20" tabindex="-1"></a>w<span class="op">=</span>csv.writer(data_t)</span>
-<span id="cb2-21"><a href="#cb2-21" tabindex="-1"></a></span>
-<span id="cb2-22"><a href="#cb2-22" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
-<span id="cb2-23"><a href="#cb2-23" tabindex="-1"></a></span>
-<span id="cb2-24"><a href="#cb2-24" tabindex="-1"></a>time <span class="op">=</span> []</span>
-<span id="cb2-25"><a href="#cb2-25" tabindex="-1"></a>date <span class="op">=</span>[]</span>
-<span id="cb2-26"><a href="#cb2-26" tabindex="-1"></a></span>
-<span id="cb2-27"><a href="#cb2-27" tabindex="-1"></a>j<span class="op">=</span><span class="dv">0</span></span>
-<span id="cb2-28"><a href="#cb2-28" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> data:</span>
-<span id="cb2-29"><a href="#cb2-29" tabindex="-1"></a>    <span class="bu">print</span>(data[j])</span>
-<span id="cb2-30"><a href="#cb2-30" tabindex="-1"></a>    <span class="co"># and this bit</span></span>
-<span id="cb2-31"><a href="#cb2-31" tabindex="-1"></a>    w.writerow(data[j].values())</span>
-<span id="cb2-32"><a href="#cb2-32" tabindex="-1"></a>    <span class="cf">if</span> <span class="st">'duration'</span> <span class="kw">in</span> data[j].keys():</span>
-<span id="cb2-33"><a href="#cb2-33" tabindex="-1"></a>        tt<span class="op">=</span>data[j][<span class="st">'duration'</span>]</span>
-<span id="cb2-34"><a href="#cb2-34" tabindex="-1"></a>        <span class="cf">if</span> tt <span class="op">==</span> <span class="st">''</span>:</span>
-<span id="cb2-35"><a href="#cb2-35" tabindex="-1"></a>            <span class="cf">pass</span></span>
-<span id="cb2-36"><a href="#cb2-36" tabindex="-1"></a>        <span class="cf">else</span>:</span>
-<span id="cb2-37"><a href="#cb2-37" tabindex="-1"></a>            t<span class="op">=</span>dt.datetime.strptime(tt,<span class="st">'%H:%M'</span>)</span>
-<span id="cb2-38"><a href="#cb2-38" tabindex="-1"></a>            ttt <span class="op">=</span> dt.timedelta(hours<span class="op">=</span>t.hour, minutes<span class="op">=</span>t.minute, seconds<span class="op">=</span>t.second).total_seconds()<span class="op">/</span>(<span class="dv">60</span><span class="op">*</span><span class="dv">60</span>)</span>
-<span id="cb2-39"><a href="#cb2-39" tabindex="-1"></a>            <span class="bu">print</span>(t,ttt)</span>
-<span id="cb2-40"><a href="#cb2-40" tabindex="-1"></a>            time.append(ttt)</span>
-<span id="cb2-41"><a href="#cb2-41" tabindex="-1"></a>            <span class="cf">if</span> <span class="st">'date'</span> <span class="kw">in</span> data[j].keys():</span>
-<span id="cb2-42"><a href="#cb2-42" tabindex="-1"></a>                date.append(dt.datetime.strptime(data[j][<span class="st">'date'</span>][<span class="dv">0</span>:<span class="dv">10</span>], <span class="st">'%Y-%m-</span><span class="sc">%d</span><span class="st">'</span>))</span>
-<span id="cb2-43"><a href="#cb2-43" tabindex="-1"></a>                <span class="co">#date.append(data[j]['date'][0:10])</span></span>
-<span id="cb2-44"><a href="#cb2-44" tabindex="-1"></a></span>
-<span id="cb2-45"><a href="#cb2-45" tabindex="-1"></a>            <span class="cf">else</span>:</span>
-<span id="cb2-46"><a href="#cb2-46" tabindex="-1"></a>                time.pop(<span class="dv">0</span>)</span>
-<span id="cb2-47"><a href="#cb2-47" tabindex="-1"></a>    j<span class="op">+=</span><span class="dv">1</span></span>
-<span id="cb2-48"><a href="#cb2-48" tabindex="-1"></a></span>
-<span id="cb2-49"><a href="#cb2-49" tabindex="-1"></a>t<span class="op">=</span>[<span class="dv">0</span>]</span>
-<span id="cb2-50"><a href="#cb2-50" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> time:</span>
-<span id="cb2-51"><a href="#cb2-51" tabindex="-1"></a>    t.append(t[<span class="op">-</span><span class="dv">1</span>]<span class="op">+</span>i)</span>
-<span id="cb2-52"><a href="#cb2-52" tabindex="-1"></a></span>
-<span id="cb2-53"><a href="#cb2-53" tabindex="-1"></a>date,time <span class="op">=</span> <span class="bu">zip</span>(<span class="op">*</span><span class="bu">sorted</span>(<span class="bu">zip</span>(date, time)))</span>
-<span id="cb2-54"><a href="#cb2-54" tabindex="-1"></a></span>
-<span id="cb2-55"><a href="#cb2-55" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb2-56"><a href="#cb2-56" tabindex="-1"></a></span>
-<span id="cb2-57"><a href="#cb2-57" tabindex="-1"></a>plt.plot(date,t[<span class="dv">1</span>:], <span class="st">'ko-'</span>)</span>
-<span id="cb2-58"><a href="#cb2-58" tabindex="-1"></a>plt.xlabel(<span class="st">'Year'</span>)</span>
-<span id="cb2-59"><a href="#cb2-59" tabindex="-1"></a>plt.ylabel(<span class="st">'Total time spent in space to date (hours)'</span>)</span>
-<span id="cb2-60"><a href="#cb2-60" tabindex="-1"></a>plt.tight_layout()</span>
-<span id="cb2-61"><a href="#cb2-61" tabindex="-1"></a>plt.savefig(g_file)</span>
-<span id="cb2-62"><a href="#cb2-62" tabindex="-1"></a>plt.show()</span>
-<span id="cb2-63"><a href="#cb2-63" tabindex="-1"></a></span></code></pre>
+<span id="cb2-12"><a href="#cb2-12" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
+<span id="cb2-13"><a href="#cb2-13" tabindex="-1"></a></span>
+<span id="cb2-14"><a href="#cb2-14" tabindex="-1"></a>data<span class="op">=</span>[]</span>
+<span id="cb2-15"><a href="#cb2-15" tabindex="-1"></a></span>
+<span id="cb2-16"><a href="#cb2-16" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> <span class="bu">range</span>(<span class="dv">374</span>):</span>
+<span id="cb2-17"><a href="#cb2-17" tabindex="-1"></a>    line<span class="op">=</span>data_f.readline()</span>
+<span id="cb2-18"><a href="#cb2-18" tabindex="-1"></a>    <span class="bu">print</span>(line)</span>
+<span id="cb2-19"><a href="#cb2-19" tabindex="-1"></a>    data.append(json.loads(line[<span class="dv">1</span>:<span class="op">-</span><span class="dv">1</span>]))</span>
+<span id="cb2-20"><a href="#cb2-20" tabindex="-1"></a><span class="co">#data.pop(0)</span></span>
+<span id="cb2-21"><a href="#cb2-21" tabindex="-1"></a><span class="co">## Comment out this bit if you don't want the spreadsheet</span></span>
+<span id="cb2-22"><a href="#cb2-22" tabindex="-1"></a></span>
+<span id="cb2-23"><a href="#cb2-23" tabindex="-1"></a>w<span class="op">=</span>csv.writer(data_t)</span>
+<span id="cb2-24"><a href="#cb2-24" tabindex="-1"></a></span>
+<span id="cb2-25"><a href="#cb2-25" tabindex="-1"></a>time <span class="op">=</span> []</span>
+<span id="cb2-26"><a href="#cb2-26" tabindex="-1"></a>date <span class="op">=</span>[]</span>
+<span id="cb2-27"><a href="#cb2-27" tabindex="-1"></a></span>
+<span id="cb2-28"><a href="#cb2-28" tabindex="-1"></a>j<span class="op">=</span><span class="dv">0</span></span>
+<span id="cb2-29"><a href="#cb2-29" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> data:</span>
+<span id="cb2-30"><a href="#cb2-30" tabindex="-1"></a>    <span class="bu">print</span>(data[j])</span>
+<span id="cb2-31"><a href="#cb2-31" tabindex="-1"></a>    <span class="co"># and this bit</span></span>
+<span id="cb2-32"><a href="#cb2-32" tabindex="-1"></a>    w.writerow(data[j].values())</span>
+<span id="cb2-33"><a href="#cb2-33" tabindex="-1"></a>    <span class="cf">if</span> <span class="st">'duration'</span> <span class="kw">in</span> data[j].keys():</span>
+<span id="cb2-34"><a href="#cb2-34" tabindex="-1"></a>        tt<span class="op">=</span>data[j][<span class="st">'duration'</span>]</span>
+<span id="cb2-35"><a href="#cb2-35" tabindex="-1"></a>        <span class="cf">if</span> tt <span class="op">==</span> <span class="st">''</span>:</span>
+<span id="cb2-36"><a href="#cb2-36" tabindex="-1"></a>            <span class="cf">pass</span></span>
+<span id="cb2-37"><a href="#cb2-37" tabindex="-1"></a>        <span class="cf">else</span>:</span>
+<span id="cb2-38"><a href="#cb2-38" tabindex="-1"></a>            t<span class="op">=</span>dt.datetime.strptime(tt,<span class="st">'%H:%M'</span>)</span>
+<span id="cb2-39"><a href="#cb2-39" tabindex="-1"></a>            ttt <span class="op">=</span> dt.timedelta(hours<span class="op">=</span>t.hour, minutes<span class="op">=</span>t.minute, seconds<span class="op">=</span>t.second).total_seconds()<span class="op">/</span>(<span class="dv">60</span><span class="op">*</span><span class="dv">60</span>)</span>
+<span id="cb2-40"><a href="#cb2-40" tabindex="-1"></a>            <span class="bu">print</span>(t,ttt)</span>
+<span id="cb2-41"><a href="#cb2-41" tabindex="-1"></a>            time.append(ttt)</span>
+<span id="cb2-42"><a href="#cb2-42" tabindex="-1"></a>            <span class="cf">if</span> <span class="st">'date'</span> <span class="kw">in</span> data[j].keys():</span>
+<span id="cb2-43"><a href="#cb2-43" tabindex="-1"></a>                date.append(dt.datetime.strptime(data[j][<span class="st">'date'</span>][<span class="dv">0</span>:<span class="dv">10</span>], <span class="st">'%Y-%m-</span><span class="sc">%d</span><span class="st">'</span>))</span>
+<span id="cb2-44"><a href="#cb2-44" tabindex="-1"></a>                <span class="co">#date.append(data[j]['date'][0:10])</span></span>
+<span id="cb2-45"><a href="#cb2-45" tabindex="-1"></a></span>
+<span id="cb2-46"><a href="#cb2-46" tabindex="-1"></a>            <span class="cf">else</span>:</span>
+<span id="cb2-47"><a href="#cb2-47" tabindex="-1"></a>                time.pop(<span class="dv">0</span>)</span>
+<span id="cb2-48"><a href="#cb2-48" tabindex="-1"></a>    j<span class="op">+=</span><span class="dv">1</span></span>
+<span id="cb2-49"><a href="#cb2-49" tabindex="-1"></a></span>
+<span id="cb2-50"><a href="#cb2-50" tabindex="-1"></a>t<span class="op">=</span>[<span class="dv">0</span>]</span>
+<span id="cb2-51"><a href="#cb2-51" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> time:</span>
+<span id="cb2-52"><a href="#cb2-52" tabindex="-1"></a>    t.append(t[<span class="op">-</span><span class="dv">1</span>]<span class="op">+</span>i)</span>
+<span id="cb2-53"><a href="#cb2-53" tabindex="-1"></a></span>
+<span id="cb2-54"><a href="#cb2-54" tabindex="-1"></a>date,time <span class="op">=</span> <span class="bu">zip</span>(<span class="op">*</span><span class="bu">sorted</span>(<span class="bu">zip</span>(date, time)))</span>
+<span id="cb2-55"><a href="#cb2-55" tabindex="-1"></a></span>
+<span id="cb2-56"><a href="#cb2-56" tabindex="-1"></a>plt.plot(date,t[<span class="dv">1</span>:], <span class="st">'ko-'</span>)</span>
+<span id="cb2-57"><a href="#cb2-57" tabindex="-1"></a>plt.xlabel(<span class="st">'Year'</span>)</span>
+<span id="cb2-58"><a href="#cb2-58" tabindex="-1"></a>plt.ylabel(<span class="st">'Total time spent in space to date (hours)'</span>)</span>
+<span id="cb2-59"><a href="#cb2-59" tabindex="-1"></a>plt.tight_layout()</span>
+<span id="cb2-60"><a href="#cb2-60" tabindex="-1"></a>plt.savefig(g_file)</span>
+<span id="cb2-61"><a href="#cb2-61" tabindex="-1"></a>plt.show()</span></code></pre>
 </div>
 <p>Let’s make sure we commit our changes.</p>
 <div class="codewrapper sourceCode" id="cb3">
@@ -3214,7 +3228,7 @@ <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
 <div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
 <div class="accordion-body">
-<p>Yes, <span class="math display">\[9.81 m/s^2 \]</span> is the <a href="https://en.wikipedia.org/wiki/Gravity_of_Earth" class="external-link">gravitational
+<p><span class="math display">\[ 9.81 m/s^2 \]</span> is the <a href="https://en.wikipedia.org/wiki/Gravity_of_Earth" class="external-link">gravitational
 force exerted by the Earth</a>. It is often referred to as “little g” to
 distinguish it from “big G” which is the <a href="https://en.wikipedia.org/wiki/Gravitational_constant" class="external-link">Gravitational
 Constant</a>. A more descriptive name for this variable therefore might
@@ -3228,12 +3242,12 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 </div>
 </div>
-<div id="challenge2" class="callout challenge">
+<div id="rename-our-variables-to-be-more-descriptive" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
 </div>
-<div class="callout-inner">
-<h3 class="callout-title">Challenge</h3>
+<div id="rename-our-variables-to-be-more-descriptive" class="callout-inner">
+<h3 class="callout-title">Rename our variables to be more descriptive</h3>
 <div class="callout-content">
 <p>Let’s apply this to <code>eva_data_analysis.py</code>.</p>
 <ol style="list-style-type: lower-alpha">
@@ -3264,16 +3278,16 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <div class="codewrapper sourceCode" id="cb6">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a></span>
-<span id="cb6-2"><a href="#cb6-2" tabindex="-1"></a><span class="im">import</span> json</span>
-<span id="cb6-3"><a href="#cb6-3" tabindex="-1"></a><span class="im">import</span> csv</span>
-<span id="cb6-4"><a href="#cb6-4" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
-<span id="cb6-5"><a href="#cb6-5" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb6-6"><a href="#cb6-6" tabindex="-1"></a></span>
-<span id="cb6-7"><a href="#cb6-7" tabindex="-1"></a><span class="co"># Data source: https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb6-8"><a href="#cb6-8" tabindex="-1"></a>input_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb6-9"><a href="#cb6-9" tabindex="-1"></a>output_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>, <span class="st">'w'</span>)</span>
-<span id="cb6-10"><a href="#cb6-10" tabindex="-1"></a>graph_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span></span>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a><span class="im">import</span> json</span>
+<span id="cb6-2"><a href="#cb6-2" tabindex="-1"></a><span class="im">import</span> csv</span>
+<span id="cb6-3"><a href="#cb6-3" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
+<span id="cb6-4"><a href="#cb6-4" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb6-5"><a href="#cb6-5" tabindex="-1"></a></span>
+<span id="cb6-6"><a href="#cb6-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb6-7"><a href="#cb6-7" tabindex="-1"></a>input_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb6-8"><a href="#cb6-8" tabindex="-1"></a>output_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>, <span class="st">'w'</span>)</span>
+<span id="cb6-9"><a href="#cb6-9" tabindex="-1"></a>graph_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span></span>
+<span id="cb6-10"><a href="#cb6-10" tabindex="-1"></a></span>
 <span id="cb6-11"><a href="#cb6-11" tabindex="-1"></a></span>
 <span id="cb6-12"><a href="#cb6-12" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
 <span id="cb6-13"><a href="#cb6-13" tabindex="-1"></a></span>
@@ -3591,19 +3605,20 @@ <h3 class="callout-title">Callout</h3>
 functionality:</p>
 <ol style="list-style-type: decimal">
 <li>reading the data from a JSON file</li>
+<li>converting and saving the data in the CSV format</li>
 <li>processing/cleaning the data and preparing it for analysis</li>
 <li>data analysis and visualising the results</li>
-<li>converting and saving the data in the CSV format</li>
 </ol>
 <p>Let’s refactor our code so that reading the data in JSON format into
 a dataframe (step 1.) and converting it and saving to the CSV format
-(step 4.) are extracted into separate functions. Let’s name those
+(step 2.) are extracted into separate functions. Let’s name those
 functions <code>read_json_to_dataframe</code> and
 <code>write_dataframe_to_csv</code> respectively. The main part of the
 script should then be simplified to invoke these new functions, while
 the functions themselves contain the complexity of each of these two
-steps.</p>
-<p>Our code may look something like the following.</p>
+steps. We will continue to work on steps 3. and 4. above later on.</p>
+<p>After the initial refactoring, our code may look something like the
+following.</p>
 <div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -3655,19 +3670,23 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <span id="cb17-46"><a href="#cb17-46" tabindex="-1"></a></span>
 <span id="cb17-47"><a href="#cb17-47" tabindex="-1"></a><span class="bu">print</span>(<span class="st">"--END--"</span>)</span></code></pre>
 </div>
-<p>We have chosen to create function for reading in and writing out data
-files since this is a very common task within research software. While
-these functions do not contain that many lines of code due to using the
-<code>pandas</code> in-built methods that do all the complex data
-reading, converting and writing operations, it can be useful to package
-these steps together into reusable functions if you need to read in or
-write out a lot of similarly structured files and process them in the
-same way.</p>
+<p>We have chosen to create functions for reading in and writing out
+data files since this is a very common task within research software.
+While these functions do not contain that many lines of code due to
+using the <code>pandas</code> in-built methods that do all the complex
+data reading, converting and writing operations, it can be useful to
+package these steps together into reusable functions if you need to read
+in or write out a lot of similarly structured files and process them in
+the same way.</p>
 </section><section><h2 class="section-heading" id="use-docstrings-to-document-functions">Use docstrings to document functions<a class="anchor" aria-label="anchor" href="#use-docstrings-to-document-functions"></a>
 </h2>
 <hr class="half-width">
-<p>Docstrings are a specific type of documentation that are provided
-within functions and <a href="https://docs.python.org/3/tutorial/classes.html" class="external-link">Python
+<p>Now that we have written some functions, it is time to document them
+so that we can quickly recall (and others looking at our code in the
+future can understand) what the functions doe without having to read the
+code.</p>
+<p><em>Docstrings</em> are a specific type of documentation that are
+provided within functions and <a href="https://docs.python.org/3/tutorial/classes.html" class="external-link">Python
 classes</a>. A function docstring should explain what that particular
 code is doing, what parameters the function needs (inputs) and what form
 they should take, what the function outputs (you may see words like
@@ -3941,7 +3960,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-07-code-structure"><p>Content from <a href="07-code-structure.html">Code structure</a></p>
 <hr>
-<p>Last updated on 2024-09-26 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/07-code-structure.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -3955,7 +3974,7 @@ <h2 class="card-header">Overview</h2>
 <div class="inner">
 <h3 class="card-title">Questions</h3>
 <ul>
-<li>How can we bests structure code?</li>
+<li>How can we best structure code?</li>
 <li>What is a common code structure (pattern) for creating software that
 can read input from command line?</li>
 <li>What are conventional places to store data, code, results, tests,
@@ -4215,7 +4234,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 set by the Python interpreter before the execution of any code in the
 source file. What value is given by the interpreter to
 <code>__name__</code> is determined by the manner in which the script is
-loaded.</p>
+invoked.</p>
 <p>If we run the source file directly using the Python interpreter,
 e.g.:</p>
 <div class="codewrapper sourceCode" id="cb5">
@@ -4240,7 +4259,8 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="im">import</span> eva_data_analysis</span></code></pre>
 </div>
 <p>then the Python interpreter will assign the name “eva_data_analysis”
-from the import statement to the <code>__name__</code> variable:</p>
+from the import statement to the <code>__name__</code> variable (note
+that import statement matches our script’s name):</p>
 <div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -4258,7 +4278,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 to do this:</p>
 <ul>
 <li>for testing of your code, you can have your testing framework import
-the main script, and run special test functions which then call the
+your script, and run special test functions which then call the
 <code>main</code> function directly;</li>
 <li>where you want to not only be able to run your script from the
 command-line, but also provide a programmer-friendly application
@@ -4400,7 +4420,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python eva_data_analysis.py eva_data.json eva_data.csv</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python eva_data_analysis.py eva-data.json eva-data.csv</span></code></pre>
 </div>
 <p>Remember to commit our changes.</p>
 <div class="codewrapper sourceCode" id="cb11">
@@ -4463,7 +4483,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <li>Code and data should be version controlled; you can also version
 control manuscripts, results, etc.</li>
 <li>If data files are too large (or contain sensitive information) to
-track by version control, untrack them using .gitignore</li>
+track by version control, untrack them using
+<code>.gitignore</code>
+</li>
 <li>Use tags/releases to mark specific versions of results (a version
 submitted to a journal, dissertation version, poster version, etc.) so
 as to avoid using version numbers in file names and proliferation of
@@ -4505,7 +4527,8 @@ <h3 class="callout-title">Challenge</h3>
 <div class="callout-content">
 <p>Refactor your software project so that input data is stored in
 <code>data/</code> directory and results (the graph and CSV data files)
-saved in <code>results/</code> directory.</p>
+saved in <code>results/</code> directory. Remember to create the
+<code>results/</code> directory or your code will fail.</p>
 </div>
 </div>
 </div>
@@ -4646,20 +4669,13 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 </div>
 </div>
-<p>After the above exercise, you will be invoking your script from
-command line as:</p>
-<div class="codewrapper sourceCode" id="cb14">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python data/eva_data_analysis.py eva_data.json results/eva_data.csv</span></code></pre>
-</div>
 <p>Remember to commit your latest changes:</p>
-<div class="codewrapper sourceCode" id="cb15">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git status</span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add eva_data_analysis.py data results</span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Update project's directory structure"</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git status</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add eva_data_analysis.py data results</span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Update project's directory structure"</span></span></code></pre>
 </div>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a>
 </h2>
@@ -4697,7 +4713,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-08-code-correctness"><p>Content from <a href="08-code-correctness.html">Code correctness</a></p>
 <hr>
-<p>Last updated on 2024-09-26 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/08-code-correctness.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -4865,7 +4881,7 @@ <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </h2>
 <hr class="half-width">
 <p>How should we test our code? One approach is to copy/paste the code
-or a function into a Python terminal (different from command line
+or a function into a Python terminal (different from a command line
 terminal), which allows you to interact with the Python interpreter more
 directly.<br>
 From the Python terminal we can then run one function or a piece of code
@@ -5010,35 +5026,29 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </ul>
 <p>Let’s explore this process by writing some formal tests for our
 <code>text_to_duration</code> function.</p>
-<p>Let’s create a new Python file <code>test_code.py</code> in the root
-of our project directory to store our tests.</p>
-<div class="codewrapper sourceCode" id="cb7">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> cd spacewalks</span>
-<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch test_code.py</span></code></pre>
-</div>
+<p>In VS Code, create a new Python file <code>test_code.py</code> in the
+root of our project directory to store our tests.</p>
 <p>Like before in the Python terminal, we need to import
 <code>text_to_duration</code> into our test script. Then, we add our
 first test function:</p>
-<div class="codewrapper sourceCode" id="cb8">
+<div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a></span>
-<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a></span>
-<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a>    input_value <span class="op">=</span> <span class="st">"10:00"</span></span>
-<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a>    test_result <span class="op">=</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>    <span class="bu">print</span>(<span class="ss">f"text_to_duration('10:00') == 10? </span><span class="sc">{</span>test_result<span class="sc">}</span><span class="ss">"</span>)</span>
-<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a></span>
-<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a>test_text_to_duration()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a></span>
+<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb7-3"><a href="#cb7-3" tabindex="-1"></a></span>
+<span id="cb7-4"><a href="#cb7-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb7-5"><a href="#cb7-5" tabindex="-1"></a>    input_value <span class="op">=</span> <span class="st">"10:00"</span></span>
+<span id="cb7-6"><a href="#cb7-6" tabindex="-1"></a>    test_result <span class="op">=</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb7-7"><a href="#cb7-7" tabindex="-1"></a>    <span class="bu">print</span>(<span class="ss">f"text_to_duration('10:00') == 10? </span><span class="sc">{</span>test_result<span class="sc">}</span><span class="ss">"</span>)</span>
+<span id="cb7-8"><a href="#cb7-8" tabindex="-1"></a></span>
+<span id="cb7-9"><a href="#cb7-9" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <p>We can run this code from the command line terminal as:</p>
-<div class="codewrapper sourceCode" id="cb9">
+<div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span><span class="ex">$</span> python3 test_code.py </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span><span class="ex">$</span> python3 test_code.py </span></code></pre>
 </div>
 <p>This test checks that when we apply <code>text_to_duration</code> to
 input value <code>10:00</code>, the output matches the expected value of
@@ -5059,16 +5069,16 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <code>False</code>, <code>assert</code> raises an
 <code>AssertError</code>.</p>
 <p>Let’s rewrite our test with an <code>assert</code> statement:</p>
-<div class="codewrapper sourceCode" id="cb10">
+<div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a></span>
-<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a></span>
-<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a></span>
-<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a></span>
+<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a></span>
+<span id="cb9-4"><a href="#cb9-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb9-5"><a href="#cb9-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb9-6"><a href="#cb9-6" tabindex="-1"></a></span>
+<span id="cb9-7"><a href="#cb9-7" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <p>Notice that when we run <code>test_text_to_duration_integer()</code>,
 nothing happens - there is no output. That is because our function is
@@ -5076,75 +5086,78 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <p>Let’s add another test to check what happens when duration is not an
 integer number and if our function can handle durations with a non-zero
 minute component, and rerun our test code.</p>
-<div class="codewrapper sourceCode" id="cb11">
+<div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb11-2"><a href="#cb11-2" tabindex="-1"></a></span>
-<span id="cb11-3"><a href="#cb11-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb11-4"><a href="#cb11-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:15"</span>) <span class="op">==</span> <span class="fl">10.25</span></span>
-<span id="cb11-5"><a href="#cb11-5" tabindex="-1"></a></span>
-<span id="cb11-6"><a href="#cb11-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb11-7"><a href="#cb11-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb11-8"><a href="#cb11-8" tabindex="-1"></a></span>
-<span id="cb11-9"><a href="#cb11-9" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb11-10"><a href="#cb11-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a></span>
+<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:15"</span>) <span class="op">==</span> <span class="fl">10.25</span></span>
+<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a></span>
+<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb10-8"><a href="#cb10-8" tabindex="-1"></a></span>
+<span id="cb10-9"><a href="#cb10-9" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb10-10"><a href="#cb10-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="error" tabindex="0"><code>(venv_spacewalks) $ python3 test_code.py
 Traceback (most recent call last):
-  File "/Users/user/work/SSI/lessons/astronaut-data-analysis/test_code.py", line 12, in &lt;module&gt;
+  File "/Users/user/Desktop/spacewalks/test_code.py", line 9, in &lt;module&gt;
     test_text_to_duration_float()
-  File "/Users/user/work/SSI/lessons/astronaut-data-analysis/test_code.py", line 5, in test_text_to_duration_float
+  File "/Users/user/Desktop/spacewalks/test_code.py", line 4, in test_text_to_duration_float
     assert text_to_duration("10:15") == 10.25
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-AssertionError
-</code></pre>
+AssertionError</code></pre>
 </div>
 <p>Notice that this time, our test
 <code>test_text_to_duration_float</code> fails. Our assert statement has
 raised an <code>AssertionError</code> - a clear signal that there is a
-problem in our code that we need to fix. Python helpfully tells us which
-line of our code is problematic:</p>
-<div class="codewrapper sourceCode" id="cb13">
+problem in our code that we need to fix. We know that duration
+<code>10:15</code> should be converted to number <code>10.25</code>.
+What is wrong with our code? If we look at our
+<code>text_to_duration</code> function, we may identify the following
+line of our code as problematic:</p>
+<div class="codewrapper sourceCode" id="cb12">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a>...</span>
-<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span> </span>
-<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="kw">def</span> text_to_duration(duration):</span>
+<span id="cb12-2"><a href="#cb12-2" tabindex="-1"></a>    ...</span>
+<span id="cb12-3"><a href="#cb12-3" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span> </span>
+<span id="cb12-4"><a href="#cb12-4" tabindex="-1"></a>    ...</span></code></pre>
 </div>
 <p>You may notice that our conversion code is wrong - the minutes
 component should have been divided by 60 and not 6. We were able to spot
 this tiny bug by testing our code.</p>
 <p>Let’s fix the problematic line and rerun out tests.</p>
-<div class="codewrapper sourceCode" id="cb14">
+<div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a>...</span>
-<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">60</span> </span>
-<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a>...</span>
+<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">60</span> </span>
+<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a>...</span></code></pre>
 </div>
 <p>This time our tests run without problem.</p>
 <p>Should we add more tests or the tests we have so far are enough? What
-happens if our duration value is <code>01:20</code> (one hour and 20
-minutes) and our result is not a rational floating point number like
-<code>10.25</code> but an irrational number such as
+happens if our duration value is <code>10:20</code> (ten hours and 20
+minutes) and our result is not a rational floating point number (like
+<code>10.25</code>) but an irrational number such as
 <code>10.333333333</code>? Let’s tests for this.</p>
-<div class="codewrapper sourceCode" id="cb15">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a></span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> <span class="fl">10.333333</span></span>
-<span id="cb15-5"><a href="#cb15-5" tabindex="-1"></a></span>
-<span id="cb15-6"><a href="#cb15-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb15-7"><a href="#cb15-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb15-8"><a href="#cb15-8" tabindex="-1"></a></span>
-<span id="cb15-9"><a href="#cb15-9" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb15-10"><a href="#cb15-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a></span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb14-4"><a href="#cb14-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> <span class="fl">10.333333</span></span>
+<span id="cb14-5"><a href="#cb14-5" tabindex="-1"></a></span>
+<span id="cb14-6"><a href="#cb14-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb14-7"><a href="#cb14-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb14-8"><a href="#cb14-8" tabindex="-1"></a></span>
+<span id="cb14-9"><a href="#cb14-9" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb14-10"><a href="#cb14-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -5164,13 +5177,13 @@ <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></
 (<code>==</code>) to compare the equality of floating point numbers.
 Instead, we check that our floating point numbers are equal within a
 very small tolerance (e.g. 1e-5). Hence, our code should look like:</p>
-<div class="codewrapper sourceCode" id="cb17">
+<div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a>...</span>
-<span id="cb17-2"><a href="#cb17-2" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb17-3"><a href="#cb17-3" tabindex="-1"></a>    <span class="cf">assert</span> <span class="bu">abs</span>(text_to_duration(<span class="st">"10:20"</span>) <span class="op">-</span> <span class="fl">10.33333333</span>) <span class="op">&lt;</span> <span class="fl">1e-5</span></span>
-<span id="cb17-4"><a href="#cb17-4" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a>...</span>
+<span id="cb16-2"><a href="#cb16-2" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb16-3"><a href="#cb16-3" tabindex="-1"></a>    <span class="cf">assert</span> <span class="bu">abs</span>(text_to_duration(<span class="st">"10:20"</span>) <span class="op">-</span> <span class="fl">10.33333333</span>) <span class="op">&lt;</span> <span class="fl">1e-5</span></span>
+<span id="cb16-4"><a href="#cb16-4" tabindex="-1"></a>...</span></code></pre>
 </div>
 <p>You may have noticed that we have to repeat a lot of code to add each
 individual test for each test case. You may also have noticed that our
@@ -5191,10 +5204,10 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 code coverage extension <code>pytest-cov</code>. To install these
 libraries into our virtual environment, from the command line terminal
 do:</p>
-<div class="codewrapper sourceCode" id="cb18">
+<div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip install pytest pytest-cov</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip install pytest pytest-cov</span></code></pre>
 </div>
 <p>Let’s make sure that our tests are ready to work with
 <code>pytest</code>.</p>
@@ -5207,12 +5220,12 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 requirements, so there is nothing to do here. However, our script does
 contain lines to run each of our test functions. These are no-longer
 required as pytest will run our tests so we can remove them:</p>
-<div class="codewrapper sourceCode" id="cb19">
+<div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="co"># Delete these 2 lines</span></span>
-<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="co"># Delete these 2 lines</span></span>
+<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 </li>
 <li><p>It is also conventional when working with a testing framework to
@@ -5225,55 +5238,57 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 test suite is currently located in the root folder of our project. Let’s
 move it to a dedicated test folder and rename our
 <code>test_code.py</code> file to <code>test_eva_analysis.py</code>.</p>
-<div class="codewrapper sourceCode" id="cb20">
+<p>You can do it from VS Code or by typing the following commands in the
+command line terminal:</p>
+<div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir tests</span>
-<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mv test_code.py tests/test_eva_analysis.py</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir tests</span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mv test_code.py tests/test_eva_analysis.py</span></code></pre>
 </div>
 <p>Before we re-run our tests using <code>pytest</code>, let’s update
 our second test to use <code>pytest</code>’s function
 <code>approx()</code> which is specifically intended for comparing
 floating point numbers within a tolerance.</p>
-<div class="codewrapper sourceCode" id="cb21">
+<div class="codewrapper sourceCode" id="cb20">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a></span>
-<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> pytest.approx(<span class="fl">10.33333333</span>)</span>
-<span id="cb21-6"><a href="#cb21-6" tabindex="-1"></a></span>
-<span id="cb21-7"><a href="#cb21-7" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb21-8"><a href="#cb21-8" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb20-3"><a href="#cb20-3" tabindex="-1"></a></span>
+<span id="cb20-4"><a href="#cb20-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb20-5"><a href="#cb20-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> pytest.approx(<span class="fl">10.33333333</span>)</span>
+<span id="cb20-6"><a href="#cb20-6" tabindex="-1"></a></span>
+<span id="cb20-7"><a href="#cb20-7" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb20-8"><a href="#cb20-8" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span></code></pre>
 </div>
 <p>Let’s also add some inline comments to clarify what each test is
 doing and expand our syntax to highlight the logic behind our
 approach:</p>
-<div class="codewrapper sourceCode" id="cb22">
+<div class="codewrapper sourceCode" id="cb21">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a></span>
-<span id="cb22-4"><a href="#cb22-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb22-5"><a href="#cb22-5" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb22-6"><a href="#cb22-6" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
-<span id="cb22-7"><a href="#cb22-7" tabindex="-1"></a><span class="co">    for typical durations with a non-zero minute component</span></span>
-<span id="cb22-8"><a href="#cb22-8" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb22-9"><a href="#cb22-9" tabindex="-1"></a>    actual_result <span class="op">=</span> text_to_duration(<span class="st">"10:20"</span>) </span>
-<span id="cb22-10"><a href="#cb22-10" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="fl">10.33333333</span></span>
-<span id="cb22-11"><a href="#cb22-11" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> pytest.approx(expected_result)</span>
-<span id="cb22-12"><a href="#cb22-12" tabindex="-1"></a>    </span>
-<span id="cb22-13"><a href="#cb22-13" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb22-14"><a href="#cb22-14" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb22-15"><a href="#cb22-15" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
-<span id="cb22-16"><a href="#cb22-16" tabindex="-1"></a><span class="co">    for typical whole hour durations </span></span>
-<span id="cb22-17"><a href="#cb22-17" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb22-18"><a href="#cb22-18" tabindex="-1"></a>    actual_result <span class="op">=</span>  text_to_duration(<span class="st">"10:00"</span>)</span>
-<span id="cb22-19"><a href="#cb22-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">10</span></span>
-<span id="cb22-20"><a href="#cb22-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb22-21"><a href="#cb22-21" tabindex="-1"></a>    </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a></span>
+<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb21-6"><a href="#cb21-6" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
+<span id="cb21-7"><a href="#cb21-7" tabindex="-1"></a><span class="co">    for typical durations with a non-zero minute component</span></span>
+<span id="cb21-8"><a href="#cb21-8" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb21-9"><a href="#cb21-9" tabindex="-1"></a>    actual_result <span class="op">=</span> text_to_duration(<span class="st">"10:20"</span>) </span>
+<span id="cb21-10"><a href="#cb21-10" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="fl">10.33333333</span></span>
+<span id="cb21-11"><a href="#cb21-11" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> pytest.approx(expected_result)</span>
+<span id="cb21-12"><a href="#cb21-12" tabindex="-1"></a>    </span>
+<span id="cb21-13"><a href="#cb21-13" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb21-14"><a href="#cb21-14" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb21-15"><a href="#cb21-15" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
+<span id="cb21-16"><a href="#cb21-16" tabindex="-1"></a><span class="co">    for typical whole hour durations </span></span>
+<span id="cb21-17"><a href="#cb21-17" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb21-18"><a href="#cb21-18" tabindex="-1"></a>    actual_result <span class="op">=</span>  text_to_duration(<span class="st">"10:00"</span>)</span>
+<span id="cb21-19"><a href="#cb21-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">10</span></span>
+<span id="cb21-20"><a href="#cb21-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb21-21"><a href="#cb21-21" tabindex="-1"></a>    </span></code></pre>
 </div>
 <p>Writing our tests this way highlights the key idea that each test
 should compare the actual results returned by our function with expected
@@ -5281,23 +5296,23 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <p>Similarly, writing inline comments for our tests that complete the
 sentence “Test that …” helps us to understand what each test is doing
 and why it is needed.</p>
-<p>Before running out tests with <code>putest</code>, let’s reintroduce
+<p>Before running out tests with <code>pytest</code>, let’s reintroduce
 our old bug in function <code>text_to_duration</code> that affects the
 durations with a non-zero minute component like “10:20” but not those
 that are whole hours, e.g. “10:00”:</p>
-<div class="codewrapper sourceCode" id="cb23">
+<div class="codewrapper sourceCode" id="cb22">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a>    ...</span>
-<span id="cb23-2"><a href="#cb23-2" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span>  <span class="co"># Divide by 6 instead of 60</span></span>
-<span id="cb23-3"><a href="#cb23-3" tabindex="-1"></a>    ...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a>    ...</span>
+<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span>  <span class="co"># Divide by 6 instead of 60</span></span>
+<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a>    ...</span></code></pre>
 </div>
 <p>Finally, let’s run our tests with <code>pytest</code> from our
 project’s root directory (and not <code>tests</code> directory):</p>
-<div class="codewrapper sourceCode" id="cb24">
+<div class="codewrapper sourceCode" id="cb23">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest </span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -5352,6 +5367,7 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 
 =========================================== 2 passed in 0.63s =============================================</code></pre>
 </div>
+<p>This time, all out tests passed.</p>
 <div id="interpreting-pytest-output" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
@@ -5471,70 +5487,70 @@ <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 that alone is not enough to properly test code. We will now look into
 what makes a good test suite and good practices for testing code.</p>
 <p>Let’s start by considering the following scenario. A collaborator on
-our project has sent us the following code which adds a new column to
-our data containing the <code>crew_size</code> values capturing the
-number of astronauts participating in any given spacewalk. How do we
-know that it works as intended and that it will not break the rest of
-our code? For this, we need to write a test suite with a comprehensive
-coverage of the new code.</p>
-<div class="codewrapper sourceCode" id="cb28">
+our project has sent us the following code which adds a new column
+called <code>crew_size</code> to our data containing the number of
+astronauts participating in any given spacewalk. How do we know that it
+works as intended and that it will not break the rest of our code? For
+this, we need to write a test suite with a comprehensive coverage of the
+new code.</p>
+<div class="codewrapper sourceCode" id="cb27">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb28-1"><a href="#cb28-1" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb28-2"><a href="#cb28-2" tabindex="-1"></a><span class="im">import</span> pandas <span class="im">as</span> pd</span>
-<span id="cb28-3"><a href="#cb28-3" tabindex="-1"></a><span class="im">import</span> sys</span>
-<span id="cb28-4"><a href="#cb28-4" tabindex="-1"></a><span class="im">import</span> re <span class="co"># added this line</span></span>
-<span id="cb28-5"><a href="#cb28-5" tabindex="-1"></a></span>
-<span id="cb28-6"><a href="#cb28-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb28-7"><a href="#cb28-7" tabindex="-1"></a></span>
-<span id="cb28-8"><a href="#cb28-8" tabindex="-1"></a><span class="kw">def</span> main(input_file, output_file, graph_file):</span>
-<span id="cb28-9"><a href="#cb28-9" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--START--"</span>)</span>
-<span id="cb28-10"><a href="#cb28-10" tabindex="-1"></a></span>
-<span id="cb28-11"><a href="#cb28-11" tabindex="-1"></a>    eva_data <span class="op">=</span> read_json_to_dataframe(input_file)</span>
-<span id="cb28-12"><a href="#cb28-12" tabindex="-1"></a></span>
-<span id="cb28-13"><a href="#cb28-13" tabindex="-1"></a>    eva_data <span class="op">=</span> add_crew_size_column(eva_data) <span class="co"># added this line</span></span>
-<span id="cb28-14"><a href="#cb28-14" tabindex="-1"></a></span>
-<span id="cb28-15"><a href="#cb28-15" tabindex="-1"></a>    write_dataframe_to_csv(eva_data, output_file)</span>
-<span id="cb28-16"><a href="#cb28-16" tabindex="-1"></a></span>
-<span id="cb28-17"><a href="#cb28-17" tabindex="-1"></a>    plot_cumulative_time_in_space(eva_data, graph_file)</span>
-<span id="cb28-18"><a href="#cb28-18" tabindex="-1"></a></span>
-<span id="cb28-19"><a href="#cb28-19" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--END--"</span>)</span>
-<span id="cb28-20"><a href="#cb28-20" tabindex="-1"></a></span>
-<span id="cb28-21"><a href="#cb28-21" tabindex="-1"></a>... </span>
-<span id="cb28-22"><a href="#cb28-22" tabindex="-1"></a></span>
-<span id="cb28-23"><a href="#cb28-23" tabindex="-1"></a><span class="kw">def</span> calculate_crew_size(crew):</span>
-<span id="cb28-24"><a href="#cb28-24" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb28-25"><a href="#cb28-25" tabindex="-1"></a><span class="co">    Calculate the size of the crew for a single crew entry</span></span>
-<span id="cb28-26"><a href="#cb28-26" tabindex="-1"></a></span>
-<span id="cb28-27"><a href="#cb28-27" tabindex="-1"></a><span class="co">    Args:</span></span>
-<span id="cb28-28"><a href="#cb28-28" tabindex="-1"></a><span class="co">        crew (str): The text entry in the crew column containing a list of crew member names</span></span>
-<span id="cb28-29"><a href="#cb28-29" tabindex="-1"></a></span>
-<span id="cb28-30"><a href="#cb28-30" tabindex="-1"></a><span class="co">    Returns:</span></span>
-<span id="cb28-31"><a href="#cb28-31" tabindex="-1"></a><span class="co">        int: The crew size</span></span>
-<span id="cb28-32"><a href="#cb28-32" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb28-33"><a href="#cb28-33" tabindex="-1"></a>    <span class="cf">if</span> crew.split() <span class="op">==</span> []:</span>
-<span id="cb28-34"><a href="#cb28-34" tabindex="-1"></a>        <span class="cf">return</span> <span class="va">None</span></span>
-<span id="cb28-35"><a href="#cb28-35" tabindex="-1"></a>    <span class="cf">else</span>:</span>
-<span id="cb28-36"><a href="#cb28-36" tabindex="-1"></a>        <span class="cf">return</span> <span class="bu">len</span>(re.split(<span class="vs">r';'</span>, crew))<span class="op">-</span><span class="dv">1</span></span>
-<span id="cb28-37"><a href="#cb28-37" tabindex="-1"></a></span>
-<span id="cb28-38"><a href="#cb28-38" tabindex="-1"></a><span class="kw">def</span> add_crew_size_column(df):</span>
-<span id="cb28-39"><a href="#cb28-39" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb28-40"><a href="#cb28-40" tabindex="-1"></a><span class="co">    Add crew_size column to the dataset containing the value of the crew size</span></span>
-<span id="cb28-41"><a href="#cb28-41" tabindex="-1"></a></span>
-<span id="cb28-42"><a href="#cb28-42" tabindex="-1"></a><span class="co">    Args:</span></span>
-<span id="cb28-43"><a href="#cb28-43" tabindex="-1"></a><span class="co">        df (pd.DataFrame): The input data frame.</span></span>
-<span id="cb28-44"><a href="#cb28-44" tabindex="-1"></a></span>
-<span id="cb28-45"><a href="#cb28-45" tabindex="-1"></a><span class="co">    Returns:</span></span>
-<span id="cb28-46"><a href="#cb28-46" tabindex="-1"></a><span class="co">        df_copy (pd.DataFrame): A copy of df with the new crew_size variable added</span></span>
-<span id="cb28-47"><a href="#cb28-47" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb28-48"><a href="#cb28-48" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">'Adding crew size variable (crew_size) to dataset'</span>)</span>
-<span id="cb28-49"><a href="#cb28-49" tabindex="-1"></a>    df_copy <span class="op">=</span> df.copy()</span>
-<span id="cb28-50"><a href="#cb28-50" tabindex="-1"></a>    df_copy[<span class="st">"crew_size"</span>] <span class="op">=</span> df_copy[<span class="st">"crew"</span>].<span class="bu">apply</span>(</span>
-<span id="cb28-51"><a href="#cb28-51" tabindex="-1"></a>        calculate_crew_size</span>
-<span id="cb28-52"><a href="#cb28-52" tabindex="-1"></a>    )</span>
-<span id="cb28-53"><a href="#cb28-53" tabindex="-1"></a>    <span class="cf">return</span> df_copy</span>
-<span id="cb28-54"><a href="#cb28-54" tabindex="-1"></a>...</span>
-<span id="cb28-55"><a href="#cb28-55" tabindex="-1"></a>    </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb27-2"><a href="#cb27-2" tabindex="-1"></a><span class="im">import</span> pandas <span class="im">as</span> pd</span>
+<span id="cb27-3"><a href="#cb27-3" tabindex="-1"></a><span class="im">import</span> sys</span>
+<span id="cb27-4"><a href="#cb27-4" tabindex="-1"></a><span class="im">import</span> re <span class="co"># added this line</span></span>
+<span id="cb27-5"><a href="#cb27-5" tabindex="-1"></a></span>
+<span id="cb27-6"><a href="#cb27-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb27-7"><a href="#cb27-7" tabindex="-1"></a></span>
+<span id="cb27-8"><a href="#cb27-8" tabindex="-1"></a><span class="kw">def</span> main(input_file, output_file, graph_file):</span>
+<span id="cb27-9"><a href="#cb27-9" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--START--"</span>)</span>
+<span id="cb27-10"><a href="#cb27-10" tabindex="-1"></a></span>
+<span id="cb27-11"><a href="#cb27-11" tabindex="-1"></a>    eva_data <span class="op">=</span> read_json_to_dataframe(input_file)</span>
+<span id="cb27-12"><a href="#cb27-12" tabindex="-1"></a></span>
+<span id="cb27-13"><a href="#cb27-13" tabindex="-1"></a>    eva_data <span class="op">=</span> add_crew_size_column(eva_data) <span class="co"># added this line</span></span>
+<span id="cb27-14"><a href="#cb27-14" tabindex="-1"></a></span>
+<span id="cb27-15"><a href="#cb27-15" tabindex="-1"></a>    write_dataframe_to_csv(eva_data, output_file)</span>
+<span id="cb27-16"><a href="#cb27-16" tabindex="-1"></a></span>
+<span id="cb27-17"><a href="#cb27-17" tabindex="-1"></a>    plot_cumulative_time_in_space(eva_data, graph_file)</span>
+<span id="cb27-18"><a href="#cb27-18" tabindex="-1"></a></span>
+<span id="cb27-19"><a href="#cb27-19" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--END--"</span>)</span>
+<span id="cb27-20"><a href="#cb27-20" tabindex="-1"></a></span>
+<span id="cb27-21"><a href="#cb27-21" tabindex="-1"></a>... </span>
+<span id="cb27-22"><a href="#cb27-22" tabindex="-1"></a></span>
+<span id="cb27-23"><a href="#cb27-23" tabindex="-1"></a><span class="kw">def</span> calculate_crew_size(crew):</span>
+<span id="cb27-24"><a href="#cb27-24" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb27-25"><a href="#cb27-25" tabindex="-1"></a><span class="co">    Calculate the size of the crew for a single crew entry</span></span>
+<span id="cb27-26"><a href="#cb27-26" tabindex="-1"></a></span>
+<span id="cb27-27"><a href="#cb27-27" tabindex="-1"></a><span class="co">    Args:</span></span>
+<span id="cb27-28"><a href="#cb27-28" tabindex="-1"></a><span class="co">        crew (str): The text entry in the crew column containing a list of crew member names</span></span>
+<span id="cb27-29"><a href="#cb27-29" tabindex="-1"></a></span>
+<span id="cb27-30"><a href="#cb27-30" tabindex="-1"></a><span class="co">    Returns:</span></span>
+<span id="cb27-31"><a href="#cb27-31" tabindex="-1"></a><span class="co">        int: The crew size</span></span>
+<span id="cb27-32"><a href="#cb27-32" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb27-33"><a href="#cb27-33" tabindex="-1"></a>    <span class="cf">if</span> crew.split() <span class="op">==</span> []:</span>
+<span id="cb27-34"><a href="#cb27-34" tabindex="-1"></a>        <span class="cf">return</span> <span class="va">None</span></span>
+<span id="cb27-35"><a href="#cb27-35" tabindex="-1"></a>    <span class="cf">else</span>:</span>
+<span id="cb27-36"><a href="#cb27-36" tabindex="-1"></a>        <span class="cf">return</span> <span class="bu">len</span>(re.split(<span class="vs">r';'</span>, crew))<span class="op">-</span><span class="dv">1</span></span>
+<span id="cb27-37"><a href="#cb27-37" tabindex="-1"></a></span>
+<span id="cb27-38"><a href="#cb27-38" tabindex="-1"></a><span class="kw">def</span> add_crew_size_column(df):</span>
+<span id="cb27-39"><a href="#cb27-39" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb27-40"><a href="#cb27-40" tabindex="-1"></a><span class="co">    Add crew_size column to the dataset containing the value of the crew size</span></span>
+<span id="cb27-41"><a href="#cb27-41" tabindex="-1"></a></span>
+<span id="cb27-42"><a href="#cb27-42" tabindex="-1"></a><span class="co">    Args:</span></span>
+<span id="cb27-43"><a href="#cb27-43" tabindex="-1"></a><span class="co">        df (pd.DataFrame): The input data frame.</span></span>
+<span id="cb27-44"><a href="#cb27-44" tabindex="-1"></a></span>
+<span id="cb27-45"><a href="#cb27-45" tabindex="-1"></a><span class="co">    Returns:</span></span>
+<span id="cb27-46"><a href="#cb27-46" tabindex="-1"></a><span class="co">        df_copy (pd.DataFrame): A copy of df with the new crew_size variable added</span></span>
+<span id="cb27-47"><a href="#cb27-47" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb27-48"><a href="#cb27-48" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">'Adding crew size variable (crew_size) to dataset'</span>)</span>
+<span id="cb27-49"><a href="#cb27-49" tabindex="-1"></a>    df_copy <span class="op">=</span> df.copy()</span>
+<span id="cb27-50"><a href="#cb27-50" tabindex="-1"></a>    df_copy[<span class="st">"crew_size"</span>] <span class="op">=</span> df_copy[<span class="st">"crew"</span>].<span class="bu">apply</span>(</span>
+<span id="cb27-51"><a href="#cb27-51" tabindex="-1"></a>        calculate_crew_size</span>
+<span id="cb27-52"><a href="#cb27-52" tabindex="-1"></a>    )</span>
+<span id="cb27-53"><a href="#cb27-53" tabindex="-1"></a>    <span class="cf">return</span> df_copy</span>
+<span id="cb27-54"><a href="#cb27-54" tabindex="-1"></a>...</span>
+<span id="cb27-55"><a href="#cb27-55" tabindex="-1"></a>    </span></code></pre>
 </div>
 <div class="section level3">
 <h3 id="writing-good-tests">Writing good tests<a class="anchor" aria-label="anchor" href="#writing-good-tests"></a>
@@ -5588,38 +5604,44 @@ <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
 <div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
 <div class="accordion-body">
 <p>We can add the following test functions to out test suite.</p>
-<div class="codewrapper sourceCode" id="cb30">
+<div class="codewrapper sourceCode" id="cb29">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb30-2"><a href="#cb30-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> (</span>
-<span id="cb30-3"><a href="#cb30-3" tabindex="-1"></a>    text_to_duration,</span>
-<span id="cb30-4"><a href="#cb30-4" tabindex="-1"></a>    calculate_crew_size</span>
-<span id="cb30-5"><a href="#cb30-5" tabindex="-1"></a>)</span>
-<span id="cb30-6"><a href="#cb30-6" tabindex="-1"></a></span>
-<span id="cb30-7"><a href="#cb30-7" tabindex="-1"></a>...</span>
-<span id="cb30-8"><a href="#cb30-8" tabindex="-1"></a></span>
-<span id="cb30-9"><a href="#cb30-9" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size():</span>
-<span id="cb30-10"><a href="#cb30-10" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb30-11"><a href="#cb30-11" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
-<span id="cb30-12"><a href="#cb30-12" tabindex="-1"></a><span class="co">    for typical crew values</span></span>
-<span id="cb30-13"><a href="#cb30-13" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb30-14"><a href="#cb30-14" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Valentina Tereshkova;"</span>)</span>
-<span id="cb30-15"><a href="#cb30-15" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">1</span></span>
-<span id="cb30-16"><a href="#cb30-16" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb30-17"><a href="#cb30-17" tabindex="-1"></a></span>
-<span id="cb30-18"><a href="#cb30-18" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Judith Resnik; Sally Ride;"</span>)</span>
-<span id="cb30-19"><a href="#cb30-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
-<span id="cb30-20"><a href="#cb30-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb30-21"><a href="#cb30-21" tabindex="-1"></a></span>
-<span id="cb30-22"><a href="#cb30-22" tabindex="-1"></a><span class="co"># Edge cases</span></span>
-<span id="cb30-23"><a href="#cb30-23" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size_edge_cases():</span>
-<span id="cb30-24"><a href="#cb30-24" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb30-25"><a href="#cb30-25" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
-<span id="cb30-26"><a href="#cb30-26" tabindex="-1"></a><span class="co">    for edge case where crew is an empty string</span></span>
-<span id="cb30-27"><a href="#cb30-27" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb30-28"><a href="#cb30-28" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">""</span>)</span>
-<span id="cb30-29"><a href="#cb30-29" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="kw">is</span> <span class="va">None</span></span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb29-2"><a href="#cb29-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> (</span>
+<span id="cb29-3"><a href="#cb29-3" tabindex="-1"></a>    text_to_duration,</span>
+<span id="cb29-4"><a href="#cb29-4" tabindex="-1"></a>    calculate_crew_size</span>
+<span id="cb29-5"><a href="#cb29-5" tabindex="-1"></a>)</span>
+<span id="cb29-6"><a href="#cb29-6" tabindex="-1"></a></span>
+<span id="cb29-7"><a href="#cb29-7" tabindex="-1"></a>...</span>
+<span id="cb29-8"><a href="#cb29-8" tabindex="-1"></a></span>
+<span id="cb29-9"><a href="#cb29-9" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size():</span>
+<span id="cb29-10"><a href="#cb29-10" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb29-11"><a href="#cb29-11" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
+<span id="cb29-12"><a href="#cb29-12" tabindex="-1"></a><span class="co">    for typical crew values</span></span>
+<span id="cb29-13"><a href="#cb29-13" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb29-14"><a href="#cb29-14" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Valentina Tereshkova;"</span>)</span>
+<span id="cb29-15"><a href="#cb29-15" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">1</span></span>
+<span id="cb29-16"><a href="#cb29-16" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb29-17"><a href="#cb29-17" tabindex="-1"></a></span>
+<span id="cb29-18"><a href="#cb29-18" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Judith Resnik; Sally Ride;"</span>)</span>
+<span id="cb29-19"><a href="#cb29-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
+<span id="cb29-20"><a href="#cb29-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb29-21"><a href="#cb29-21" tabindex="-1"></a></span>
+<span id="cb29-22"><a href="#cb29-22" tabindex="-1"></a><span class="co"># Edge cases</span></span>
+<span id="cb29-23"><a href="#cb29-23" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size_edge_cases():</span>
+<span id="cb29-24"><a href="#cb29-24" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb29-25"><a href="#cb29-25" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
+<span id="cb29-26"><a href="#cb29-26" tabindex="-1"></a><span class="co">    for edge case where crew is an empty string</span></span>
+<span id="cb29-27"><a href="#cb29-27" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb29-28"><a href="#cb29-28" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">""</span>)</span>
+<span id="cb29-29"><a href="#cb29-29" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="kw">is</span> <span class="va">None</span></span></code></pre>
+</div>
+<p>Let’s run out tests:</p>
+<div class="codewrapper sourceCode" id="cb30">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest</span></code></pre>
 </div>
 </div>
 </div>
@@ -5650,9 +5672,9 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <span id="cb31-11"><a href="#cb31-11" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
 <span id="cb31-12"><a href="#cb31-12" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span></code></pre>
 </div>
-<p>To avoid such repetitions in our test code, we can <strong>test
+<p>To avoid such repetitions in our test code, we use <strong>test
 parameterisation</strong>. This allows us to apply our test function to
-a list of input / expected output pairs without the need for repetition.
+a list of input/expected output pairs without the need for repetition.
 To parameterise the <code>test_calculate_crew_size</code> function, we
 can rewrite is as follows:</p>
 <div class="codewrapper sourceCode" id="cb32">
@@ -5942,7 +5964,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-09-code-documentation"><p>Content from <a href="09-code-documentation.html">Code documentation</a></p>
 <hr>
-<p>Last updated on 2024-09-26 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/09-code-documentation.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -6005,8 +6027,8 @@ <h3 class="callout-title">Activate your virtual environment</h3>
 <div class="codewrapper sourceCode" id="cb1">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="ex">$</span> source venv_spacewalks/bin/activate <span class="co"># Mac or Linux</span></span>
-<span id="cb1-2"><a href="#cb1-2" tabindex="-1"></a><span class="ex">$</span> source venv_spacewalks/Scripts/activate <span class="co"># Windows</span></span>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> source venv_spacewalks/bin/activate <span class="co"># Mac or Linux</span></span>
+<span id="cb1-2"><a href="#cb1-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> source venv_spacewalks/Scripts/activate <span class="co"># Windows</span></span>
 <span id="cb1-3"><a href="#cb1-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span></span></code></pre>
 </div>
 </div>
@@ -6045,10 +6067,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <hr class="half-width">
 <p>In previous episodes we encountered several different forms of
 in-code documentation aspects, including in-line comments and
-docstrings.</p>
-<p>These are an excellent way to improve the readability of our code,
-but by themselves are insufficient to ensure that our code is easy to
-use, understand and modify - this requires additional software-level
+docstrings. These are an excellent way to improve the readability of our
+code, but by themselves are insufficient to ensure that our code is easy
+to use, understand and modify - this requires additional software-level
 documentation.</p>
 <p>There are many different types of software-level documentation.</p>
 <div class="section level3">
@@ -6067,15 +6088,22 @@ <h3 id="technical-documentation">Technical documentation<a class="anchor" aria-l
 understand implementation decisions</li>
 </ul>
 </div>
+</section><section><h2 class="section-heading" id="project-level-documentation">Project-level documentation<a class="anchor" aria-label="anchor" href="#project-level-documentation"></a>
+</h2>
+<hr class="half-width">
+<p>Project-level documentation includes various information and metadata
+about software that help to discover it, explain the legal terms of
+reusing it, describe its functionality on a high level and how to
+install, run and contribute to it.</p>
 <div class="section level3">
 <h3 id="repository-metadata-files">Repository metadata files<a class="anchor" aria-label="anchor" href="#repository-metadata-files"></a>
 </h3>
-<p>In addition to software-level technical documentation, it is also
-common to see repository metadata files included in a code repository.
-Many of these files can be described as “social documentation” i.e. they
-indicate how users should “behave” in relation to our software project.
-Some common examples of repository metadata files and their role are
-tabulated below:</p>
+<p>A common way to to provide project-level documentation is to include
+various metadata files in the software repository together with code.
+Many of these files can be described as “social documentation”,
+i.e. they indicate how users should “behave” in relation to our software
+project. Some common examples of repository metadata files and their
+role are explained below:</p>
 <table class="table">
 <colgroup>
 <col width="7%">
@@ -6118,13 +6146,20 @@ <h3 id="repository-metadata-files">Repository metadata files<a class="anchor" ar
 </tr>
 </tbody>
 </table>
+<div id="just-enough-documentation" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="just-enough-documentation" class="callout-inner">
+<h3 class="callout-title">Just enough documentation</h3>
+<div class="callout-content">
+<p>For many small projects the following three pieces of project-level
+documentation may be sufficient: README, LICENSE and CITATION.</p>
+</div>
+</div>
 </div>
-</section><section><h2 class="section-heading" id="just-enough-documentation">Just enough documentation<a class="anchor" aria-label="anchor" href="#just-enough-documentation"></a>
-</h2>
-<hr class="half-width">
-<p>For many small projects the following three pieces of documentation
-may be sufficient: README, LICENSE and CITATION.</p>
 <p>Let’s look at each of these files in turn.</p>
+</div>
 <div class="section level3">
 <h3 id="readme-file">README file<a class="anchor" aria-label="anchor" href="#readme-file"></a>
 </h3>
@@ -6227,23 +6262,20 @@ <h4 id="optional">Optional<a class="anchor" aria-label="anchor" href="#optional"
 </div>
 </div>
 </div>
-<p>Let’s create a simple README for our repository.</p>
-<div class="codewrapper sourceCode" id="cb2">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="ex">$</span> cd ~/Desktop/Spacewalks</span>
-<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="ex">$</span> touch README.md</span></code></pre>
-</div>
-<p>Let’s start by adding a one-liner that explains the purpose of our
+<p>Let’s create a simple README for our repository - from VS Code or
+command line terminal create file <code>README.md</code> (in Markdown
+format) or <code>README.txt</code> (in plain text format).</p>
+<p>We can start by adding a one-liner that explains the purpose of our
 code and who it is for.</p>
 <pre class="code"><code># Spacewalks
 
 ## Overview
-Spacewalks is a python-based analysis tool for researchers to generate visualisations
+Spacewalks is a Python analysis tool for researchers to generate visualisations
 and statistical summaries of NASA's extravehicular activity datasets.</code></pre>
 <p>Now let’s add a list of Spacewalks’ key features:</p>
 <pre class="code"><code>## Features
 Key features of Spacewalks:
+
 - Generates a CSV table of summary statistics of extravehicular activity crew sizes
 - Generates a line plot to show the cumulative duration of space walks over time</code></pre>
 <p>Now let’s tell users about any pre-requisites required to run the
@@ -6266,8 +6298,11 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div id="spacewalks-readme" class="callout-inner">
 <h3 class="callout-title">Spacewalks README</h3>
 <div class="callout-content">
-<p>Extend the README for Spacewalks by adding a. Installation
-instructions b. A simple usage example</p>
+<p>Extend the README for Spacewalks by adding:</p>
+<ol style="list-style-type: decimal">
+<li>Installation instructions</li>
+<li>A simple usage example</li>
+</ol>
 </div>
 </div>
 </div>
@@ -6280,39 +6315,40 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <div class="accordion-body">
 <p>Installation instructions:</p>
 <p>NB: In the solution below the back ticks of each code block have been
-escaped to avoid rendering issues.</p>
-<pre class="text"><code># Installation instructions
+escaped to avoid rendering issues (if you are copying and pasting the
+text, make sure you unescape them).</p>
+<pre class="text"><code>## Installation instructions
 
 + Clone the Spacewalks repository to your local machine using Git.
 If you don't have Git installed, you can download it from the official Git website.
 
-\`\`\`bash
+\`\`\`
 git clone https://github.com/your-repository-url/spacewalks.git
 cd spacewalks
 \`\`\`
 
 + Install the necessary dependencies:
-\`\`\`bash
-pip install pandas==2.2.2 matplotlib==3.8.4 numpy==2.0.0 pytest==7.4.2
+\`\`\`
+python3 -m pip install pandas==2.2.2 matplotlib==3.8.4 numpy==2.0.0 pytest==7.4.2
 \`\`\`
 
 + To ensure everything is working correctly, run the tests using pytest.
 
-\`\`\`bash
-python -m pytest
+\`\`\`
+python3 -m pytest
 \`\`\`</code></pre>
 <p>Usage instructions:</p>
-<pre class="text"><code># Usage Example
+<pre class="text"><code>## Usage Example
 
 To run an analysis using the eva_data_analysis.py script from the command line terminal,
 launch the script using Python as follows:
 
-\`\`\`python
+\`\`\`
 # Usage Examples
-python eva_data_analysis.py eva-data.json eva-data.csv
+python3 eva_data_analysis.py eva-data.json eva-data.csv
 \`\`\`
 
-The first argument is path to the Json data file.
+The first argument is path to the JSON data file.
 The second argument is the path the CSV output file.</code></pre>
 </div>
 </div>
@@ -6424,155 +6460,130 @@ <h3 id="citation-file">CITATION file<a class="anchor" aria-label="anchor" href="
 </h3>
 <p>We can add a citation file to our repository to provide instructions
 on how and when to cite our code. A citation file can be a plain text
-(CITATION.txt) or a Markdown file (CITATION.md), but there are certain
-benefits to use a special file format called the Citation File Format
-(CFF) which provides a way to include richer metadata about software or
-datasets we want to cite, making it easy for both humans and machines to
-use this information.</p>
+(<code>CITATION.txt</code>) or a Markdown file
+(<code>CITATION.md</code>), but there are certain benefits to use a
+special file format called the Citation File Format (CFF) which provides
+a way to include richer metadata about software or datasets we want to
+cite, making it easy for both humans and machines to use this
+information.</p>
 <div class="section level4">
 <h4 id="why-use-cff">Why use CFF?<a class="anchor" aria-label="anchor" href="#why-use-cff"></a>
 </h4>
 <p>For developers, using a CFF file can help to automate the process of
-publishing new releases on Zenodo via GitHub. GitHub also “understands”
-CFF, and will display citation information prominently on the landing
-page of a repository that contains citation info in CFF.</p>
+publishing new releases on <a href="https://zenodo.org/" class="external-link">Zenodo</a> via
+GitHub. GitHub also “understands” CFF, and will display citation
+information prominently on the landing page of a repository that
+contains citation info in CFF.</p>
 <p>For users, having a CFF file makes it easy to cite the software or
 dataset with formatted citation information available for copy-paste and
 direct import from GitHub into reference managers like Zotero.</p>
 </div>
 <div class="section level4">
-<h4 id="creating-a-cff-file">Creating a CFF file<a class="anchor" aria-label="anchor" href="#creating-a-cff-file"></a>
+<h4 id="cff-file-format">CFF file format<a class="anchor" aria-label="anchor" href="#cff-file-format"></a>
 </h4>
 <p>A CFF file is using the <a href="https://yaml.org/" class="external-link">YAML</a>
 key-value pair format. At a minimum a CFF file must contain the title of
 the software/data, the type of asset (software or data) and at least one
 author:</p>
-<div class="codewrapper sourceCode" id="cb8">
+<div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
-<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb8-10"><a href="#cb8-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
-<span id="cb8-11"><a href="#cb8-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
+<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
+<span id="cb7-3"><a href="#cb7-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb7-4"><a href="#cb7-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
+<span id="cb7-5"><a href="#cb7-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb7-6"><a href="#cb7-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb7-7"><a href="#cb7-7" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb7-8"><a href="#cb7-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb7-9"><a href="#cb7-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb7-10"><a href="#cb7-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
+<span id="cb7-11"><a href="#cb7-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span></code></pre>
 </div>
 <p>Additional and optional metadata includes an abstract, repository URL
 and more.</p>
 </div>
 <div class="section level4">
-<h4 id="steps-to-make-your-software-citable">Steps to make your software citable<a class="anchor" aria-label="anchor" href="#steps-to-make-your-software-citable"></a>
+<h4 id="creating-cff-file-and-making-your-software-citable">Creating CFF file and making your software citable<a class="anchor" aria-label="anchor" href="#creating-cff-file-and-making-your-software-citable"></a>
 </h4>
-<p>We can create (and update) a CFF file for our software using an
-online application called <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a>.</p>
-<p>Let’s create a dummy citation file for a project called “Spacetravel”
-with Author “Max Hypothesis” by following these steps:</p>
+<p>We can create (and later update) a CFF file for our software using an
+online application called <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a> by following
+these steps:</p>
 <ol style="list-style-type: decimal">
-<li>First, head to <code>cffinit</code> online at <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a>.</li>
-<li>Then, let’s work through the metadata input form to complete the
-minimum information needed to generate a CFF. We’ll also add the
-following abstract:
-<code>"Spacetravel - a simple python script to calculate time spent in Space by individual NASA astronauts"</code>
+<li><p>Head to <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code>
+online tool</a>.</p></li>
+<li>
+<p>Then, work through the metadata input form to complete the
+minimum information needed to generate a CFF.</p>
+<p>We can use the following description as an “Abstract”: “A Python
+script to analyse NASA extravehicular activity data”</p>
+<p>Add the URL of the code repository as a “Related Resources”.</p>
+<p>Add at least two key words under the “Keywords” section.</p>
 </li>
-<li>At the end of the process, download the CFF file and inspect it. It
-should look like this:</li>
+<li><p>At the end of the process, download the CFF file and inspect it.
+It should look like this:</p></li>
 </ol>
-<div class="codewrapper sourceCode" id="cb9">
+<div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a></span>
-<span id="cb9-4"><a href="#cb9-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb9-5"><a href="#cb9-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacetravel</span></span>
-<span id="cb9-6"><a href="#cb9-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb9-7"><a href="#cb9-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb9-8"><a href="#cb9-8" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb9-9"><a href="#cb9-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb9-10"><a href="#cb9-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb9-11"><a href="#cb9-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Hypothesis</span></span>
-<span id="cb9-12"><a href="#cb9-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Max</span></span>
-<span id="cb9-13"><a href="#cb9-13" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb9-14"><a href="#cb9-14" tabindex="-1"></a>    A simple python script to calculate time spent in Space by individual NASA astronauts</span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
+<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
+<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a></span>
+<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
+<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb8-10"><a href="#cb8-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb8-11"><a href="#cb8-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
+<span id="cb8-12"><a href="#cb8-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
+<span id="cb8-13"><a href="#cb8-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
+<span id="cb8-14"><a href="#cb8-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
+<span id="cb8-15"><a href="#cb8-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
+<span id="cb8-16"><a href="#cb8-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
+<span id="cb8-17"><a href="#cb8-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-18"><a href="#cb8-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
+<span id="cb8-19"><a href="#cb8-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-20"><a href="#cb8-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
+<span id="cb8-21"><a href="#cb8-21" tabindex="-1"></a>  data</span>
+<span id="cb8-22"><a href="#cb8-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
+<span id="cb8-23"><a href="#cb8-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
+<span id="cb8-24"><a href="#cb8-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span></code></pre>
 </div>
+<p>CFF files can also be updated using the <code>cffinit</code> online
+tool by pasting the previous version of CFF file and working through the
+form to update various fields.</p>
 </div>
 <div class="section level4">
-<h4 id="updating-and-citing">Updating and citing<a class="anchor" aria-label="anchor" href="#updating-and-citing"></a>
+<h4 id="citing">Citing<a class="anchor" aria-label="anchor" href="#citing"></a>
 </h4>
-<p>CFF files can also be updated using the <code>cffinit</code> online
-tool.</p>
 <p>To cite our software (or dataset), once a CFF file has been pushed to
 our remote repository, GitHub’s “Cite this repository” button can be
 used to generate a citation in various formats (APA, BibTeX).</p>
-</div>
-<div class="section level4">
-<h4 id="tools">Tools<a class="anchor" aria-label="anchor" href="#tools"></a>
-</h4>
-<p>Command line tools are also available for creating, validating, and
-converting CFF files. Further information is available from the <a href="https://book.the-turing-way.org/communication/citable/citable-cff.html" class="external-link">Turing
-Way’s guide to software citation</a>.</p>
-<div id="spacewalks-software-citation" class="callout challenge">
+<div id="section" class="callout">
 <div class="callout-square">
-<i class="callout-icon" data-feather="zap"></i>
+<i class="callout-icon" data-feather="bell"></i>
 </div>
-<div id="spacewalks-software-citation" class="callout-inner">
-<h3 class="callout-title">Spacewalks software citation</h3>
+<div id="section" class="callout-inner">
+<h3 class="callout-title"></h3>
 <div class="callout-content">
-<p>Write a software citation file for our Spacewalks software and add it
-to the root folder of our project.</p>
-<ul>
-<li>Add the URL of the code repository as a “Related Resources”</li>
-<li>Add a one-line description of the code under the “Abstract”
-section</li>
-<li>Add at least two key words under the “Keywords” section</li>
-</ul>
-</div>
+<p>Further information is available from the <a href="https://book.the-turing-way.org/communication/citable/citable-cff.html" class="external-link">Turing
+Way’s guide to software citation</a>.</p>
 </div>
 </div>
-<div id="accordionSolution4" class="accordion challenge-accordion accordion-flush">
-<div class="accordion-item">
-<button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution4" aria-expanded="false" aria-controls="collapseSolution4">
-  <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
-</button>
-<div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
-<div class="accordion-body">
-<p>Use <a href="https://citation-file-format.github.io/cff-initializer-javascript/#/version-specific" class="external-link">cffinit</a>,
-a web application to create your citation file using a series of online
-forms.</p>
-<div class="codewrapper sourceCode" id="cb10">
-<h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a></span>
-<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
-<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb10-8"><a href="#cb10-8" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb10-9"><a href="#cb10-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb10-10"><a href="#cb10-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb10-11"><a href="#cb10-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
-<span id="cb10-12"><a href="#cb10-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
-<span id="cb10-13"><a href="#cb10-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
-<span id="cb10-14"><a href="#cb10-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
-<span id="cb10-15"><a href="#cb10-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
-<span id="cb10-16"><a href="#cb10-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
-<span id="cb10-17"><a href="#cb10-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-18"><a href="#cb10-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
-<span id="cb10-19"><a href="#cb10-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-20"><a href="#cb10-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
-<span id="cb10-21"><a href="#cb10-21" tabindex="-1"></a>  data</span>
-<span id="cb10-22"><a href="#cb10-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
-<span id="cb10-23"><a href="#cb10-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
-<span id="cb10-24"><a href="#cb10-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span></code></pre>
 </div>
+<div id="spacewalks-software-citation" class="callout discussion">
+<div class="callout-square">
+<i class="callout-icon" data-feather="message-circle"></i>
 </div>
+<div id="spacewalks-software-citation" class="callout-inner">
+<h3 class="callout-title">Spacewalks software citation</h3>
+<div class="callout-content">
+<p>Add the citation file for our Spacewalks software to the root folder
+of our repository on GitHub. You can either do it directly on GitHub or
+creating the file locally and the committing and pushing to GitHub from
+the command line.</p>
 </div>
 </div>
 </div>
@@ -6583,16 +6594,15 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 <hr class="half-width">
 <p>Once our project reaches a certain size or level of complexity we may
 want to add additional documentation such as a standalone tutorial or
-“Background” explaining our methodological choices.</p>
+“background” explaining our methodological choices.</p>
 <p>Once we move beyond using a README as our primary source of
 documentation, we need to consider how we will distribute our
-documentation to our users.</p>
-<p>Options include:</p>
+documentation to our users. Options include:</p>
 <ul>
-<li>A <code>docs/</code> folder of Markdown files.</li>
-<li>Adding a Wiki to our repository.</li>
+<li>A <code>docs/</code> folder of Markdown files</li>
+<li>Adding a Wiki to our repository</li>
 <li>Creating a set of web pages for our documentation using a static
-site generator for our documentation such as Sphinx or MkDocs</li>
+site generator for our documentation such as Sphinx or MkDocs.</li>
 </ul>
 <p>Creating a static site is a popular solution as it has the key
 benefit being able to automatically generate a reference manual from any
@@ -6601,25 +6611,19 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 id="mkdocs">MkDocs<a class="anchor" aria-label="anchor" href="#mkdocs"></a>
 </h3>
 <p>Let’s setup the static documentation site generator tool MkDocs.</p>
-<div class="codewrapper sourceCode" id="cb11">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install mkdocs</span>
-<span id="cb11-2"><a href="#cb11-2" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install <span class="st">"mkdocstrings[python]"</span></span>
-<span id="cb11-3"><a href="#cb11-3" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install mkdocs-material</span></code></pre>
-</div>
-<p>Let’s check that MkDocs has been setup correctly:</p>
-<div class="codewrapper sourceCode" id="cb12">
+<div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip list</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install mkdocs</span>
+<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install <span class="st">"mkdocstrings[python]"</span></span>
+<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install mkdocs-material</span></code></pre>
 </div>
-<p>Let’s creates a new MkDocs project in the current directory</p>
-<div class="codewrapper sourceCode" id="cb13">
+<p>Let’s creates a new MkDocs project in the current directory:</p>
+<div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="co"># In ~/Desktop/spacewalks</span></span>
-<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a><span class="ex">mkdocs</span> new .    </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="co"># In ~/Desktop/spacewalks</span></span>
+<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="ex">mkdocs</span> new .    </span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6629,72 +6633,76 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 <p>This command creates a new MkDocs project in the current directory
 with a <code>docs</code> folder containing an <code>index.md</code> file
-and a <code>mkdocs.yml</code> configuration file.</p>
-<p>Now, let’s fill in the configuration file for our project.</p>
-<div class="codewrapper sourceCode" id="cb15">
+and a <code>mkdocs.yml</code> configuration file in the root of our
+project.</p>
+<p>Now, let’s fill in the <code>mkdocs.yml</code> configuration file for
+our project.</p>
+<div class="codewrapper sourceCode" id="cb12">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a></span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
-<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
-<span id="cb15-5"><a href="#cb15-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
-<span id="cb15-6"><a href="#cb15-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
-<span id="cb15-7"><a href="#cb15-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
-<span id="cb15-8"><a href="#cb15-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
-<span id="cb15-9"><a href="#cb15-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
-<span id="cb15-10"><a href="#cb15-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
-<span id="cb15-11"><a href="#cb15-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span></code></pre>
-</div>
-<p>Note font-false is for GDPR compliance.</p>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
+<span id="cb12-2"><a href="#cb12-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb12-3"><a href="#cb12-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
+<span id="cb12-4"><a href="#cb12-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
+<span id="cb12-5"><a href="#cb12-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb12-6"><a href="#cb12-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
+<span id="cb12-7"><a href="#cb12-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
+<span id="cb12-8"><a href="#cb12-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
+<span id="cb12-9"><a href="#cb12-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
+<span id="cb12-10"><a href="#cb12-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
+<span id="cb12-11"><a href="#cb12-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span></code></pre>
+</div>
+<p>Note <code>font: false</code> variable is for GDPR compliance;
+<code>use_directory_url: false</code> variable tells MKDocs tools how to
+handle URLs for documentation that is served as a website (we will cover
+this in a moment).</p>
 <p>Let’s add support for <code>mkdocstrings</code> - this will allow us
 to automatically our docstrings into our documentation using a simple
 tag.</p>
-<div class="codewrapper sourceCode" id="cb16">
+<div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
-<span id="cb16-2"><a href="#cb16-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
-<span id="cb16-3"><a href="#cb16-3" tabindex="-1"></a></span>
-<span id="cb16-4"><a href="#cb16-4" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
-<span id="cb16-5"><a href="#cb16-5" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
-<span id="cb16-6"><a href="#cb16-6" tabindex="-1"></a></span>
-<span id="cb16-7"><a href="#cb16-7" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
-<span id="cb16-8"><a href="#cb16-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
-<span id="cb16-9"><a href="#cb16-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
-<span id="cb16-10"><a href="#cb16-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
-<span id="cb16-11"><a href="#cb16-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
-<span id="cb16-12"><a href="#cb16-12" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span>
-<span id="cb16-13"><a href="#cb16-13" tabindex="-1"></a></span>
-<span id="cb16-14"><a href="#cb16-14" tabindex="-1"></a><span class="fu">plugins</span><span class="kw">:</span></span>
-<span id="cb16-15"><a href="#cb16-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> mkdocstrings</span></span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
+<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
+<span id="cb13-4"><a href="#cb13-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
+<span id="cb13-5"><a href="#cb13-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb13-6"><a href="#cb13-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
+<span id="cb13-7"><a href="#cb13-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
+<span id="cb13-8"><a href="#cb13-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
+<span id="cb13-9"><a href="#cb13-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
+<span id="cb13-10"><a href="#cb13-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
+<span id="cb13-11"><a href="#cb13-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span>
+<span id="cb13-12"><a href="#cb13-12" tabindex="-1"></a></span>
+<span id="cb13-13"><a href="#cb13-13" tabindex="-1"></a><span class="fu">plugins</span><span class="kw">:</span></span>
+<span id="cb13-14"><a href="#cb13-14" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> mkdocstrings</span></span></code></pre>
 </div>
 <p>Let’s populate our <code>docs/</code> folder to match our
 configuration file.</p>
-<div class="codewrapper sourceCode" id="cb17">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="fu">touch</span> docs/tutorials.md</span>
-<span id="cb17-2"><a href="#cb17-2" tabindex="-1"></a><span class="fu">touch</span> docs/how-to-guides.md</span>
-<span id="cb17-3"><a href="#cb17-3" tabindex="-1"></a><span class="fu">touch</span> docs/reference.md</span>
-<span id="cb17-4"><a href="#cb17-4" tabindex="-1"></a><span class="fu">touch</span> docs/explanation.md</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/tutorials.md</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/how-to-guides.md</span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/reference.md</span>
+<span id="cb14-4"><a href="#cb14-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/explanation.md</span></code></pre>
 </div>
-<p>Let’s populate our reference file with some preamble to include
-before the reference manual that will be generated from the docstrings
-we created.</p>
-<div class="codewrapper sourceCode" id="cb18">
+<p>Let’s populate our reference file <code>reference.md</code> with some
+preamble to include before the reference manual that will be generated
+from the docstrings we created.</p>
+<div class="codewrapper sourceCode" id="cb15">
 <h3 class="code-label">MARKDOWN<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode markdown" tabindex="0"><code class="sourceCode markdown"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a>This file documents the key functions in the Spacewalks tool.</span>
-<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a>It is provided as a reference manual.</span>
-<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a></span>
-<span id="cb18-4"><a href="#cb18-4" tabindex="-1"></a>::: eva_data_analysis</span></code></pre>
+<pre class="sourceCode markdown" tabindex="0"><code class="sourceCode markdown"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a>This file documents the key functions in the Spacewalks tool.</span>
+<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a>It is provided as a reference manual.</span>
+<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a></span>
+<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a>::: eva_data_analysis</span></code></pre>
 </div>
 <p>Finally, let’s build our documentation.</p>
-<div class="codewrapper sourceCode" id="cb19">
+<div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="ex">mkdocs</span> build</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs build</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6707,25 +6715,43 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 INFO    -  Documentation built in 0.31 seconds</code></pre>
 </div>
 <p>Once the build step is completed, our documentation site is saved to
-a <code>site</code> folder in the root of our project folder.</p>
-<p>These files will be distributed with our code. We can either direct
-users to read these files locally on their own device using their
-browser, or we can choose to host our documentation as a website that
-our uses can navigate to.</p>
+a <code>site</code> folder in the root of our project folder. These
+files will be distributed with our code. We can either direct users to
+read these files locally on their own device using their browser, or we
+can choose to host our documentation as a website that our uses can
+navigate to.</p>
 <p>Note that we used the setting <code>use_directory_urls: false</code>
 in the <code>mkdocs.yml</code> file. This setting ensures that the
 documentation site is generated with URLs that are easy to navigate
 locally on a user’s device.</p>
-<p>Finally let us commit our documentation to the main branch of our git
-repository and push the changes to GitHub</p>
-<div class="codewrapper sourceCode" id="cb21">
+<div id="explore-your-documentation" class="callout discussion">
+<div class="callout-square">
+<i class="callout-icon" data-feather="message-circle"></i>
+</div>
+<div id="explore-your-documentation" class="callout-inner">
+<h3 class="callout-title">Explore your documentation</h3>
+<div class="callout-content">
+<p>Explore documentation in <code>site/</code> folder built with MkDocs
+for your project, starting from <code>index.html</code> file.</p>
+<p>For example, check <code>site/reference.html</code> to see how
+docstrings from your functions are provided here as a reference
+manual.</p>
+</div>
+</div>
+</div>
+<p>Finally, let us commit our documentation to the main branch of our
+git repository and push the changes to GitHub.</p>
+<div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="fu">git</span> add mkdocs.yml </span>
-<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="fu">git</span> add docs/</span>
-<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a><span class="fu">git</span> add site/</span>
-<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
-<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add mkdocs.yml </span>
+<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add docs/</span>
+<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add site/</span>
+<span id="cb18-4"><a href="#cb18-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
+<span id="cb18-5"><a href="#cb18-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip freeze <span class="op">&gt;</span> requirements.txt</span>
+<span id="cb18-6"><a href="#cb18-6" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add requirements.txt </span>
+<span id="cb18-7"><a href="#cb18-7" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Added mkdocs plugin"</span></span>
+<span id="cb18-8"><a href="#cb18-8" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 <div id="hosting-documentation" class="callout">
 <div class="callout-square">
@@ -6734,9 +6760,8 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div id="hosting-documentation" class="callout-inner">
 <h3 class="callout-title">Hosting documentation</h3>
 <div class="callout-content">
-<p>In the previous section, we saw how Mkdocs documentation can be
-distributed with our repository and viewed “offline” using a
-browser.</p>
+<p>We saw how MkDocs documentation can be distributed with our
+repository and viewed “offline” using a browser.</p>
 <p>We can also make our documentation available as a live website by
 deploying our documentation to a hosting service.</p>
 <div id="accordionSpoiler1" class="accordion spoiler-accordion accordion-flush">
@@ -6755,10 +6780,11 @@ <h3 id="github-pages">GitHub Pages<a class="anchor" aria-label="anchor" href="#g
 <p>There are two types of GitHub Pages: project pages and
 user/organization Pages. While similar, they have different deployment
 workflows, and we will only discuss project pages here. For information
-about deploying to user/organisational pages, see [MkDocs Deployment
-pages][mkdocs-deploy].</p>
-<p>Project Pages deploy site files to a branch within the project
-repository (default is gh-pages). To deploy our documentation:</p>
+about deploying to user/organisational pages, see <a href="https://www.mkdocs.org/user-guide/deploying-your-docs/" class="external-link">MkDocs
+Deployment pages</a>.</p>
+<p>Project Pages deploy site files to a branch (by default the
+<code>gh-pages</code> branch, but it can be any other branch) within the
+project repository. To deploy our documentation:</p>
 <blockquote>
 <p><strong>Warning!</strong> Before we proceed to the next step, we MUST
 ensure that there are no uncommitted changes or untracked files in our
@@ -6768,28 +6794,29 @@ <h3 id="github-pages">GitHub Pages<a class="anchor" aria-label="anchor" href="#g
 </blockquote>
 <ol style="list-style-type: decimal">
 <li>(If not done already), let us commit our documentation to the main
-branch of our git repository and push the changes to GitHub</li>
+branch of our git repository and push the changes to GitHub.</li>
 </ol>
-<div class="codewrapper sourceCode" id="cb22">
+<div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="fu">git</span> add mkdocs.yml </span>
-<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a><span class="fu">git</span> add docs/</span>
-<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a><span class="fu">git</span> add site/</span>
-<span id="cb22-4"><a href="#cb22-4" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
-<span id="cb22-5"><a href="#cb22-5" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add mkdocs.yml </span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add docs/</span>
+<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add site/</span>
+<span id="cb19-4"><a href="#cb19-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
+<span id="cb19-5"><a href="#cb19-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 <ol start="2" style="list-style-type: decimal">
 <li>Once we are on the main branch and all our changes are up to date,
-run the following command to deploy our documentation to GitHub.</li>
+run the following command from the command line termindal to deploy our
+documentation to GitHub.</li>
 </ol>
-<div class="codewrapper sourceCode" id="cb23">
+<div class="codewrapper sourceCode" id="cb20">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="co"># Important: </span></span>
-<span id="cb23-2"><a href="#cb23-2" tabindex="-1"></a><span class="co"># - This command will push the documentation to the gh-pages branch of your repository</span></span>
-<span id="cb23-3"><a href="#cb23-3" tabindex="-1"></a><span class="co"># - It will ALSO include uncommitted changes and untracked files (read the warning above!!) &lt;- VERY IMPORTANT!!</span></span>
-<span id="cb23-4"><a href="#cb23-4" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="co"># Important: </span></span>
+<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="co"># - This command will push the documentation to the gh-pages branch of your repository</span></span>
+<span id="cb20-3"><a href="#cb20-3" tabindex="-1"></a><span class="co"># - It will ALSO include uncommitted changes and untracked files (read the warning above!!) &lt;- VERY IMPORTANT!!</span></span>
+<span id="cb20-4"><a href="#cb20-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs gh-deploy</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6819,13 +6846,14 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 INFO    -  Your documentation should shortly be available at: https://kkh451.github.io/spacewalks/</code></pre>
 </div>
 <p>This command will build our documentation with MkDocs, then commit
-and push the files to the gh-pages branch using the GitHub ghp-import
-tool which is installed as a dependency of MkDocs.</p>
+and push the files to the <code>gh-pages</code> branch using the GitHub
+<code>ghp-import</code> tool which is installed as a dependency of
+MkDocs.</p>
 <p>For more options, use:</p>
-<div class="codewrapper sourceCode" id="cb25">
+<div class="codewrapper sourceCode" id="cb22">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy <span class="at">--help</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy <span class="at">--help</span></span></code></pre>
 </div>
 <p>Notice that the deploy command did not allow us to preview the site
 before it was pushed to GitHub; so, it is a good idea to check changes
@@ -6835,8 +6863,8 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 id="other-options">Other options<a class="anchor" aria-label="anchor" href="#other-options"></a>
 </h3>
 <p>You can find out about other deployment options including free
-documentation hosting service ReadTheDocs on the [MkDocs deployment
-pages][mkdocs-deploy].</p>
+documentation hosting service ReadTheDocs on the <a href="https://www.mkdocs.org/user-guide/deploying-your-docs/" class="external-link">MkDocs
+deployment pages</a>.</p>
 </div>
 </div>
 </div>
@@ -6850,8 +6878,8 @@ <h3 id="other-options">Other options<a class="anchor" aria-label="anchor" href="
 </h2>
 <hr class="half-width">
 <p>Once we start to consider other forms of documentation beyond the
-README, we can also increase the re-usability of our code by ensuring
-that the content and style of our documentation matches its purpose.</p>
+README, we can also increase reusability of our code by ensuring that
+the content and style of our documentation matches its purpose.</p>
 <p>Documentation guides such as <a href="https://www.writethedocs.org/" class="external-link">Write the Docs</a>, <a href="https://www.thegooddocsproject.dev/" class="external-link">The Good Docs Project</a> and
 the <a href="https://diataxis.fr/" class="external-link">Diataxis framework</a> provide a
 range of resources including documentation templates to help to help us
@@ -6867,8 +6895,9 @@ <h3 class="callout-title">Spacewalks how-to guide</h3>
 <li><p>Review the Diataxis guidance page on writing a How-to guide.
 Identify three features of an effective how-to guide.</p></li>
 <li><p>Following the Diataxis guidelines, add a how-to guide to the
-<code>docs</code> folder that show users how to change the destination
-filename for the output dataset generated by Spacewalks.</p></li>
+<code>docs/how-to-guides.md</code> file in your documentation folder to
+show users how to change the destination filename for the output CSV
+dataset generated by the Spacewalks software.</p></li>
 </ol>
 <div id="accordionSpoiler2" class="accordion spoiler-accordion accordion-flush">
 <div class="accordion-item">
@@ -6884,21 +6913,30 @@ <h3 class="accordion-header" id="headingSpoiler2">  <div class="note-square"><i
 <li>use appropriate language e.g. conditional imperatives</li>
 <li>have an informative title</li>
 </ul>
-<p>An example how-to guide:</p>
+<p>An example how-to guide for our project to the file
+<code>docs/how-to-guides.md</code>:</p>
 <pre><code># How to change the file path of Spacewalk's output dataset
 
 This guide shows you how to set the file path for Spacewalk's output
 data set to a location of your choice.
 
-By default, the cleaned data set generated by Spacewalk is saved to the current
-working directory with file name `eva-data.csv`.
+By default, the cleaned data set in CSV format, generated by the Spacewalk software, is saved to the `results/`
+folder within the working directory with file name `eva-data.csv`.
 
 If you would like to modify the name or location of the output dataset, set the
 second command line argument to your chosen file path.
+For example, if you want to save the output data set to the subfolder `data/clean/` you can
+invoke the script as:
 
-`python eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv`
+`(venv_spacewalks) $ python3 eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv`
 
-The specified destination folder must exist before running spacewalks analysis script.</code></pre>
+The specified destination folder `data/clean/` must exist before running spacewalks analysis script.</code></pre>
+<p>Remember to rebuild your documentation:</p>
+<div class="codewrapper sourceCode" id="cb24">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs build</span></code></pre>
+</div>
 </div>
 </div>
 </div>
@@ -6932,8 +6970,9 @@ <h3 class="accordion-header" id="headingSpoiler3">  <div class="note-square"><i
 <h4 id="introduction">Introduction<a class="anchor" aria-label="anchor" href="#introduction"></a>
 </h4>
 <p>In this tutorial, we will learn how to change the file path for the
-output dataset generated by Spacewalk. By the end of this tutorial, you
-will be able to specify a custom file path for the cleaned dataset.</p>
+output dataset generated by the Spacewalk software. By the end of this
+tutorial, you will be able to specify a custom file path for the cleaned
+dataset.</p>
 </div>
 <div class="section level4">
 <h4 id="prerequisites">Prerequisites<a class="anchor" aria-label="anchor" href="#prerequisites"></a>
@@ -6948,35 +6987,36 @@ <h4 id="prerequisites">Prerequisites<a class="anchor" aria-label="anchor" href="
 <div class="section level4">
 <h4 id="prepare-the-destination-directory">Prepare the destination directory<a class="anchor" aria-label="anchor" href="#prepare-the-destination-directory"></a>
 </h4>
-<p>First, let us decide where we want to save the cleaned dataset. and
+<p>First, let us decide where we want to save the cleaned dataset and
 make sure the directory exists.</p>
-<p>For this tutorial, we will use data/clean as the destination
-folder.</p>
-<p>Let’s create the directory if it does not exist:</p>
-<div class="codewrapper sourceCode" id="cb27">
+<p>For this tutorial, we will use <code>data/clean/</code> as the
+destination folder.</p>
+<p>Let’s create the directory if it does not exist - e.g. from the
+command line do:</p>
+<div class="codewrapper sourceCode" id="cb25">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="fu">mkdir</span> <span class="at">-p</span> data/clean</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir <span class="at">-p</span> data/clean</span></code></pre>
 </div>
 </div>
 <div class="section level4">
-<h4 id="run-the-analysis-script-with-custom-path">Run the analysis script with custom path<a class="anchor" aria-label="anchor" href="#run-the-analysis-script-with-custom-path"></a>
+<h4 id="run-the-analysis-script-with-a-custom-path">Run the analysis script with a custom path<a class="anchor" aria-label="anchor" href="#run-the-analysis-script-with-a-custom-path"></a>
 </h4>
 <p>Next, execute the Spacewalk script and specify the custom file path
 for the output dataset:</p>
-<div class="codewrapper sourceCode" id="cb28">
+<div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb28-1"><a href="#cb28-1" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py <span class="op">&lt;</span>input-file<span class="op">&gt;</span> <span class="op">&lt;</span>output-file<span class="op">&gt;</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py <span class="op">&lt;</span>input-file<span class="op">&gt;</span> <span class="op">&lt;</span>output-file<span class="op">&gt;</span></span></code></pre>
 </div>
-<p>Replace <input-file> with your input dataset (eva-data.json) and
-<output-file> with your desired output path
-(data/clean/eva-data-clean.csv).</output-file></input-file></p>
+<p>Replace <input-file> with your input dataset
+(<code>data/eva-data.json</code>) and <output-file> with your desired
+output path (<code>data/clean/eva-data-clean.csv</code>).</output-file></input-file></p>
 <p>Here is the complete command:</p>
-<div class="codewrapper sourceCode" id="cb29">
+<div class="codewrapper sourceCode" id="cb27">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py data/eva-data.json data/clean/eva-data-clean.csv</span></code></pre>
 </div>
 <p>Notice how the output to the command line clearly indicates that we
 are using a custom output file path.</p>
@@ -6984,48 +7024,49 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="output" tabindex="0"><code>Using custom input and output filenames
-Reading JSON file eva-data.json
+Reading JSON file data/eva-data.json
 Saving to CSV file data/clean/eva-data-clean.csv
 Adding crew size variable (crew_size) to dataset
 Saving to CSV file data/clean/eva-data-clean.csv
-Plotting cumulative spacewalk duration and saving to ./cumulative_eva_graph.png</code></pre>
+Plotting cumulative spacewalk duration and saving to results/cumulative_eva_graph.png</code></pre>
 </div>
-<p>After running the script, let us check the data/clean directory to
-ensure the cleaned dataset has been saved correctly.</p>
-<div class="codewrapper sourceCode" id="cb31">
+<p>After running the script, let us check the <code>data/clean</code>
+directory to ensure the cleaned dataset has been saved correctly.</p>
+<div class="codewrapper sourceCode" id="cb29">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" tabindex="-1"></a><span class="fu">ls</span> data/clean</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> ls data/clean</span></code></pre>
 </div>
-<p>You should see eva-data-clean.csv listed in the data/clean folder</p>
+<p>You should see <code>eva-data-clean.csv</code> file listed in the
+<code>data/clean</code> folder.</p>
 </div>
 <div class="section level4">
 <h4 id="exercise-custom-output-path">Exercise: custom output path<a class="anchor" aria-label="anchor" href="#exercise-custom-output-path"></a>
 </h4>
 <ul>
-<li>Create a new directory named output/data in your working
-directory.</li>
+<li>Create a new directory named <code>output/data</code> in your
+working directory.</li>
 <li>Run the Spacewalk script to save the cleaned dataset in the newly
-created output/data directory with the filename
-cleaned-eva-data.csv.</li>
+created <code>output/data</code> directory with the filename
+<code>cleaned-eva-data.csv</code>.</li>
 <li>Verify that the dataset has been saved correctly.</li>
 </ul>
 <div class="section level5">
 <h5 id="solution-1">Solution<a class="anchor" aria-label="anchor" href="#solution-1"></a>
 </h5>
-<div class="codewrapper sourceCode" id="cb32">
+<div class="codewrapper sourceCode" id="cb30">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb32-1"><a href="#cb32-1" tabindex="-1"></a><span class="co"># Create the directory:</span></span>
-<span id="cb32-2"><a href="#cb32-2" tabindex="-1"></a><span class="fu">mkdir</span> <span class="at">-p</span> output/data</span>
-<span id="cb32-3"><a href="#cb32-3" tabindex="-1"></a></span>
-<span id="cb32-4"><a href="#cb32-4" tabindex="-1"></a><span class="co"># Run the script:</span></span>
-<span id="cb32-5"><a href="#cb32-5" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py eva-data.json output/data/cleaned-eva-data.csv</span>
-<span id="cb32-6"><a href="#cb32-6" tabindex="-1"></a></span>
-<span id="cb32-7"><a href="#cb32-7" tabindex="-1"></a><span class="co"># Verify the output:</span></span>
-<span id="cb32-8"><a href="#cb32-8" tabindex="-1"></a><span class="fu">ls</span> output/data</span>
-<span id="cb32-9"><a href="#cb32-9" tabindex="-1"></a></span>
-<span id="cb32-10"><a href="#cb32-10" tabindex="-1"></a><span class="co"># You should see cleaned-eva-data.csv listed</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="co"># Create the directory:</span></span>
+<span id="cb30-2"><a href="#cb30-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir <span class="at">-p</span> output/data</span>
+<span id="cb30-3"><a href="#cb30-3" tabindex="-1"></a></span>
+<span id="cb30-4"><a href="#cb30-4" tabindex="-1"></a><span class="co"># Run the script:</span></span>
+<span id="cb30-5"><a href="#cb30-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py data/eva-data.json output/data/cleaned-eva-data.csv</span>
+<span id="cb30-6"><a href="#cb30-6" tabindex="-1"></a></span>
+<span id="cb30-7"><a href="#cb30-7" tabindex="-1"></a><span class="co"># Verify the output:</span></span>
+<span id="cb30-8"><a href="#cb30-8" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> ls output/data</span>
+<span id="cb30-9"><a href="#cb30-9" tabindex="-1"></a></span>
+<span id="cb30-10"><a href="#cb30-10" tabindex="-1"></a><span class="co"># You should see cleaned-eva-data.csv listed</span></span></code></pre>
 </div>
 <p>Congratulations! You have successfully changed the file path for
 Spacewalks output dataset and completed an exercise to practice the
@@ -7086,24 +7127,14 @@ <h4 id="language">Language<a class="anchor" aria-label="anchor" href="#language"
 </div>
 </div>
 </div>
-<div id="commit-and-push-your-changes" class="callout">
-<div class="callout-square">
-<i class="callout-icon" data-feather="bell"></i>
-</div>
-<div id="commit-and-push-your-changes" class="callout-inner">
-<h3 class="callout-title">Commit and push your changes</h3>
-<div class="callout-content">
-<p>Do not forget to commit any uncommited changes you may have and then
+<p>Do not forget to commit any uncommitted changes you may have and then
 push your work to GitHub.</p>
-<div class="codewrapper sourceCode" id="cb33">
+<div class="codewrapper sourceCode" id="cb31">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb33-1"><a href="#cb33-1" tabindex="-1"></a><span class="fu">git</span> add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
-<span id="cb33-2"><a href="#cb33-2" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
-<span id="cb33-3"><a href="#cb33-3" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
-</div>
-</div>
-</div>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
+<span id="cb31-2"><a href="#cb31-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
+<span id="cb31-3"><a href="#cb31-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a>
 </h2>
@@ -7161,9 +7192,9 @@ <h3 class="callout-title">Key Points</h3>
 Place links that you need to refer to multiple times across pages here. Delete
 any links that you are not going to use.
  -->
-</section></section><section id="aio-10-open-collaboration"><p>Content from <a href="10-open-collaboration.html">Open collaboration on code</a></p>
+</section></section><section id="aio-10-open-collaboration"><p>Content from <a href="10-open-collaboration.html">Open code &amp; collaboration</a></p>
 <hr>
-<p>Last updated on 2024-09-24 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/10-open-collaboration.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -7205,9 +7236,16 @@ <h3 class="card-title">Objectives</h3>
 </div>
 </div>
 </div>
-<p>In addition to adding a license and other metadata to our code
-(covered in previous episode) there are several other important steps to
-consider before sharing the code publicly.</p>
+<p>Sharing code openly promotes collaboration, transparency, and
+innovation by allowing others to review, use, and improve the code. It
+fosters knowledge exchange, accelerates scientific progress, and
+enhances the reproducibility of research. Additionally, open sharing
+encourages community contributions and can lead to better-maintained,
+more reliable software.</p>
+<p>Adding a <a href="licensing.html">license</a> and other metadata to
+our code (covered in the previous episode) are the first steps towards
+sharing the code publicly. There are several other important steps to
+consider which we will cover here.</p>
 <div id="activate-your-virtual-environment" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
@@ -7233,86 +7271,87 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="section level3">
 <h3 id="making-the-code-public">Making the code public<a class="anchor" aria-label="anchor" href="#making-the-code-public"></a>
 </h3>
-<p>By default repositories created on Github are private and only their
-creator can see them. If we’re going to be adding an open source license
-to our repository we probably want to make sure people can actually
-access it too!</p>
-<p>Go to the Github webpage of your repository
-(<code>https://github.com/&lt;yourusername&gt;/&lt;yourrepsoitoryname&gt;</code>)
-and click on the Settings link near the top right corner. Then scroll
-down to the bottom of the page and the “Danger Zone” settings. Click on
-“Change Visibility” and you should see a message saying “Change to
-public”, if it says “Change to private” then the repository is already
-public. You’ll then be asked to confirm that you want to make the
-repository public and agree to the warning that the code will now be
-publicly visible. As a security measure you’ll then have to put in your
-Github password.</p>
+<p>By default repositories created on GitHub are private and only their
+creator can see them. Since we added an open source license to our
+repository we probably want to make sure people can actually access
+it.</p>
+<p>To make your repository public, if it is not already, go to your
+repository on GitHub and click on the <code>Settings</code> link near
+the top right corner. Then scroll down to the bottom of the page and the
+“Danger Zone” settings. Click on “Change Visibility” and you should see
+a message saying “Change to public”. If it says “Change to private” then
+the repository is already public. You will then be asked to confirm that
+you indeed want to make the repository public and agree to the warning
+that the code will now be publicly visible. As a security measure, you
+will then have to put in your GitHub password.</p>
 </div>
 <div class="section level3">
 <h3 id="transferring-to-an-organisation">Transferring to an organisation<a class="anchor" aria-label="anchor" href="#transferring-to-an-organisation"></a>
 </h3>
-<p>Currently our repository is under the Github “namespace” of our
-individual user. This is ok for individual projects where we are the
-sole or at least main author, but for bigger and more complex projects
-it is common to use a Github organisation named after our project. If we
-are a member of an organisation and have the appropriate permissions
-then we can transfer a repository from our personal namespace to the
-organisation’s. This can be done with another option in the “Danger
-Zone” settings, the “Transfer ownership” button. Pressing this will then
-prompt us as to which organisation we want to transfer the repository
-to.</p>
+<p>Currently our repository is under the GitHub “namespace” of our
+individual user. This is OK for individual projects where we are the
+sole or at least the main code author, but for bigger and more complex
+projects it is common to use a GitHub organisation named after our
+project. If we are a member of an organisation and have the appropriate
+permissions then we can transfer a repository from our personal
+namespace to the organisation’s. This can be done with another option in
+the “Danger Zone” settings, the “Transfer ownership” button. Pressing
+this will then prompt us as to which organisation we want to transfer
+the repository to.</p>
 </div>
 <div class="section level3">
-<h3 id="archiving-to-zenodo-and-obtaining-a-doi">Archiving to Zenodo and obtaining a DOI<a class="anchor" aria-label="anchor" href="#archiving-to-zenodo-and-obtaining-a-doi"></a>
+<h3 id="archiving-code-to-zenodo-and-obtaining-a-doi">Archiving code to Zenodo and obtaining a DOI<a class="anchor" aria-label="anchor" href="#archiving-code-to-zenodo-and-obtaining-a-doi"></a>
 </h3>
-<p>Zenodo is a data archive run by CERN. Anybody can upload datasets up
-to 50GB to it and receive a Digital Object Identifier (DOI). Zenodo’s
-definition of a dataset is quite broad and can include code. This gives
-us a way to obtain a DOI for our code. We can archive our Github
-repository to Zenodo by doing the following:</p>
+<p><a href="https://zenodo.org/" class="external-link">Zenodo</a> is a data archive run by
+CERN. Anybody can upload datasets up to 50GB to it and receive a Digital
+Object Identifier (DOI). Zenodo’s definition of a dataset is quite broad
+and can include code - which gives us a way to obtain a DOI for our
+software. We can archive our GitHub repository to Zenodo by doing the
+following:</p>
 <ol style="list-style-type: decimal">
 <li>Go to the <a href="https://zenodo.org/login" class="external-link">Zenodo Login page</a>
-and choose to login with Github.</li>
-<li>Authorise Zenodo to connect to Github.</li>
-<li>Go to the <a href="https://zenodo.org/account/settings/github/" class="external-link">Github page</a> in
+and choose to login with GitHub.</li>
+<li>Authorise Zenodo to connect to GitHub.</li>
+<li>Go to the <a href="https://zenodo.org/account/settings/github/" class="external-link">GitHub page</a> in
 your Zenodo account. This can be found in the pull down menu with your
 user name in the top right corner of the screen.</li>
-<li>You’ll now have a list of all of your Github repositories. Next to
+<li>You’ll now have a list of all of your GitHub repositories. Next to
 each will be an “On” button. If you have created a new repository you
 might need to press the “Sync” button to update the list of repositories
 Zenodo knows about.</li>
 <li>Press the “On” button for the repository you want to archive. If
-this was successful you’ll be told to refresh the page.</li>
-<li>The repository should now appear in the list of Enabled repositories
-at the top of the screen. But it doesn’t yet have a DOI. To get one we
-have to make a release on Github. Click on the repository and then press
-the green button to create a release. This will take you to Github’s
-release page where you’ll be asked to give a title and description of
-the release. You will also have to create a tag, this is a way of having
-a friendly name for the version of some code in Git instead of using a
-long hash code. Often we’ll create a sequential version number for each
-release of the software and have the tag name match this, for example
-v1.0 or just 1.0.</li>
+this was successful you will be told to refresh the page.</li>
+<li>The repository should now appear in the list of “Enabled”
+repositories at the top of the screen, but it does not yet have a DOI.
+To get one we have to make a “release” on GitHub. Click on the
+repository and then press the green button to create a release. This
+will take you to GitHub’s release page where you will be asked to give a
+title and description of the release. You will also have to create a
+“tag” for your release - a way of having a friendly name for the version
+of some code in Git instead of using a long hash code. Often we will
+create a sequential version number for each release of the software and
+have the tag name match this, for example v1.0 or just 1.0.</li>
 <li>If we now refresh the Zenodo page for this repository we will see
 that it has been assigned a DOI.</li>
 </ol>
-<p>The DOI doesn’t just link to Github, Zenodo will have taken a copy of
-our repository at the point where we tagged the release. This means that
-even if we delete it from Github or even if Github were ever to go away
-or remove it, they’ll still be a copy on Zenodo. Zenodo will allow
-people to download the entire repository as a single Zip file.</p>
+<p>The DOI does not just link to GitHub, Zenodo will have taken a copy
+(a snapshot) of our repository at the point where we tagged the release.
+This means that even if we delete it from GitHub or even if GitHub were
+ever to go away or remove it, there will still be a copy on Zenodo.
+Zenodo will allow people to download the entire repository as a single
+<code>zip</code> file.</p>
 <p>Zenodo will have actually created two DOIs for you. One represents
 the latest version of the software and will always represent the latest
-if you make more releases. The other is specfic to the release you made
+if you make more releases. The other is specific to the release you made
 and will always point to that version. We can see both of these by
-clicking on the DOI link in the Zenodo page for the repository. One of
-the things which is displayed on this page is a badge image that you can
-copy the link for and add to the README file in your Git repository so
-that people can find the Zenodo version of the repository. If you click
-on the DOI image in the Details section of the Zenodo page then you will
-be shown instructions for obtaining a link to the DOI badge in various
-formats including Markdown. Here is the badge for this repository and
-the corresponding Markdown:</p>
+clicking on the DOI link in the Zenodo page for the repository.</p>
+<p>One of the things which is displayed on this page is a badge image
+that you can copy the link for and add to the README file in your GitHub
+repository so that people can find the Zenodo version of the repository.
+If you click on the DOI image in the Details section of the Zenodo page
+then you will be shown instructions for obtaining a link to the DOI
+badge in various formats including Markdown. Here is the badge for this
+repository and the corresponding Markdown:</p>
 <p><a href="https://doi.org/10.5281/zenodo.11869450" class="external-link"><img src="https://zenodo.org/badge/DOI/10.5281/zenodo.11869450.svg" alt="DOI" class="figure"></a></p>
 <pre class="text"><code>[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.11869450.svg)](https://doi.org/10.5281/zenodo.11869450)</code></pre>
 <div id="archive-your-repository-to-zenodo" class="callout discussion">
@@ -7322,8 +7361,12 @@ <h3 id="archiving-to-zenodo-and-obtaining-a-doi">Archiving to Zenodo and obtaini
 <div id="archive-your-repository-to-zenodo" class="callout-inner">
 <h3 class="callout-title">Archive your repository to Zenodo</h3>
 <div class="callout-content">
+<p>Note: for this exercise, you should use the <a href="https://sandbox.zenodo.org/" class="external-link">Sandbox Zenodo</a> (which is a
+version of Zenodo for testing and playing with before minting a real
+DOI) to avoid polluting the DOI space with test repositories we use for
+this course.</p>
 <ul>
-<li>Create an account on Zenodo that is linked to your Github
+<li>Create an account on Zenodo that is linked to your GitHub
 account.</li>
 <li>Use Zenodo to create a release for your repository and obtain a DOI
 for it.</li>
@@ -7340,12 +7383,12 @@ <h3 class="callout-title">Archive your repository to Zenodo</h3>
 <i class="callout-icon" data-feather="bell"></i>
 </div>
 <div id="problems-with-github-and-zenodo-integration" class="callout-inner">
-<h3 class="callout-title">Problems with Github and Zenodo integration</h3>
+<h3 class="callout-title">Problems with GitHub and Zenodo integration</h3>
 <div class="callout-content">
-<p>The integration between Github and Zenodo does not interact well with
+<p>The integration between GitHub and Zenodo does not interact well with
 some browser privacy features and extensions. Firefox can be
 particularly problematic with this and might open new tabs to login to
-Github and then give an error saying:
+GitHub and then give an error saying:
 <code>Your browser did something unexpected.  Please try again. If the error continues, try disabling all browser extensions.</code>
 If this happens try disabling the extra privacy features/extensions or
 using another browser such as Chrome.</p>
@@ -7357,35 +7400,49 @@ <h3 class="callout-title">Problems with Github and Zenodo integration</h3>
 <h3 id="adding-a-doi-and-orcid-to-the-citation-file">Adding a DOI and ORCID to the citation file<a class="anchor" aria-label="anchor" href="#adding-a-doi-and-orcid-to-the-citation-file"></a>
 </h3>
 <p>Now that we have our DOI it is good practice to include this
-information in our citation file. In the previous part of this lesson we
-created a <code>CITATION.cff</code> file with information about how to
-cite our code. There are a few fields we can add which are related to
-the DOI, one of these is the <code>version</code> file which covers the
+information in our citation file. Earlier we created a
+<code>CITATION.cff</code> file with information about how to cite our
+code. There are a few fields we can add now which are related to the
+DOI; one of these is the <code>version</code> file which covers the
 version number of the software. We can add a DOI to the file in the
 <code>identifiers</code> section with a type of <code>doi</code> and
-<code>value</code> with the URL. Optionally we can also add a
+<code>value</code> of the Zenodo URL. Optionally we can also add a
 <code>date-released</code> field indicating the date we released this
-software. Here is an updated version of our CITATION.cff from the
-previous episode with a version number, DOI and release date added.</p>
+software. Here is an updated version of our <code>CITATION.cff</code>
+from the previous episode with a version number, DOI and release date
+added.</p>
 <div class="codewrapper sourceCode" id="cb3">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb3-1"><a href="#cb3-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
 <span id="cb3-2"><a href="#cb3-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb3-3"><a href="#cb3-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb3-4"><a href="#cb3-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
-<span id="cb3-5"><a href="#cb3-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb3-6"><a href="#cb3-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb3-7"><a href="#cb3-7" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb3-8"><a href="#cb3-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb3-9"><a href="#cb3-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb3-10"><a href="#cb3-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
-<span id="cb3-11"><a href="#cb3-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span>
-<span id="cb3-12"><a href="#cb3-12" tabindex="-1"></a><span class="fu">version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.0.1</span></span>
-<span id="cb3-13"><a href="#cb3-13" tabindex="-1"></a><span class="fu">identifiers</span><span class="kw">:</span></span>
-<span id="cb3-14"><a href="#cb3-14" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> doi</span></span>
-<span id="cb3-15"><a href="#cb3-15" tabindex="-1"></a><span class="at">    </span><span class="fu">value</span><span class="kw">:</span><span class="at"> 10.5281/zenodo.1234</span></span>
-<span id="cb3-16"><a href="#cb3-16" tabindex="-1"></a><span class="fu">date-released</span><span class="kw">:</span><span class="at"> 2024-06-01</span></span></code></pre>
+<span id="cb3-3"><a href="#cb3-3" tabindex="-1"></a></span>
+<span id="cb3-4"><a href="#cb3-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb3-5"><a href="#cb3-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
+<span id="cb3-6"><a href="#cb3-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-7"><a href="#cb3-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb3-8"><a href="#cb3-8" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb3-9"><a href="#cb3-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb3-10"><a href="#cb3-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb3-11"><a href="#cb3-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
+<span id="cb3-12"><a href="#cb3-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
+<span id="cb3-13"><a href="#cb3-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
+<span id="cb3-14"><a href="#cb3-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
+<span id="cb3-15"><a href="#cb3-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
+<span id="cb3-16"><a href="#cb3-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
+<span id="cb3-17"><a href="#cb3-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-18"><a href="#cb3-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
+<span id="cb3-19"><a href="#cb3-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-20"><a href="#cb3-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
+<span id="cb3-21"><a href="#cb3-21" tabindex="-1"></a>  data</span>
+<span id="cb3-22"><a href="#cb3-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
+<span id="cb3-23"><a href="#cb3-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
+<span id="cb3-24"><a href="#cb3-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span>
+<span id="cb3-25"><a href="#cb3-25" tabindex="-1"></a><span class="fu">version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.0.1</span></span>
+<span id="cb3-26"><a href="#cb3-26" tabindex="-1"></a><span class="fu">identifiers</span><span class="kw">:</span></span>
+<span id="cb3-27"><a href="#cb3-27" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> doi</span></span>
+<span id="cb3-28"><a href="#cb3-28" tabindex="-1"></a><span class="at">    </span><span class="fu">value</span><span class="kw">:</span><span class="at"> 10.5281/zenodo.1234</span></span>
+<span id="cb3-29"><a href="#cb3-29" tabindex="-1"></a><span class="fu">date-released</span><span class="kw">:</span><span class="at"> 2024-06-01</span></span></code></pre>
 </div>
 <div id="add-a-doi-to-your-citation-file" class="callout discussion">
 <div class="callout-square">
@@ -7395,10 +7452,11 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="callout-title">Add a DOI to your citation file</h3>
 <div class="callout-content">
 <p>Add the DOI you were allocated in the previous exercise to your
-CITATION.cff file and commit/push the updated version to your Github
-repository. You can remove the <code>commit</code> field from the
-CITATION.cff file as the DOI is a better way to point to given version
-of the code.</p>
+<code>CITATION.cff</code> file and then commit and push the updated
+version to your GitHub repository. If you used the <code>commit</code>
+field in your <code>CITATION.cff</code> file before to point to a given
+version of the code - you can now remove it as using the DOI field is
+better for this job.</p>
 </div>
 </div>
 </div>
@@ -7429,25 +7487,25 @@ <h3 class="callout-title">Going further with publishing code</h3>
 </section><section><h2 class="section-heading" id="working-with-collaborators">Working with collaborators<a class="anchor" aria-label="anchor" href="#working-with-collaborators"></a>
 </h2>
 <hr class="half-width">
-<p>The strength of online collaboration tools such as Github doesn’t
-just lie in the ability to share code. They also allow us to track
+<p>The strength of online collaboration platforms such as GitHub does
+not just lie in the ability to share code. They also allow us to track
 problems with that code, for multiple developers to work on it
 independently and bring their changes together and to review those
 changes before they are accepted.</p>
 <div class="section level3">
 <h3 id="tracking-issues-with-code">Tracking issues with code<a class="anchor" aria-label="anchor" href="#tracking-issues-with-code"></a>
 </h3>
-<p>A key feature of Github (as opposed to Git itself) is the issue
+<p>A key feature of GitHub (as opposed to Git itself) is the issue
 tracker. This provides us with a place to keep track of any problems or
 bugs in the code and to discuss them with other developers. Sometimes
 advanced users will also use issue trackers of public projects to report
 problems they are having (and sometimes this is misused by users seeking
 help using documented features of the program).</p>
 <p>The code from the testing chapter earlier has a bug with an extra
-bracket in eva_data_analysis.py (and if you’ve fixed that a missing
+bracket in eva_data_analysis.py (and if you have fixed that a missing
 import of summarise_categorical in the test). Let’s go ahead and create
-a new issue in our Github repository to describe this problem. We can
-find the issue tracker on the “Issues” tab in the top left of the Github
+a new issue in our GitHub repository to describe this problem. We can
+find the issue tracker on the “Issues” tab in the top left of the GitHub
 page for the repository. Click on this and then click on the green “New
 Issue” button on the right hand side of the screen. We can then enter a
 title and description of our issue.</p>
@@ -7473,7 +7531,7 @@ <h3 class="callout-title">Write an issue to describe our bug</h3>
 <p>Create a new issue in your repository’s issue tracker by doing the
 following:</p>
 <ul>
-<li>Go to the Github webpage for your code</li>
+<li>Go to the GitHub webpage for your code</li>
 <li>Click on the Issues tab</li>
 <li>Click on the “New issue” button</li>
 <li>Enter a title and description for the issue</li>
@@ -7497,7 +7555,7 @@ <h3 id="discussing-an-issue">Discussing an issue<a class="anchor" aria-label="an
 <h3 id="closing-an-issue">Closing an issue<a class="anchor" aria-label="anchor" href="#closing-an-issue"></a>
 </h3>
 <p>Once an issue is solved then it can be closed. This can be done
-either by pressing the “Close” button in the Github web interface or by
+either by pressing the “Close” button in the GitHub web interface or by
 making a commit which includes the word “fixes”, “fixed”, “close”,
 “closed” or “closes” followed by a # symbol and the issue number.</p>
 </div>
@@ -7509,37 +7567,38 @@ <h3 id="working-in-parallel-with-git-branches">Working in parallel with Git bran
 with another. Branches are commonly used as a way for one developer to
 work on a new feature or a bug fix while other developers work on other
 features. When those new features or bug fixes are complete, the branch
-will be merged back with the main (sometimes called master) branch.</p>
+will be merged back with the <code>main</code> (sometimes called the
+<code>master</code>) branch.</p>
 <div class="section level4">
 <h4 id="creating-a-new-branch">Creating a new branch<a class="anchor" aria-label="anchor" href="#creating-a-new-branch"></a>
 </h4>
-<p>New git branches are created with the <code>git branch</code>
+<p>New Git branches are created with the <code>git branch</code>
 command. This should be followed by the name of the branch to create. It
 is common practice when the bug we are fixing has a corresponding issue
 to name the branch after the issue number and name. For example, we
-might call the branch <code>01-extra-brakcet-bug</code> instead of
+might call the branch <code>01-extra-bracket-bug</code> instead of
 something less descriptive like <code>bugfix</code>.</p>
 <p>For example, the command:</p>
 <div class="codewrapper sourceCode" id="cb4">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="fu">git</span> branch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git branch 01-extra-bracket-bug</span></code></pre>
 </div>
-<p>will create a new branch called <code>01-extra-brakcet-bug</code>. We
-can view the names of all the branches, by default there should be one
-branch called <code>main</code> or perhaps <code>master</code> and our
-new <code>01-extra-brakcet-bug</code> branch. by running
-<code>git branch</code> with no parameters. This will put <code>*</code>
-next to the currently active branch.</p>
+<p>will create a new branch called <code>01-extra-bracket-bug</code>. We
+can view the names of all the branches by running
+<code>git branch</code> with no parameters. By default there should be
+one branch called <code>main</code> (formerly <code>master</code>) and
+our new <code>01-extra-bracket-bug</code> branch. The command will put
+<code>*</code> next to the currently active branch.</p>
 <div class="codewrapper sourceCode" id="cb5">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" tabindex="-1"></a><span class="fu">git</span> branch</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git branch</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="output" tabindex="0"><code>  01-extra-brakcet-bug
+<pre class="output" tabindex="0"><code>  01-extra-bracket-bug
 * main</code></pre>
 </div>
 <p>We can see that creating a new branch has not activated that branch.
@@ -7549,28 +7608,28 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="fu">git</span> switch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch 01-extra-bracket-bug</span></code></pre>
 </div>
 <p>To create a branch and change to it in a single command we can use
 <code>git switch</code> with the <code>-c</code> option (or
-<code>git checkout</code> with the <code>-b</code> option,
-<code>git switch</code> is only found in more recent versions of
-Git).</p>
+<code>git checkout</code> with the <code>-b</code> option). Note that
+<code>git switch</code> command is only available in more recent
+versions of Git.</p>
 <div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="fu">git</span> switch <span class="at">-c</span> 02-another-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch <span class="at">-c</span> 02-another-bug</span></code></pre>
 </div>
 </div>
 <div class="section level4">
 <h4 id="committing-to-a-branch">Committing to a branch<a class="anchor" aria-label="anchor" href="#committing-to-a-branch"></a>
 </h4>
 <p>Once we have switched to a branch any further commits that are made
-will go to that branch. When we run a <code>git commit</code> command
-we’ll see the name of the branch we’re committing to in the output of
+will go to that branch. When we run a <code>git commit</code> command we
+will see the name of the branch we are committing to in the output of
 <code>git commit</code>. Let’s edit our code and fix the lack of default
 values bug that we entered into the issue tracker earlier on.</p>
-<p>Change your code from</p>
+<p>Change your code from:</p>
 <div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -7586,7 +7645,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb11">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"fixed bug"</span> eva_data_analysis.py</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"fixed bug"</span> eva_data_analysis.py</span></code></pre>
 </div>
 <p>In the output of <code>git commit -m</code> the first part of the
 output line will show the name of the branch we just made the commit
@@ -7602,14 +7661,14 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">git</span> switch main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch main</span></code></pre>
 </div>
-<p>And if we go back to the <code>01-extra-brakcet-bug</code> branch it
+<p>And if we go back to the <code>01-extra-bracket-bug</code> branch it
 will re-appear.</p>
 <div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="fu">git</span> switch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch 01-extra-bracket-bug</span></code></pre>
 </div>
 <p>If we want to push our changes to a remote such as GitHub we have to
 tell the <code>git push</code> command which branch to push to. If the
@@ -7618,18 +7677,18 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="codewrapper sourceCode" id="cb15">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">git</span> push origin 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin 01-extra-bracket-bug</span></code></pre>
 </div>
-<p>If we now refresh the Github webpage for this repository we should
+<p>If we now refresh the GitHub webpage for this repository we should
 see the bugfix branch has appeared in the list of branches.</p>
 <p>If we needed to pull changes from a branch on a remote (for example
-if we’ve made changes on another computer or via Github’s web based
+if we have made changes on another computer or via GitHub’s web based
 editor), then we can specify a branch on a <code>git pull</code>
 command.</p>
 <div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">git</span> pull origin 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">git</span> pull origin 01-extra-bracket-bug</span></code></pre>
 </div>
 </div>
 </div>
@@ -7639,19 +7698,19 @@ <h3 id="merging-branches">Merging branches<a class="anchor" aria-label="anchor"
 <p>When we have completed working on a branch (for example fixing a bug)
 then we can merge our branch back into the main one (or any other
 branch). This is done with the <code>git merge</code> command.</p>
-<p>This must be run on the <em>TARGET</em> branch of the merge, so we’ll
-have to use a <code>git switch</code> command to set this.</p>
+<p>This must be run on the <em>TARGET</em> branch of the merge, so we
+will have to use a <code>git switch</code> command to set this.</p>
 <div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="fu">git</span> switch main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch main</span></code></pre>
 </div>
-<p>Now we’re back on the main branch we can go ahead and merge the
+<p>Now we are back on the main branch we can go ahead and merge the
 changes from the bugfix branch:</p>
 <div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="fu">git</span> merge 01-extra-bracket-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git merge 01-extra-bracket-bug</span></code></pre>
 </div>
 </div>
 <div class="section level3">
@@ -7660,25 +7719,26 @@ <h3 id="pull-requests">Pull requests<a class="anchor" aria-label="anchor" href="
 <p>On larger projects we might need to have a code review process before
 changes are merged, especially before they are merged onto the main
 branch that might be what is being released as the public version of the
-software. Github has a process for this that it calls a “Pull Request”,
-other Git services such as GitLab have different names for this, GitLab
-calls them “Merge Requests”. Pull requests are where one developer
-requests that another merge code from a branch (or “pull” it from
-another copy of the repository). The person receiving the request then
-has the chance to review the code, write comments suggesting changes or
-even change the code themselves before merging it. It is also very
-common for automated checks of code to be run on a pull request to
-ensure the code is of good quality and is passing automated tests.</p>
+software. GitHub has a process for this that is called a <strong>pull
+request</strong>. Other Git services such as GitLab have different names
+for this; GitLab calls them <strong>merge requests</strong>. Pull
+requests are situations where one developer requests that another merges
+code from a branch (or “pull” it from another copy of the repository).
+The person receiving the request then has the chance to review the code,
+write comments suggesting changes or even change the code themselves
+before merging it. It is also very common for automated checks of code
+to be run on a pull request to ensure the code is of good quality and is
+passing automated tests.</p>
 <p>As a simple example of a pull request, we can now create a pull
 request for the changes we made on our <code>01-extra-bracket-bug</code>
-branch and pushed to Github earlier on. The Github webpage for our
-repository will now be saying something like “bugfix had recent pushes n
-minutes ago - Compare &amp; Pull request”. Click on this button and
-create a new pull request.</p>
+branch and pushed to GitHub earlier on. The GitHub webpage for our
+repository will now be saying something like “bugfix had recent pushes
+<code>n</code> minutes ago - Compare &amp; Pull request”. Click on this
+button and create a new pull request.</p>
 <p>Give the pull request a title and write a brief description of it,
-then click the green “Create pull request” button. Github will then
-check if we can merge this pull request without any problems. We’ll look
-at what to do when this isn’t possible later on.</p>
+then click the green “Create pull request” button. GitHub will then
+check if we can merge this pull request without any problems. We will
+look at what to do when this is not possible later on.</p>
 <p>There should be a green “Merge pull request” button, but if we click
 on the down arrow inside this button there are three options on how to
 handle this request:</p>
@@ -7702,44 +7762,45 @@ <h3 id="pull-requests">Pull requests<a class="anchor" aria-label="anchor" href="
 kind of merge they will prefer. For the purposes of this exercise we’ll
 stick with the default merge commit.</p>
 <p>Go ahead and click on “Merge pull request”, then “Confirm merge”. The
-changes will now be merged together. Github gives us the option to
-delete the branch we were working on, since it’s history is preserved in
-the main branch there isn’t any reason to keep it.</p>
+changes will now be merged together. GitHub gives us the option to
+delete the branch we were working on, since its history is preserved in
+the main branch there is no reason to keep it.</p>
 <div class="section level4">
 <h4 id="using-forks-instead-of-branches">Using forks instead of branches<a class="anchor" aria-label="anchor" href="#using-forks-instead-of-branches"></a>
 </h4>
 <p>A fork is similar to a branch, but instead of it being part of the
 same repository it is a entirely new copy of the repository. Forks are
-commonly used by Github users who wish to work on a project that they’re
-not a member of. Typically forking will copy the repository to our own
-namespace (e.g. github.com/username/reponame instead of
+commonly used by Github users who wish to work on a project that they
+are not a member of. Typically forking will copy the repository to our
+own namespace (e.g. github.com/username/reponame instead of
 github.com/projectname/reponame)</p>
 <p>To create a fork on github use the “Fork” button to the right of the
 repository name. After we create our fork we can make some changes and
 these could even be on the main branch inside our forked repository.
-Github will track that a fork has been made displays a “Contribute”
+GitHub will track that a fork has been made displays a “Contribute”
 button to create a pull request back to the original repository. Using
 this we can request that the changes on our fork are incorporated by the
 upstream project.</p>
-<div id="pull-request-exercise" class="callout discussion">
+<div id="practice-pull-requests" class="callout discussion">
 <div class="callout-square">
 <i class="callout-icon" data-feather="message-circle"></i>
 </div>
-<div id="pull-request-exercise" class="callout-inner">
-<h3 class="callout-title">Pull request exercise</h3>
+<div id="practice-pull-requests" class="callout-inner">
+<h3 class="callout-title">Practice pull requests</h3>
 <div class="callout-content">
-<p>Q: Work in pairs for this exercise. Share the Github link of your
+<p>Q: Work in pairs for this exercise. Share the GitHub link of your
 repository with your partner. If you have set your repository to
-private, you’ll need to add them as a collaborator. Go to the settings
-page on your Github repository’s webpage, click on Collaborators from
+private, you will need to add them as a collaborator. Go to the settings
+page on your GitHub repository’s webpage, click on Collaborators from
 the left hand menu and then click the green “Add People” button and
-enter the Github username or email address of your partner. They will
-get an email and an alert within Github to accept your invitation to
+enter the GitHub username or email address of your partner. They will
+get an email and an alert within GitHub to accept your invitation to
 work on this repository, without doing this they won’t be able to access
 it.</p>
 <ul>
 <li>Now make a fork of your partners repository.</li>
-<li>Edit the CITATION.cff file and add your name to it.</li>
+<li>Edit the <code>CITATION.cff</code> file and add your name to
+it.</li>
 <li>Commit these changes to your fork</li>
 <li>Create a pull request back to the original repository</li>
 <li>Your partner will now receive your pull request and can review</li>
@@ -7747,24 +7808,14 @@ <h3 class="callout-title">Pull request exercise</h3>
 </div>
 </div>
 </div>
-<div id="commit-and-push-your-changes" class="callout">
-<div class="callout-square">
-<i class="callout-icon" data-feather="bell"></i>
-</div>
-<div id="commit-and-push-your-changes" class="callout-inner">
-<h3 class="callout-title">Commit and push your changes</h3>
-<div class="callout-content">
-<p>Do not forget to commit any uncommited changes you may have and then
+<p>Do not forget to commit any uncommitted changes you may have and then
 push your work to GitHub.</p>
 <div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="fu">git</span> add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
-<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
-<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
-</div>
-</div>
-</div>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
+<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 </div>
 </div>
@@ -7777,7 +7828,7 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <li>Licencing and citation episodes from the <a href="https://swcarpentry.github.io/git-novice" class="external-link">Software Carpentry’s Git
 Novice lesson</a>
 </li>
-<li>Carpentries Github Skill ups for <a href="https://carpentries-incubator.github.io/github-skill-up-instructors/" class="external-link">instructors</a>
+<li>Carpentries GitHub Skill ups for <a href="https://carpentries-incubator.github.io/github-skill-up-instructors/" class="external-link">instructors</a>
 and <a href="https://carpentries.github.io/github-skill-up-maintainers/" class="external-link">maintainers</a>
 </li>
 <li>
@@ -7802,26 +7853,13 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="callout-title">Key Points</h3>
 <div class="callout-content">
 <ul>
-<li>Open source applies Copyright licenses permitting others to reuse
-and adapt your code or data.</li>
-<li>Permissive licenses allow code to be used in other products
-providing the copyright statement is displayed.</li>
-<li>Copyleft licenses require the source code of any modifications to be
-released under a copyleft license.</li>
-<li>Creative commons licenses are suitable for non-code files such as
-documentation and images.</li>
-<li>Open source software can be sold, but you must supply the source
-code and the people you sell it to can give it away to somebody
-else.</li>
-<li>Add license file to your repository and add a license to each file
-in case it gets detached.</li>
-<li>Zenodo can be used to archive a Github repository and obtain a DOI
+<li>Zenodo can be used to archive a GitHub repository and obtain a DOI
 for it.</li>
-<li>We can include a CITATION file to tell people how to cite our
-code.</li>
-<li>Github can track bugs or issues with a program.</li>
+<li>We include a CITATION file with our code to tell people how to cite
+it.</li>
+<li>GitHub can help us track bugs or issues with software.</li>
 <li>Git branches can be used to allow multiple developers to work on the
-same part of a program in parallel.</li>
+same part of code in parallel.</li>
 <li>The <code>git branch</code> command shows the list of branches and
 can create new branches.</li>
 <li>The <code>git switch</code> command changes which branch we are
@@ -7967,7 +8005,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer>
 </div> <!-- / div.container -->
@@ -7990,8 +8028,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/aio.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/aio.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/ci-for-testing.html b/ci-for-testing.html
index 3412f570..092ed7c7 100644
--- a/ci-for-testing.html
+++ b/ci-for-testing.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -582,7 +582,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -605,7 +605,7 @@ <h3 class="callout-title">Key Points</h3>
   "identifier": "https://softwaresaved.github.io/fair-research-software/ci-for-testing.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/ethical-environmental-considerations.html b/ethical-environmental-considerations.html
index 990c318d..a9a8f81d 100644
--- a/ethical-environmental-considerations.html
+++ b/ethical-environmental-considerations.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -446,7 +446,7 @@ <h3 class="callout-title">Scraping publicly available data responsibly</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <ol style="list-style-type: decimal"><li>Compliance with Terms of Service (ToS) - most websites, including
 forums, have ToS that explicitly prohibit or restrict web scraping.
@@ -522,7 +522,7 @@ <h3 class="callout-title">Ethical software reuse</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <p>When incorporating other researchers’ software into our research
 workflows we should not do it blindly but should inspect it critically
@@ -603,7 +603,7 @@ <h3 class="callout-title">Intellectual property and licensing of AI-generated co
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution3" aria-expanded="false" aria-controls="collapseSolution3">
   <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 </button>
-<div id="collapseSolution3" class="accordion-collapse collapse" aria-labelledby="headingSolution3" data-bs-parent="#accordionSolution3">
+<div id="collapseSolution3" class="accordion-collapse collapse" data-bs-parent="#accordionSolution3" aria-labelledby="headingSolution3">
 <div class="accordion-body">
 <p>Here are some considerations:</p>
 <ul><li>Intellectual Property (IP) ownership of the AI-generated code -
@@ -685,7 +685,7 @@ <h3 class="callout-title">Using HPC systems in a more environmentally responsibl
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution4" aria-expanded="false" aria-controls="collapseSolution4">
   <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
 </button>
-<div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
+<div id="collapseSolution4" class="accordion-collapse collapse" data-bs-parent="#accordionSolution4" aria-labelledby="headingSolution4">
 <div class="accordion-body">
 <p>Here are some thing to consider:</p>
 <ul><li>Code efficiency: writing efficient code and choosing more efficient
@@ -783,7 +783,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -806,7 +806,7 @@ <h3 class="callout-title">Key Points</h3>
   "identifier": "https://softwaresaved.github.io/fair-research-software/ethical-environmental-considerations.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-09-17",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/images.html b/images.html
index 61e25d06..6c139333 100644
--- a/images.html
+++ b/images.html
@@ -354,7 +354,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -509,7 +509,7 @@ <h3 id="04-version-control-figure-8">Figure 8</h3>
 <hr class="half-width"></section><section id="07-code-structure"><h2 class="section-heading"><a href="07-code-structure.html">Code structure</a></h2>
 <hr class="half-width"></section><section id="08-code-correctness"><h2 class="section-heading"><a href="08-code-correctness.html">Code correctness</a></h2>
 <hr class="half-width"></section><section id="09-code-documentation"><h2 class="section-heading"><a href="09-code-documentation.html">Code documentation</a></h2>
-<hr class="half-width"></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open collaboration on code</a></h2>
+<hr class="half-width"></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open code &amp; collaboration</a></h2>
 <hr class="half-width">
 <h3 id="10-open-collaboration-figure-1">Figure 1</h3>
 <p aria-hidden="true">Image 1 of 1: ‘DOI’</p>
@@ -560,7 +560,7 @@ <h3 id="11-wrap-up-figure-4">Figure 4</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer>
 </div> <!-- / div.container -->
@@ -583,8 +583,8 @@ <h3 id="11-wrap-up-figure-4">Figure 4</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/images.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/images.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/index.html b/index.html
index 0989c62a..e494cb35 100644
--- a/index.html
+++ b/index.html
@@ -298,7 +298,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -903,7 +903,7 @@ <h3 id="astronaut-data-and-analysis-code">Astronaut data and analysis code<a cla
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -925,8 +925,8 @@ <h3 id="astronaut-data-and-analysis-code">Astronaut data and analysis code<a cla
   "url": "https://softwaresaved.github.io/fair-research-software/index.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/index.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor-notes.html b/instructor-notes.html
index 05da90bb..f2a01160 100644
--- a/instructor-notes.html
+++ b/instructor-notes.html
@@ -354,7 +354,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -465,7 +465,7 @@ <h1>Instructor Notes</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer>
 </div> <!-- / div.container -->
@@ -488,8 +488,8 @@ <h1>Instructor Notes</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor-notes.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor-notes.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/01-introduction.html b/instructor/01-introduction.html
index 0d707ace..fc8128b6 100644
--- a/instructor/01-introduction.html
+++ b/instructor/01-introduction.html
@@ -303,7 +303,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -705,7 +705,7 @@ <h3 class="callout-title">What does open and reproducible research mean
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -728,7 +728,7 @@ <h3 class="callout-title">What does open and reproducible research mean
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/01-introduction.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-07-04",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/02-fair-research-software.html b/instructor/02-fair-research-software.html
index 698682e0..b32da463 100644
--- a/instructor/02-fair-research-software.html
+++ b/instructor/02-fair-research-software.html
@@ -300,7 +300,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -373,7 +373,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>FAIR research software</h1>
-        <p>Last updated on 2024-07-04 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/02-fair-research-software.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -460,39 +460,55 @@ <h3 class="callout-title">Motivation</h3>
 below is not exhaustive, but any of the practices that you employ in
 your research software workflow will bring you closer to the gold
 standard of a fully reproducible research.</p>
-<ul><li>Findable
-<ul><li>Create a description of your software</li>
+<div class="section level3">
+<h3 id="findable">Findable<a class="anchor" aria-label="anchor" href="#findable"></a></h3>
+<p>In order to make your software more findable, you should:</p>
+<ul><li>Create a description of your software to make it discoverable by
+search engines and other search tools</li>
 <li>Place your software in a public software repository (and ideally
-register it in a <a href="https://github.com/NLeSC/awesome-research-software-registries" class="external-link">software
-registry</a>)</li>
+register it in a [general-purpose or domain-specific software
+registry][software-registries])</li>
 <li>Use a unique and persistent identifier (DOI) for your software
-(e.g. by depositing your code on Zenodo), which is also useful for
+(e.g. by depositing your code on <a href="https://zenodo.org/" class="external-link">Zenodo</a>), which is also useful for
 citations - note that depositing your data/code on GitHub and similar
 software repositories may not be enough as they may change their open
-access model or disappear completely in the future</li>
-</ul></li>
-<li>Accessible
+access model or disappear completely in the future, so archiving your
+code means it stands a better chance at being preserved</li>
+</ul></div>
+<div class="section level3">
+<h3 id="accessible">Accessible<a class="anchor" aria-label="anchor" href="#accessible"></a></h3>
+<p>In order to make your software more accessible, you should:</p>
 <ul><li>Make sure people can freely, legally and easily get a copy your
 software</li>
-<li>Use coding conventions and comments to make your code readable and
-understandable by people (once they get a copy of it)</li>
-</ul></li>
-<li>Interoperable
-<ul><li>Explain the functionality of your software</li>
+<li>Use code style conventions and code structure patterns, use comments
+and create documentation to make your code comprehensible by people
+(once they get a copy of it) - i.e. make your code accessible in the
+<em>intelligible</em> sense</li>
+</ul></div>
+<div class="section level3">
+<h3 id="interoperable">Interoperable<a class="anchor" aria-label="anchor" href="#interoperable"></a></h3>
+<p>In order to make your software more interoperable, you should:</p>
+<ul><li>Explain the functionality of your software, so others can understand
+how other tools can interoperate with it</li>
 <li>Use standard formats for inputs and outputs</li>
 <li>Communicate with other software via standard protocols and APIs</li>
-</ul></li>
-<li>Reusable
+</ul></div>
+<div class="section level3">
+<h3 id="reusable">Reusable<a class="anchor" aria-label="anchor" href="#reusable"></a></h3>
+<p>In order to make your software more reusable, you should:</p>
 <ul><li>Document your software (including its functionality, and how to
-install and run it)</li>
-<li>Follow best practices for software development (including coding
-conventions, code readability and verifying its correctness)</li>
+install and run it) to make it more understandable by others who may
+wish to reuse or extend it</li>
+<li>Follow best practices for software development (including code
+conventions, structure, readability and correctness)</li>
 <li>Test your software and make sure it works on different
-platforms/operating systems</li>
+platforms/operating systems to make it more reusable</li>
 <li>Give a licence to your software clearly stating how it can be
 reused</li>
-<li>State how to cite your software</li>
-</ul></li>
+<li>State how to cite your software, so people can give you credit when
+they reuse it</li>
+<li>Include a contributor policy so that others can contribute to your
+code and credit for contributions is provided</li>
 </ul><div id="fair-is-a-process-not-a-perfect-metric" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
@@ -500,7 +516,7 @@ <h3 class="callout-title">Motivation</h3>
 <div id="fair-is-a-process-not-a-perfect-metric" class="callout-inner">
 <h3 class="callout-title">FAIR is a process, not a perfect metric</h3>
 <div class="callout-content">
-<p>FAIR is not a binary metric - there is no such thing as “FAIR or not
+<p>FAIR is not a binary metric - there is no such thing as “FAIR or”not
 FAIR”.</p>
 <p>FAIR is not a perfect metric, nor does it provide a full and
 exhaustive software quality checklist. Software may be FAIR but still
@@ -542,13 +558,15 @@ <h3 class="callout-title">Challenge</h3>
 </ul></div>
 </div>
 </div>
+</div>
 </section><section><h2 class="section-heading" id="software-and-data-used-in-this-course">Software and data used in this course<a class="anchor" aria-label="anchor" href="#software-and-data-used-in-this-course"></a></h2>
 <hr class="half-width"><p>We are going to follow a fairly typical experience of a new PhD or
 postdoc joining a research group. They were emailed some data and
 analysis code bundled in a <code>.zip</code> archive and written by
-another group member who works on similar things. They need to be able
-to install and run this code on their machine, check they understand it
-and then adapt it to their own project.</p>
+another group member who worked on similar things but has since left the
+group. They need to be able to install and run this code on their
+machine, check they can understand it and then adapt it to their own
+project.</p>
 <p>As part of the <a href="./index.html#astronaut-data-and-analysis-code">setup for this
 course</a>, you should have downloaded a <code>.zip</code> archive
 containing the software project the new research team member was given.
@@ -577,10 +595,11 @@ <h3 class="callout-title">Challenge</h3>
 <div class="callout-inner">
 <h3 class="callout-title">Discussion</h3>
 <div class="callout-content">
-<p>Compare this data and code to the software you chose earlier. Do you
-think it is Findable, Accessible, Interoperable and Reusable? Give it a
-score from 1 to 5 in each category, as in the previous exercise, and
-then we will discuss it together.</p>
+<p>Look at our code in VS Code and compare this data and code to the
+software you chose earlier (or assess it on its own). Do you think it is
+Findable, Accessible, Interoperable and Reusable? Give it a score from 1
+to 5 in each category, as in the previous exercise, and then we will
+discuss it together.</p>
 </div>
 </div>
 </div>
@@ -758,7 +777,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -780,8 +799,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/02-fair-research-software.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/02-fair-research-software.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-07-04",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/03-tools.html b/instructor/03-tools.html
index 1452cf1c..a77a6b15 100644
--- a/instructor/03-tools.html
+++ b/instructor/03-tools.html
@@ -234,16 +234,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 
     <div id="flush-collapsecurrent" class="accordion-collapse collapse show" aria-labelledby="flush-headingcurrent" data-bs-parent="#accordionFlushcurrent">
       <div class="accordion-body">
-        <ul><li><a href="#development-environment">Development environment</a></li>
-<li><a href="#command-line-toolshell">Command line tool/shell</a></li>
-<li><a href="#version-control">Version control</a></li>
-<li><a href="#code-structure-and-style-guidelines">Code structure and style guidelines</a></li>
-<li><a href="#code-correctness">Code correctness</a></li>
-<li><a href="#documentation">Documentation</a></li>
-<li><a href="#licences-and-citation">Licences and citation</a></li>
-<li><a href="#code-repositories-and-registries">Code repositories and registries</a></li>
-<li><a href="#summary-of-tools-practices">Summary of tools &amp; practices</a></li>
-<li><a href="#checking-your-setup">Checking your setup</a></li>
+        <ul><li><a href="#checking-your-setup">Checking your setup</a></li>
 <li><a href="#further-reading">Further reading</a></li>
         </ul></div><!--/div.accordion-body-->
     </div><!--/div.accordion-collapse-->
@@ -308,7 +299,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -381,7 +372,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Tools and practices for FAIR research software development</h1>
-        <p>Last updated on 2024-09-24 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/03-tools.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -424,233 +415,210 @@ <h3 class="card-title">Objectives</h3>
 <p>In this course we will introduce you to a group of tools and
 practices that are commonly used in research to help you develop
 software in a FAIR way. You should already have these tools installed on
-your machine following the setup instructions. Here we will give an
-overview of the tools, how they help you achieve the aims of FAIR
-research software and how they work together. In later episodes we will
-describe some of these tools in more detail.</p>
-<section><h2 class="section-heading" id="development-environment">Development environment<a class="anchor" aria-label="anchor" href="#development-environment"></a></h2>
-<hr class="half-width"><p>One of the first choices we make when writing code is what tool to
-use to do the writing. You can use a simple text editor such as Notepad,
-a terminal based editor with syntax highlighting such as Vim or Emacs,
-or one of many Integrated Development Environments (IDEs) which give you
-the tools to write, run and debug your code and inspect the output all
-in one place. Note that you should not use word processing software such
-as Microsoft Word or Apple Pages to write code - these tools are
-designed to create nicely formatted text for humans to read, so they may
-add or change formatting, or insert invisible characters that the
-programming language cannot interpret. Try opening a Word document in
-Notepad to see an example.</p>
-<p>This is mostly a personal choice as an experienced user of any of
-these tools can write good, FAIR software efficiently, but IDEs are
-popular because they are designed specifically for writing and running
-code. There are some language specific IDEs such as PyCharm, and some
-that can work with many languages like VS Code (Visual Studio Code).
-IDEs also have add-ons that provide extra functionality, such as
-checking your code as you type (similar to a spell-checker in Word),
-highlighting when you are not following best practice, or even
-automatically generating bits of code for you.</p>
-<div id="accordionInstructor1" class="accordion instructor-note accordion-flush">
-<div class="accordion-item">
-<button class="accordion-button instructor-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseInstructor1" aria-expanded="false" aria-controls="collapseInstructor1">
-  <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square"><i aria-hidden="true" class="callout-icon" data-feather="edit-2"></i></div> Instructor Note </h3>
-</button>
-<div id="collapseInstructor1" class="accordion-collapse collapse" aria-labelledby="headingInstructor1" data-bs-parent="#accordionInstructor1">
-<div class="accordion-body">
-<p>At this point you could open the Python file or another file in VS
-Code to show all the squiggly lines suggesting improvements.</p>
+your machine following the <a href="./index.html#astronaut-data-and-analysis-code">setup
+instructions</a>. Here we will give an overview of the tools, how they
+help you achieve the aims of FAIR research software and how they work
+together. In later episodes we will describe some of these tools in more
+detail.</p>
+<div class="section level3">
+<h3 id="development-environments">Development environments<a class="anchor" aria-label="anchor" href="#development-environments"></a></h3>
+<p>Virtual and integrated development environments (IDEs), such as VS
+Code or PyCharm, help with running, testing, and debugging code. Virtual
+environments further enable us to share our working environments with
+others, making it easier to access, reuse and extend our code. IDEs
+often provide integrations with other tools, e.g. version control and
+command line terminals, enabling you to do many tasks from a single
+environment, saving time in switching between different tools.</p>
+</div>
+<div class="section level3">
+<h3 id="command-line-terminals">Command line terminals<a class="anchor" aria-label="anchor" href="#command-line-terminals"></a></h3>
+<p>Command line terminals (e.g. Bash, GitBash) enable us to run and test
+our code without graphical user interfaces (GUI) afforded to us by IDEs
+- this is sometimes needed for accessing and running our code remotely
+on servers and high-performance systems without a GUI provision, where
+time, memory and processing power are expensive or in high demand.</p>
+<p>Version control systems are typically provided as command line tools,
+making them often only accessible from command line terminals to enter
+commands and access remote version control servers to backing up and
+sharing our work.</p>
+<p>Finally, command line tools use standard protocols for passing
+parameters, inputs and outputs. This makes it easier to integrate ours
+with other command line tools, allowing us to chain them and build up
+complex and reproducible workflows and analysis pipelines using several
+programs in different steps. If we write our software in a way which
+provides such an interoperable command line interface - we will be able
+to integrate it with other command line tools to automate and speed up
+our work.</p>
 </div>
+<div class="section level3">
+<h3 id="standard-inputoutput-formats-and-communication-protocols">Standard input/output formats and communication protocols<a class="anchor" aria-label="anchor" href="#standard-inputoutput-formats-and-communication-protocols"></a></h3>
+<p>Using standard data exchange, input and output formats and
+communication protocols helps create interoperable software that can
+more readily integrate with other tools into more complex pipelines -
+increasing its interoperability and reusability.</p>
 </div>
+<div class="section level3">
+<h3 id="version-control-tools">Version control tools<a class="anchor" aria-label="anchor" href="#version-control-tools"></a></h3>
+<p>Version control means knowing what changes were made to your code,
+when and by whom - promoting code ownership, responsibility and credit.
+When combined with software sharing and collaborative platforms such as
+GitHub or GitLab, it facilitates code publication, sharing and
+findability, teamwork and discussions about software and design
+decisions, provides backup facilities for your code and speeds up
+collaboration on shared code by allowing edits by more than one person
+at a time.</p>
 </div>
+<div class="section level3">
+<h3 id="code-style-and-structure-conventions">Code style and structure conventions<a class="anchor" aria-label="anchor" href="#code-style-and-structure-conventions"></a></h3>
+<p>Following code style conventions for your programming language and
+standard code structure patterns that are agreed upon by the community
+and other programmers are important practices to ensure that others find
+it easy to read your code, reuse or extend it in their own examples and
+applications.</p>
 </div>
-<p>In this course we will use VS Code IDE, as it is free, available on
-Windows, Mac and Linux operating systems, and can be used with many
-programming languages. It is a single tool in which we can:</p>
-<ul><li>view our file system</li>
-<li>open many kinds of files</li>
-<li>edit, compile, run and debug code</li>
-<li>open a terminal to run command line tools (including version control
-tool Git) or view code outputs</li>
-</ul><p>Use VS Code to open the Python script and the data file from our
-project.</p>
-</section><section><h2 class="section-heading" id="command-line-toolshell">Command line tool/shell<a class="anchor" aria-label="anchor" href="#command-line-toolshell"></a></h2>
-<hr class="half-width"><p>In VS Code and similar IDEs you can often run the code by clicking a
-button or pressing some keyboard shortcut. If you gave your code to a
-colleague or collaborator they might use the same IDE or something
-different, so you cannot guarantee that they will have the same buttons
-and shortcuts as you.</p>
-<p>In the previous episode we mentioned that interoperable software
-should use standard protocols so that it can integrate with other tools.
-One of these standard protocols/tools is using the inputs and outputs
-via the command line terminal or shell. Command line terminal provides
-one of the oldest ways of interacting with operating system so many
-programs will have command line interfaces. Command line terminals, such
-as Bash and Zsh, have their own language syntax that allow you to write
-scripts and/or group and chain commands together to build up complex
-workflows using several programs in different steps. They also use less
-resources than a graphical user interface tool like an IDE, so are
-commonly used on high-performance computers and other shared systems
-where time, memory and processing power are expensive or in high
-demand.</p>
-<p>In this course we will use the Bash shell, which is one of the most
-common and comes already installed on Mac and Linux operating systems.
-You can create a command line interface to your program which will allow
-it to be run on any system that has a Bash shell, and allow users to
-change things like input and output files or choose different settings
-or parameters without editing your code. With a command line interface,
-your code can be built into automated workflows so that the whole
-process from data gathering to analysis to saving publication-quality
-results can be written in one Bash script and saved and reused.</p>
-</section><section><h2 class="section-heading" id="version-control">Version control<a class="anchor" aria-label="anchor" href="#version-control"></a></h2>
-<hr class="half-width"><p>Version control means knowing what changes were made to your code and
-when. Many people who have worked on large documents such as essays
-start doing this by saving files called <code>essay_draft</code>,
-<code>essay_version1.doc</code>, <code>essay_version2.doc</code>, and so
-on. This can work on a small scale but most people find it quickly gets
-confusing which version a certain change was made, or which version is
-the one that you got feedback from a supervisor on. Using a version
-control system helps you keep track of changes, including when you might
-be working on shared code being edited by more than one person at a
-time.</p>
-<p>It also lets you assign version numbers or tags to particular
-versions so you can then use those to refer back to them later. For
-example, you can run your code and output some results and add a comment
-to your output that those results were produced by version 2.4 of your
-code, so if you try to run the same thing later and find it is
-different, you can check if it is a change in the code due to using a
-newer version, or a change in the data, or something else.</p>
-<p>We will be using the Git version control system, which can be used
-through the command line terminal, in a browser or in a desktop
-application.</p>
-</section><section><h2 class="section-heading" id="code-structure-and-style-guidelines">Code structure and style guidelines<a class="anchor" aria-label="anchor" href="#code-structure-and-style-guidelines"></a></h2>
-<hr class="half-width"><p>TODO</p>
-</section><section><h2 class="section-heading" id="code-correctness">Code correctness<a class="anchor" aria-label="anchor" href="#code-correctness"></a></h2>
-<hr class="half-width"><p>Testing ensures that your code is correct and does what it is set out
+<div class="section level3">
+<h3 id="code-testing">Code testing<a class="anchor" aria-label="anchor" href="#code-testing"></a></h3>
+<p>Testing ensures that your code is correct and does what it is set out
 to do. When you write code you often feel very confident that it is
 perfect, but when writing bigger codes or code that is meant to do
 complex operations it is very hard to consider all possible edge cases
 or notice every single typing mistake. Testing also gives other people
 confidence in your code as they can see an example of how it is meant to
-run and be assured that it does work correctly on their machine.</p>
-<p>We will show different ways to test your code for different purposes.
-You need to think about what it is that is important to you and any
-future users or collaborators to decide what kind of testing is most
-useful for you.</p>
-</section><section><h2 class="section-heading" id="documentation">Documentation<a class="anchor" aria-label="anchor" href="#documentation"></a></h2>
-<hr class="half-width"><p>Documentation comes in many forms - from the names of variables and
-functions in your code, additional comments that explain some lines, up
-to a whole website full of documentation with function definitions,
-usage examples, tutorials and guides. You many not need as much
-documentation as a large commercial software product, but making your
-code reusable relies on other people being able to understand what your
-code does and how to use it.</p>
-</section><section><h2 class="section-heading" id="licences-and-citation">Licences and citation<a class="anchor" aria-label="anchor" href="#licences-and-citation"></a></h2>
-<hr class="half-width"><p>A licence states what people can legally do with your code, and what
-restrictions you have placed on it. Whenever you want to use someone
-else’s code you should check what license they have and make sure your
-use is legal. You may be restricted by your institution, your grant
-funding, or by other tools you use that require certain licenses for you
-to be compatible with them.</p>
-<p>Having a citation instructions is not a legal requirement but if you
-want to get academic credit for your work, you can make other people’s
-life much easier by telling them how you would like to be credited.
-Similarly, follow citation instructions ensures that when you use
-others’ code in your research they will be credited accordingly.</p>
-<p>Both licensing law and citation procedures can vary depending on your
-country and institution, so remember to check with a local team where
-you are. Your local research IT support or library teams would be a good
-place to start.</p>
-</section><section><h2 class="section-heading" id="code-repositories-and-registries">Code repositories and registries<a class="anchor" aria-label="anchor" href="#code-repositories-and-registries"></a></h2>
-<hr class="half-width"><p>Having somewhere to share your code is fundamental to making it
-Findable. Your institution might have a code repository, your research
-field may have a practice of sharing code via a specific website or
-journal, or your version control system might include an online
-component that makes sharing different versions of your code easy.
-Again, remember to check the rules of your institution and grant on
-publishing code, and any licenses for code you depend on or reuse.</p>
-<p>We will discuss later how to share your code on GitHub and make it
-easy for others to find and use.</p>
-</section><section><h2 class="section-heading" id="summary-of-tools-practices">Summary of tools &amp; practices<a class="anchor" aria-label="anchor" href="#summary-of-tools-practices"></a></h2>
-<hr class="half-width"><p>The table below summarises some tools and practices that can help
-with each of the FAIR software principles.</p>
-<table class="table"><colgroup><col width="67%"><col width="6%"><col width="8%"><col width="10%"><col width="6%"></colgroup><thead><tr class="header"><th>Tools and practices</th>
+run and be assured that it does work correctly on their machine -
+helping with code understanding and reusability.</p>
+</div>
+<div class="section level3">
+<h3 id="software--and-project--level-documentation">Software- and project- level documentation<a class="anchor" aria-label="anchor" href="#software--and-project--level-documentation"></a></h3>
+<p>Documentation comes in many forms - from <strong>software-level
+documentation</strong> including docstrings describing functions and
+classes and in-line comments that explain lines of your code, to
+<strong>project-level documentation</strong> and
+<strong>metadata</strong> (including README, LICENCE, CITATION,
+CONTRIBUTING, etc. files) that help to discover it, explain the legal
+terms of reusing it, describe its functionality and how to install, run
+and contribute to it, to whole websites full of documentation with
+function definitions, usage examples, tutorials and guides. You many not
+need as much documentation as a large commercial software product, but
+making your code reusable relies on other people being able to
+understand what your code does and how to use it.</p>
+</div>
+<div class="section level3">
+<h3 id="software-repositories-and-registries">Software repositories and registries<a class="anchor" aria-label="anchor" href="#software-repositories-and-registries"></a></h3>
+<p>Having somewhere to share your code is fundamental to making it
+findable and accessible. Your institution might have a code repository,
+your research field may have a practice of sharing code via a specific
+website, archive or journal, or your version control system might
+include an online component that makes sharing different versions of
+your code easy. You should check the rules or guidelines of your
+institution, grant or domain on publishing code, as well as any licenses
+of the code your software depends on or reuses.</p>
+<p>Some examples of commonly used software repositories and registries
+include:</p>
+<ul><li>general-purpose software repositories, such as <a href="https://github.com" class="external-link">GitHub</a> and <a href="https://about.gitlab.com/" class="external-link">GitLab</a>
+</li>
+<li>programming language-specific software repositories, such as <a href="https://pypi.org/" class="external-link">PyPi</a> (for Python) and <a href="https://cran.r-project.org/web/packages/" class="external-link">CRAN</a> (for R)</li>
+<li>software registries, such as <a href="https://biotools.us/" class="external-link">BioTools</a> (for biosciences) and <a href="https://github.com/NLeSC/awesome-research-software-registries" class="external-link">Awesome
+Research Software Registries</a> (providing a list of research software
+registries by country, organisation, domain and programming language)
+where research software can be registered to help promote its
+discovery</li>
+</ul></div>
+<div class="section level3">
+<h3 id="persistent-identifiers">Persistent identifiers<a class="anchor" aria-label="anchor" href="#persistent-identifiers"></a></h3>
+<p>Unique persistent identifiers, such as Digital Object Identifiers
+(DOIs) provided by <a href="https://zenodo.org/" class="external-link">Zenodo</a>, <a href="https://figshare.com/" class="external-link">FigShare</a> and similar digital archiving
+services, and commits/tags/releases used by GitHub and similar code
+sharing platforms, help with findability and accessibility of your
+software, and can help you get credit for your work by providing citable
+references.</p>
+</div>
+<div class="section level3">
+<h3 id="tools-and-practices-summary">Tools and practices summary<a class="anchor" aria-label="anchor" href="#tools-and-practices-summary"></a></h3>
+<p>The table below provides a summary of how different tools and
+practices help with the FAIR software principles.</p>
+<table class="table"><colgroup><col width="71%"><col width="5%"><col width="7%"><col width="9%"><col width="5%"></colgroup><thead><tr class="header"><th>Tools and practices</th>
 <th>Findable</th>
 <th>Accessible</th>
 <th>Interoperable</th>
 <th>Reusable</th>
-</tr></thead><tbody><tr class="odd"><td>Virtual development environments, programming language and
-dependencies - run, test, debug, share</td>
+</tr></thead><tbody><tr class="odd"><td>Virtual development environments</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
-</tr><tr class="even"><td>Integrated development environments/IDEs (e.g. VS Code, PyCharm) -
-run, test, debug</td>
+</tr><tr class="even"><td>Integrated development environments/IDEs</td>
 <td></td>
 <td></td>
 <td></td>
 <td>x</td>
-</tr><tr class="odd"><td>Command line terminal (e.g. Bash, GitBash) - reproducible
-workflows/pipelines</td>
+</tr><tr class="odd"><td>Command line terminals - automated and reproducible pipelines</td>
 <td></td>
 <td></td>
 <td>x</td>
 <td>x</td>
-</tr><tr class="even"><td>Version control tools</td>
+</tr><tr class="even"><td>Standard formats - e.g. for data exchange (CSV, YAML)</td>
+<td></td>
+<td>x</td>
+<td>x</td>
 <td>x</td>
+</tr><tr class="odd"><td>Communication protocols - Command Line Interface (CLI) or
+Application Programming Interface (API)</td>
 <td></td>
+<td>x</td>
+<td>x</td>
+<td>x</td>
+</tr><tr class="even"><td>Version control tools</td>
+<td>x</td>
 <td></td>
 <td></td>
-</tr><tr class="odd"><td>Testing - code correctness and reproducibility</td>
 <td></td>
-<td>x</td>
+</tr><tr class="odd"><td>Code testing and correctness</td>
 <td></td>
 <td>x</td>
-</tr><tr class="even"><td>Coding conventions and documentation</td>
 <td></td>
 <td>x</td>
-<td>x</td>
-<td>x</td>
-</tr><tr class="odd"><td>Explaining functionality/installation/running - README, inline
-comments and documentation</td>
+</tr><tr class="even"><td>Code style conventions</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
-</tr><tr class="even"><td>Standard formats - e.g. for data exchange (CSV, YAML)</td>
+</tr><tr class="odd"><td>Software-level documentation (comments and docstrings, explaining
+functionality)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
-</tr><tr class="odd"><td>Communication protocols - Command Line Interface (CLI) or
-Application Programming Interface (API)</td>
+</tr><tr class="even"><td>Project-level documentation (READMEs, explaining
+functionality/installation/running)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
-</tr><tr class="even"><td>License</td>
+</tr><tr class="odd"><td>License - code sharing and reuse</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
-</tr><tr class="odd"><td>Citation</td>
+</tr><tr class="even"><td>Citation - code reuse and credit</td>
 <td>x</td>
 <td></td>
 <td></td>
 <td>x</td>
-</tr><tr class="even"><td>Software repositories (e.g. GitHub, PyPi) or registries
-(e.g. BioTools)</td>
+</tr><tr class="odd"><td>Software repositories and registries - code sharing</td>
 <td>x</td>
 <td>x</td>
 <td></td>
 <td></td>
-</tr><tr class="odd"><td>Unique persistent identifier (e.g. DOIs, commits/tags/releases) -
-Zenodo, FigShare GitHub</td>
+</tr><tr class="even"><td>Unique persistent identifiers - finding and citing software</td>
 <td>x</td>
 <td>x</td>
 <td></td>
 <td></td>
-</tr></tbody></table></section><section><h2 class="section-heading" id="checking-your-setup">Checking your setup<a class="anchor" aria-label="anchor" href="#checking-your-setup"></a></h2>
-<hr class="half-width"><div id="checking-your-setup-1" class="callout challenge">
+</tr></tbody></table></div>
+<section><h2 class="section-heading" id="checking-your-setup">Checking your setup<a class="anchor" aria-label="anchor" href="#checking-your-setup"></a></h2>
+<hr class="half-width"><p>Let’s check your setup now to make sure you are ready for the rest of
+this course.</p>
+<div id="checking-your-setup-1" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
 </div>
@@ -823,7 +791,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -845,8 +813,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/03-tools.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/03-tools.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-24",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/04-version-control.html b/instructor/04-version-control.html
index 52084b40..72ba57f5 100644
--- a/instructor/04-version-control.html
+++ b/instructor/04-version-control.html
@@ -302,7 +302,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -375,7 +375,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Version control</h1>
-        <p>Last updated on 2024-09-24 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/04-version-control.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -822,14 +822,13 @@ <h3 id="rename-our-data-and-output-files">Rename our data and output files<a cla
 <ol style="list-style-type: lower-roman"><li>give our input data file and script more meaningful names and</li>
 <li>choose informative file names for our output data file and
 plot.</li>
-</ol><p>First let’s update file names in our script.</p>
+</ol><p>First let’s update file names in our script using VS Code.</p>
 <div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb26-2"><a href="#cb26-2" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb26-3"><a href="#cb26-3" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
-<span id="cb26-4"><a href="#cb26-4" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>   </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb26-2"><a href="#cb26-2" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
+<span id="cb26-3"><a href="#cb26-3" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>   </span></code></pre>
 </div>
 <p>Now, let’s actually rename our files on the file system using git and
 commit our changes.</p>
@@ -1266,7 +1265,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1288,8 +1287,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/04-version-control.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/04-version-control.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-24",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/05-code-environment.html b/instructor/05-code-environment.html
index 63edd49b..b972c4b9 100644
--- a/instructor/05-code-environment.html
+++ b/instructor/05-code-environment.html
@@ -257,6 +257,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <li><a href="#creating-virtual-environments">Creating virtual environments</a></li>
 <li><a href="#installing-external-packages">Installing external packages</a></li>
 <li><a href="#sharing-virtual-environments">Sharing virtual environments</a></li>
+<li><a href="#running-the-code">Running the code</a></li>
 <li><a href="#further-reading">Further reading</a></li>
         </ul></div><!--/div.accordion-body-->
     </div><!--/div.accordion-collapse-->
@@ -303,7 +304,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -376,7 +377,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Reproducible development environment</h1>
-        <p>Last updated on 2024-09-24 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/05-code-environment.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -799,6 +800,16 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 file accordingly by re-issuing <code>pip freeze</code> command and
 propagate the updated <code>requirements.txt</code> file to your
 collaborators via your code sharing platform.</p>
+</section><section><h2 class="section-heading" id="running-the-code">Running the code<a class="anchor" aria-label="anchor" href="#running-the-code"></a></h2>
+<hr class="half-width"><p>We are now setup to run our code from the newly created virtual
+environment:</p>
+<div class="codewrapper sourceCode" id="cb25">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py</span></code></pre>
+</div>
+<p>You should get a pop up window with a graph. Let’s inspect the code
+in a more detail, see if we can understand and improve it.</p>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a></h2>
 <hr class="half-width"><p>We recommend the following resources for some additional reading on
 the topic of this episode:</p>
@@ -866,7 +877,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -888,8 +899,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/05-code-environment.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/05-code-environment.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-24",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/06-code-readability.html b/instructor/06-code-readability.html
index ecf57805..50007a4a 100644
--- a/instructor/06-code-readability.html
+++ b/instructor/06-code-readability.html
@@ -304,7 +304,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -377,7 +377,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code readability</h1>
-        <p>Last updated on 2024-09-26 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/06-code-readability.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -485,69 +485,67 @@ <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square">
 <div class="codewrapper sourceCode" id="cb2">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a></span>
-<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb2-3"><a href="#cb2-3" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb2-4"><a href="#cb2-4" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
-<span id="cb2-5"><a href="#cb2-5" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>  </span>
-<span id="cb2-6"><a href="#cb2-6" tabindex="-1"></a></span>
-<span id="cb2-7"><a href="#cb2-7" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
-<span id="cb2-8"><a href="#cb2-8" tabindex="-1"></a></span>
-<span id="cb2-9"><a href="#cb2-9" tabindex="-1"></a>data<span class="op">=</span>[]</span>
-<span id="cb2-10"><a href="#cb2-10" tabindex="-1"></a><span class="im">import</span> json</span>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="im">import</span> json</span>
+<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="im">import</span> csv</span>
+<span id="cb2-3"><a href="#cb2-3" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
+<span id="cb2-4"><a href="#cb2-4" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb2-5"><a href="#cb2-5" tabindex="-1"></a></span>
+<span id="cb2-6"><a href="#cb2-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb2-7"><a href="#cb2-7" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb2-8"><a href="#cb2-8" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
+<span id="cb2-9"><a href="#cb2-9" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span> </span>
+<span id="cb2-10"><a href="#cb2-10" tabindex="-1"></a></span>
 <span id="cb2-11"><a href="#cb2-11" tabindex="-1"></a></span>
-<span id="cb2-12"><a href="#cb2-12" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> <span class="bu">range</span>(<span class="dv">374</span>):</span>
-<span id="cb2-13"><a href="#cb2-13" tabindex="-1"></a>    line<span class="op">=</span>data_f.readline()</span>
-<span id="cb2-14"><a href="#cb2-14" tabindex="-1"></a>    <span class="bu">print</span>(line)</span>
-<span id="cb2-15"><a href="#cb2-15" tabindex="-1"></a>    data.append(json.loads(line[<span class="dv">1</span>:<span class="op">-</span><span class="dv">1</span>]))</span>
-<span id="cb2-16"><a href="#cb2-16" tabindex="-1"></a><span class="co">#data.pop(0)</span></span>
-<span id="cb2-17"><a href="#cb2-17" tabindex="-1"></a><span class="co">## Comment out this bit if you don't want the spreadsheet</span></span>
-<span id="cb2-18"><a href="#cb2-18" tabindex="-1"></a><span class="im">import</span> csv</span>
-<span id="cb2-19"><a href="#cb2-19" tabindex="-1"></a></span>
-<span id="cb2-20"><a href="#cb2-20" tabindex="-1"></a>w<span class="op">=</span>csv.writer(data_t)</span>
-<span id="cb2-21"><a href="#cb2-21" tabindex="-1"></a></span>
-<span id="cb2-22"><a href="#cb2-22" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
-<span id="cb2-23"><a href="#cb2-23" tabindex="-1"></a></span>
-<span id="cb2-24"><a href="#cb2-24" tabindex="-1"></a>time <span class="op">=</span> []</span>
-<span id="cb2-25"><a href="#cb2-25" tabindex="-1"></a>date <span class="op">=</span>[]</span>
-<span id="cb2-26"><a href="#cb2-26" tabindex="-1"></a></span>
-<span id="cb2-27"><a href="#cb2-27" tabindex="-1"></a>j<span class="op">=</span><span class="dv">0</span></span>
-<span id="cb2-28"><a href="#cb2-28" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> data:</span>
-<span id="cb2-29"><a href="#cb2-29" tabindex="-1"></a>    <span class="bu">print</span>(data[j])</span>
-<span id="cb2-30"><a href="#cb2-30" tabindex="-1"></a>    <span class="co"># and this bit</span></span>
-<span id="cb2-31"><a href="#cb2-31" tabindex="-1"></a>    w.writerow(data[j].values())</span>
-<span id="cb2-32"><a href="#cb2-32" tabindex="-1"></a>    <span class="cf">if</span> <span class="st">'duration'</span> <span class="kw">in</span> data[j].keys():</span>
-<span id="cb2-33"><a href="#cb2-33" tabindex="-1"></a>        tt<span class="op">=</span>data[j][<span class="st">'duration'</span>]</span>
-<span id="cb2-34"><a href="#cb2-34" tabindex="-1"></a>        <span class="cf">if</span> tt <span class="op">==</span> <span class="st">''</span>:</span>
-<span id="cb2-35"><a href="#cb2-35" tabindex="-1"></a>            <span class="cf">pass</span></span>
-<span id="cb2-36"><a href="#cb2-36" tabindex="-1"></a>        <span class="cf">else</span>:</span>
-<span id="cb2-37"><a href="#cb2-37" tabindex="-1"></a>            t<span class="op">=</span>dt.datetime.strptime(tt,<span class="st">'%H:%M'</span>)</span>
-<span id="cb2-38"><a href="#cb2-38" tabindex="-1"></a>            ttt <span class="op">=</span> dt.timedelta(hours<span class="op">=</span>t.hour, minutes<span class="op">=</span>t.minute, seconds<span class="op">=</span>t.second).total_seconds()<span class="op">/</span>(<span class="dv">60</span><span class="op">*</span><span class="dv">60</span>)</span>
-<span id="cb2-39"><a href="#cb2-39" tabindex="-1"></a>            <span class="bu">print</span>(t,ttt)</span>
-<span id="cb2-40"><a href="#cb2-40" tabindex="-1"></a>            time.append(ttt)</span>
-<span id="cb2-41"><a href="#cb2-41" tabindex="-1"></a>            <span class="cf">if</span> <span class="st">'date'</span> <span class="kw">in</span> data[j].keys():</span>
-<span id="cb2-42"><a href="#cb2-42" tabindex="-1"></a>                date.append(dt.datetime.strptime(data[j][<span class="st">'date'</span>][<span class="dv">0</span>:<span class="dv">10</span>], <span class="st">'%Y-%m-</span><span class="sc">%d</span><span class="st">'</span>))</span>
-<span id="cb2-43"><a href="#cb2-43" tabindex="-1"></a>                <span class="co">#date.append(data[j]['date'][0:10])</span></span>
-<span id="cb2-44"><a href="#cb2-44" tabindex="-1"></a></span>
-<span id="cb2-45"><a href="#cb2-45" tabindex="-1"></a>            <span class="cf">else</span>:</span>
-<span id="cb2-46"><a href="#cb2-46" tabindex="-1"></a>                time.pop(<span class="dv">0</span>)</span>
-<span id="cb2-47"><a href="#cb2-47" tabindex="-1"></a>    j<span class="op">+=</span><span class="dv">1</span></span>
-<span id="cb2-48"><a href="#cb2-48" tabindex="-1"></a></span>
-<span id="cb2-49"><a href="#cb2-49" tabindex="-1"></a>t<span class="op">=</span>[<span class="dv">0</span>]</span>
-<span id="cb2-50"><a href="#cb2-50" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> time:</span>
-<span id="cb2-51"><a href="#cb2-51" tabindex="-1"></a>    t.append(t[<span class="op">-</span><span class="dv">1</span>]<span class="op">+</span>i)</span>
-<span id="cb2-52"><a href="#cb2-52" tabindex="-1"></a></span>
-<span id="cb2-53"><a href="#cb2-53" tabindex="-1"></a>date,time <span class="op">=</span> <span class="bu">zip</span>(<span class="op">*</span><span class="bu">sorted</span>(<span class="bu">zip</span>(date, time)))</span>
-<span id="cb2-54"><a href="#cb2-54" tabindex="-1"></a></span>
-<span id="cb2-55"><a href="#cb2-55" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb2-56"><a href="#cb2-56" tabindex="-1"></a></span>
-<span id="cb2-57"><a href="#cb2-57" tabindex="-1"></a>plt.plot(date,t[<span class="dv">1</span>:], <span class="st">'ko-'</span>)</span>
-<span id="cb2-58"><a href="#cb2-58" tabindex="-1"></a>plt.xlabel(<span class="st">'Year'</span>)</span>
-<span id="cb2-59"><a href="#cb2-59" tabindex="-1"></a>plt.ylabel(<span class="st">'Total time spent in space to date (hours)'</span>)</span>
-<span id="cb2-60"><a href="#cb2-60" tabindex="-1"></a>plt.tight_layout()</span>
-<span id="cb2-61"><a href="#cb2-61" tabindex="-1"></a>plt.savefig(g_file)</span>
-<span id="cb2-62"><a href="#cb2-62" tabindex="-1"></a>plt.show()</span>
-<span id="cb2-63"><a href="#cb2-63" tabindex="-1"></a></span></code></pre>
+<span id="cb2-12"><a href="#cb2-12" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
+<span id="cb2-13"><a href="#cb2-13" tabindex="-1"></a></span>
+<span id="cb2-14"><a href="#cb2-14" tabindex="-1"></a>data<span class="op">=</span>[]</span>
+<span id="cb2-15"><a href="#cb2-15" tabindex="-1"></a></span>
+<span id="cb2-16"><a href="#cb2-16" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> <span class="bu">range</span>(<span class="dv">374</span>):</span>
+<span id="cb2-17"><a href="#cb2-17" tabindex="-1"></a>    line<span class="op">=</span>data_f.readline()</span>
+<span id="cb2-18"><a href="#cb2-18" tabindex="-1"></a>    <span class="bu">print</span>(line)</span>
+<span id="cb2-19"><a href="#cb2-19" tabindex="-1"></a>    data.append(json.loads(line[<span class="dv">1</span>:<span class="op">-</span><span class="dv">1</span>]))</span>
+<span id="cb2-20"><a href="#cb2-20" tabindex="-1"></a><span class="co">#data.pop(0)</span></span>
+<span id="cb2-21"><a href="#cb2-21" tabindex="-1"></a><span class="co">## Comment out this bit if you don't want the spreadsheet</span></span>
+<span id="cb2-22"><a href="#cb2-22" tabindex="-1"></a></span>
+<span id="cb2-23"><a href="#cb2-23" tabindex="-1"></a>w<span class="op">=</span>csv.writer(data_t)</span>
+<span id="cb2-24"><a href="#cb2-24" tabindex="-1"></a></span>
+<span id="cb2-25"><a href="#cb2-25" tabindex="-1"></a>time <span class="op">=</span> []</span>
+<span id="cb2-26"><a href="#cb2-26" tabindex="-1"></a>date <span class="op">=</span>[]</span>
+<span id="cb2-27"><a href="#cb2-27" tabindex="-1"></a></span>
+<span id="cb2-28"><a href="#cb2-28" tabindex="-1"></a>j<span class="op">=</span><span class="dv">0</span></span>
+<span id="cb2-29"><a href="#cb2-29" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> data:</span>
+<span id="cb2-30"><a href="#cb2-30" tabindex="-1"></a>    <span class="bu">print</span>(data[j])</span>
+<span id="cb2-31"><a href="#cb2-31" tabindex="-1"></a>    <span class="co"># and this bit</span></span>
+<span id="cb2-32"><a href="#cb2-32" tabindex="-1"></a>    w.writerow(data[j].values())</span>
+<span id="cb2-33"><a href="#cb2-33" tabindex="-1"></a>    <span class="cf">if</span> <span class="st">'duration'</span> <span class="kw">in</span> data[j].keys():</span>
+<span id="cb2-34"><a href="#cb2-34" tabindex="-1"></a>        tt<span class="op">=</span>data[j][<span class="st">'duration'</span>]</span>
+<span id="cb2-35"><a href="#cb2-35" tabindex="-1"></a>        <span class="cf">if</span> tt <span class="op">==</span> <span class="st">''</span>:</span>
+<span id="cb2-36"><a href="#cb2-36" tabindex="-1"></a>            <span class="cf">pass</span></span>
+<span id="cb2-37"><a href="#cb2-37" tabindex="-1"></a>        <span class="cf">else</span>:</span>
+<span id="cb2-38"><a href="#cb2-38" tabindex="-1"></a>            t<span class="op">=</span>dt.datetime.strptime(tt,<span class="st">'%H:%M'</span>)</span>
+<span id="cb2-39"><a href="#cb2-39" tabindex="-1"></a>            ttt <span class="op">=</span> dt.timedelta(hours<span class="op">=</span>t.hour, minutes<span class="op">=</span>t.minute, seconds<span class="op">=</span>t.second).total_seconds()<span class="op">/</span>(<span class="dv">60</span><span class="op">*</span><span class="dv">60</span>)</span>
+<span id="cb2-40"><a href="#cb2-40" tabindex="-1"></a>            <span class="bu">print</span>(t,ttt)</span>
+<span id="cb2-41"><a href="#cb2-41" tabindex="-1"></a>            time.append(ttt)</span>
+<span id="cb2-42"><a href="#cb2-42" tabindex="-1"></a>            <span class="cf">if</span> <span class="st">'date'</span> <span class="kw">in</span> data[j].keys():</span>
+<span id="cb2-43"><a href="#cb2-43" tabindex="-1"></a>                date.append(dt.datetime.strptime(data[j][<span class="st">'date'</span>][<span class="dv">0</span>:<span class="dv">10</span>], <span class="st">'%Y-%m-</span><span class="sc">%d</span><span class="st">'</span>))</span>
+<span id="cb2-44"><a href="#cb2-44" tabindex="-1"></a>                <span class="co">#date.append(data[j]['date'][0:10])</span></span>
+<span id="cb2-45"><a href="#cb2-45" tabindex="-1"></a></span>
+<span id="cb2-46"><a href="#cb2-46" tabindex="-1"></a>            <span class="cf">else</span>:</span>
+<span id="cb2-47"><a href="#cb2-47" tabindex="-1"></a>                time.pop(<span class="dv">0</span>)</span>
+<span id="cb2-48"><a href="#cb2-48" tabindex="-1"></a>    j<span class="op">+=</span><span class="dv">1</span></span>
+<span id="cb2-49"><a href="#cb2-49" tabindex="-1"></a></span>
+<span id="cb2-50"><a href="#cb2-50" tabindex="-1"></a>t<span class="op">=</span>[<span class="dv">0</span>]</span>
+<span id="cb2-51"><a href="#cb2-51" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> time:</span>
+<span id="cb2-52"><a href="#cb2-52" tabindex="-1"></a>    t.append(t[<span class="op">-</span><span class="dv">1</span>]<span class="op">+</span>i)</span>
+<span id="cb2-53"><a href="#cb2-53" tabindex="-1"></a></span>
+<span id="cb2-54"><a href="#cb2-54" tabindex="-1"></a>date,time <span class="op">=</span> <span class="bu">zip</span>(<span class="op">*</span><span class="bu">sorted</span>(<span class="bu">zip</span>(date, time)))</span>
+<span id="cb2-55"><a href="#cb2-55" tabindex="-1"></a></span>
+<span id="cb2-56"><a href="#cb2-56" tabindex="-1"></a>plt.plot(date,t[<span class="dv">1</span>:], <span class="st">'ko-'</span>)</span>
+<span id="cb2-57"><a href="#cb2-57" tabindex="-1"></a>plt.xlabel(<span class="st">'Year'</span>)</span>
+<span id="cb2-58"><a href="#cb2-58" tabindex="-1"></a>plt.ylabel(<span class="st">'Total time spent in space to date (hours)'</span>)</span>
+<span id="cb2-59"><a href="#cb2-59" tabindex="-1"></a>plt.tight_layout()</span>
+<span id="cb2-60"><a href="#cb2-60" tabindex="-1"></a>plt.savefig(g_file)</span>
+<span id="cb2-61"><a href="#cb2-61" tabindex="-1"></a>plt.show()</span></code></pre>
 </div>
 <p>Let’s make sure we commit our changes.</p>
 <div class="codewrapper sourceCode" id="cb3">
@@ -629,7 +627,7 @@ <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
 <div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
 <div class="accordion-body">
-<p>Yes, <span class="math display">\[9.81 m/s^2 \]</span> is the <a href="https://en.wikipedia.org/wiki/Gravity_of_Earth" class="external-link">gravitational
+<p><span class="math display">\[ 9.81 m/s^2 \]</span> is the <a href="https://en.wikipedia.org/wiki/Gravity_of_Earth" class="external-link">gravitational
 force exerted by the Earth</a>. It is often referred to as “little g” to
 distinguish it from “big G” which is the <a href="https://en.wikipedia.org/wiki/Gravitational_constant" class="external-link">Gravitational
 Constant</a>. A more descriptive name for this variable therefore might
@@ -643,12 +641,12 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 </div>
 </div>
-<div id="challenge2" class="callout challenge">
+<div id="rename-our-variables-to-be-more-descriptive" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
 </div>
-<div class="callout-inner">
-<h3 class="callout-title">Challenge</h3>
+<div id="rename-our-variables-to-be-more-descriptive" class="callout-inner">
+<h3 class="callout-title">Rename our variables to be more descriptive</h3>
 <div class="callout-content">
 <p>Let’s apply this to <code>eva_data_analysis.py</code>.</p>
 <ol style="list-style-type: lower-alpha"><li>
@@ -675,16 +673,16 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <div class="codewrapper sourceCode" id="cb6">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a></span>
-<span id="cb6-2"><a href="#cb6-2" tabindex="-1"></a><span class="im">import</span> json</span>
-<span id="cb6-3"><a href="#cb6-3" tabindex="-1"></a><span class="im">import</span> csv</span>
-<span id="cb6-4"><a href="#cb6-4" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
-<span id="cb6-5"><a href="#cb6-5" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb6-6"><a href="#cb6-6" tabindex="-1"></a></span>
-<span id="cb6-7"><a href="#cb6-7" tabindex="-1"></a><span class="co"># Data source: https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb6-8"><a href="#cb6-8" tabindex="-1"></a>input_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb6-9"><a href="#cb6-9" tabindex="-1"></a>output_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>, <span class="st">'w'</span>)</span>
-<span id="cb6-10"><a href="#cb6-10" tabindex="-1"></a>graph_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span></span>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a><span class="im">import</span> json</span>
+<span id="cb6-2"><a href="#cb6-2" tabindex="-1"></a><span class="im">import</span> csv</span>
+<span id="cb6-3"><a href="#cb6-3" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
+<span id="cb6-4"><a href="#cb6-4" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb6-5"><a href="#cb6-5" tabindex="-1"></a></span>
+<span id="cb6-6"><a href="#cb6-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb6-7"><a href="#cb6-7" tabindex="-1"></a>input_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb6-8"><a href="#cb6-8" tabindex="-1"></a>output_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>, <span class="st">'w'</span>)</span>
+<span id="cb6-9"><a href="#cb6-9" tabindex="-1"></a>graph_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span></span>
+<span id="cb6-10"><a href="#cb6-10" tabindex="-1"></a></span>
 <span id="cb6-11"><a href="#cb6-11" tabindex="-1"></a></span>
 <span id="cb6-12"><a href="#cb6-12" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
 <span id="cb6-13"><a href="#cb6-13" tabindex="-1"></a></span>
@@ -987,18 +985,19 @@ <h3 class="callout-title">Callout</h3>
 <p>Looking at our code, you may notice it contains different pieces of
 functionality:</p>
 <ol style="list-style-type: decimal"><li>reading the data from a JSON file</li>
+<li>converting and saving the data in the CSV format</li>
 <li>processing/cleaning the data and preparing it for analysis</li>
 <li>data analysis and visualising the results</li>
-<li>converting and saving the data in the CSV format</li>
 </ol><p>Let’s refactor our code so that reading the data in JSON format into
 a dataframe (step 1.) and converting it and saving to the CSV format
-(step 4.) are extracted into separate functions. Let’s name those
+(step 2.) are extracted into separate functions. Let’s name those
 functions <code>read_json_to_dataframe</code> and
 <code>write_dataframe_to_csv</code> respectively. The main part of the
 script should then be simplified to invoke these new functions, while
 the functions themselves contain the complexity of each of these two
-steps.</p>
-<p>Our code may look something like the following.</p>
+steps. We will continue to work on steps 3. and 4. above later on.</p>
+<p>After the initial refactoring, our code may look something like the
+following.</p>
 <div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -1050,17 +1049,21 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <span id="cb17-46"><a href="#cb17-46" tabindex="-1"></a></span>
 <span id="cb17-47"><a href="#cb17-47" tabindex="-1"></a><span class="bu">print</span>(<span class="st">"--END--"</span>)</span></code></pre>
 </div>
-<p>We have chosen to create function for reading in and writing out data
-files since this is a very common task within research software. While
-these functions do not contain that many lines of code due to using the
-<code>pandas</code> in-built methods that do all the complex data
-reading, converting and writing operations, it can be useful to package
-these steps together into reusable functions if you need to read in or
-write out a lot of similarly structured files and process them in the
-same way.</p>
+<p>We have chosen to create functions for reading in and writing out
+data files since this is a very common task within research software.
+While these functions do not contain that many lines of code due to
+using the <code>pandas</code> in-built methods that do all the complex
+data reading, converting and writing operations, it can be useful to
+package these steps together into reusable functions if you need to read
+in or write out a lot of similarly structured files and process them in
+the same way.</p>
 </section><section><h2 class="section-heading" id="use-docstrings-to-document-functions">Use docstrings to document functions<a class="anchor" aria-label="anchor" href="#use-docstrings-to-document-functions"></a></h2>
-<hr class="half-width"><p>Docstrings are a specific type of documentation that are provided
-within functions and <a href="https://docs.python.org/3/tutorial/classes.html" class="external-link">Python
+<hr class="half-width"><p>Now that we have written some functions, it is time to document them
+so that we can quickly recall (and others looking at our code in the
+future can understand) what the functions doe without having to read the
+code.</p>
+<p><em>Docstrings</em> are a specific type of documentation that are
+provided within functions and <a href="https://docs.python.org/3/tutorial/classes.html" class="external-link">Python
 classes</a>. A function docstring should explain what that particular
 code is doing, what parameters the function needs (inputs) and what form
 they should take, what the function outputs (you may see words like
@@ -1358,7 +1361,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1380,8 +1383,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/06-code-readability.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/06-code-readability.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/07-code-structure.html b/instructor/07-code-structure.html
index 244f1206..cda5bc75 100644
--- a/instructor/07-code-structure.html
+++ b/instructor/07-code-structure.html
@@ -301,7 +301,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -374,7 +374,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code structure</h1>
-        <p>Last updated on 2024-09-26 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/07-code-structure.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -395,7 +395,7 @@ <h2 class="card-header">Overview</h2>
 <div class="card-body">
 <div class="inner">
 <h3 class="card-title">Questions</h3>
-<ul><li>How can we bests structure code?</li>
+<ul><li>How can we best structure code?</li>
 <li>What is a common code structure (pattern) for creating software that
 can read input from command line?</li>
 <li>What are conventional places to store data, code, results, tests,
@@ -659,7 +659,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 set by the Python interpreter before the execution of any code in the
 source file. What value is given by the interpreter to
 <code>__name__</code> is determined by the manner in which the script is
-loaded.</p>
+invoked.</p>
 <p>If we run the source file directly using the Python interpreter,
 e.g.:</p>
 <div class="codewrapper sourceCode" id="cb5">
@@ -684,7 +684,8 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="im">import</span> eva_data_analysis</span></code></pre>
 </div>
 <p>then the Python interpreter will assign the name “eva_data_analysis”
-from the import statement to the <code>__name__</code> variable:</p>
+from the import statement to the <code>__name__</code> variable (note
+that import statement matches our script’s name):</p>
 <div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -701,7 +702,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 another script, there are a number of situations in which you would want
 to do this:</p>
 <ul><li>for testing of your code, you can have your testing framework import
-the main script, and run special test functions which then call the
+your script, and run special test functions which then call the
 <code>main</code> function directly;</li>
 <li>where you want to not only be able to run your script from the
 command-line, but also provide a programmer-friendly application
@@ -842,7 +843,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python eva_data_analysis.py eva_data.json eva_data.csv</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python eva_data_analysis.py eva-data.json eva-data.csv</span></code></pre>
 </div>
 <p>Remember to commit our changes.</p>
 <div class="codewrapper sourceCode" id="cb11">
@@ -895,7 +896,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <ul><li>Code and data should be version controlled; you can also version
 control manuscripts, results, etc.</li>
 <li>If data files are too large (or contain sensitive information) to
-track by version control, untrack them using .gitignore</li>
+track by version control, untrack them using
+<code>.gitignore</code>
+</li>
 <li>Use tags/releases to mark specific versions of results (a version
 submitted to a journal, dissertation version, poster version, etc.) so
 as to avoid using version numbers in file names and proliferation of
@@ -935,7 +938,8 @@ <h3 class="callout-title">Challenge</h3>
 <div class="callout-content">
 <p>Refactor your software project so that input data is stored in
 <code>data/</code> directory and results (the graph and CSV data files)
-saved in <code>results/</code> directory.</p>
+saved in <code>results/</code> directory. Remember to create the
+<code>results/</code> directory or your code will fail.</p>
 </div>
 </div>
 </div>
@@ -1076,20 +1080,13 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 </div>
 </div>
-<p>After the above exercise, you will be invoking your script from
-command line as:</p>
-<div class="codewrapper sourceCode" id="cb14">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python data/eva_data_analysis.py eva_data.json results/eva_data.csv</span></code></pre>
-</div>
 <p>Remember to commit your latest changes:</p>
-<div class="codewrapper sourceCode" id="cb15">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git status</span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add eva_data_analysis.py data results</span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Update project's directory structure"</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git status</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add eva_data_analysis.py data results</span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Update project's directory structure"</span></span></code></pre>
 </div>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a></h2>
 <hr class="half-width"><p>We recommend the following resources for some additional reading on
@@ -1155,7 +1152,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1177,8 +1174,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/07-code-structure.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/07-code-structure.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/08-code-correctness.html b/instructor/08-code-correctness.html
index 9f25e817..f7a599f7 100644
--- a/instructor/08-code-correctness.html
+++ b/instructor/08-code-correctness.html
@@ -306,7 +306,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -379,7 +379,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code correctness</h1>
-        <p>Last updated on 2024-09-26 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/08-code-correctness.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -551,7 +551,7 @@ <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </div>
 </section><section><h2 class="section-heading" id="informal-testing">Informal testing<a class="anchor" aria-label="anchor" href="#informal-testing"></a></h2>
 <hr class="half-width"><p>How should we test our code? One approach is to copy/paste the code
-or a function into a Python terminal (different from command line
+or a function into a Python terminal (different from a command line
 terminal), which allows you to interact with the Python interpreter more
 directly.<br>
 From the Python terminal we can then run one function or a piece of code
@@ -686,35 +686,29 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <li>Are recorded in a test script that can be re-run on demand.</li>
 </ul><p>Let’s explore this process by writing some formal tests for our
 <code>text_to_duration</code> function.</p>
-<p>Let’s create a new Python file <code>test_code.py</code> in the root
-of our project directory to store our tests.</p>
-<div class="codewrapper sourceCode" id="cb7">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> cd spacewalks</span>
-<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch test_code.py</span></code></pre>
-</div>
+<p>In VS Code, create a new Python file <code>test_code.py</code> in the
+root of our project directory to store our tests.</p>
 <p>Like before in the Python terminal, we need to import
 <code>text_to_duration</code> into our test script. Then, we add our
 first test function:</p>
-<div class="codewrapper sourceCode" id="cb8">
+<div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a></span>
-<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a></span>
-<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a>    input_value <span class="op">=</span> <span class="st">"10:00"</span></span>
-<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a>    test_result <span class="op">=</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>    <span class="bu">print</span>(<span class="ss">f"text_to_duration('10:00') == 10? </span><span class="sc">{</span>test_result<span class="sc">}</span><span class="ss">"</span>)</span>
-<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a></span>
-<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a>test_text_to_duration()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a></span>
+<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb7-3"><a href="#cb7-3" tabindex="-1"></a></span>
+<span id="cb7-4"><a href="#cb7-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb7-5"><a href="#cb7-5" tabindex="-1"></a>    input_value <span class="op">=</span> <span class="st">"10:00"</span></span>
+<span id="cb7-6"><a href="#cb7-6" tabindex="-1"></a>    test_result <span class="op">=</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb7-7"><a href="#cb7-7" tabindex="-1"></a>    <span class="bu">print</span>(<span class="ss">f"text_to_duration('10:00') == 10? </span><span class="sc">{</span>test_result<span class="sc">}</span><span class="ss">"</span>)</span>
+<span id="cb7-8"><a href="#cb7-8" tabindex="-1"></a></span>
+<span id="cb7-9"><a href="#cb7-9" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <p>We can run this code from the command line terminal as:</p>
-<div class="codewrapper sourceCode" id="cb9">
+<div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span><span class="ex">$</span> python3 test_code.py </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span><span class="ex">$</span> python3 test_code.py </span></code></pre>
 </div>
 <p>This test checks that when we apply <code>text_to_duration</code> to
 input value <code>10:00</code>, the output matches the expected value of
@@ -735,16 +729,16 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <code>False</code>, <code>assert</code> raises an
 <code>AssertError</code>.</p>
 <p>Let’s rewrite our test with an <code>assert</code> statement:</p>
-<div class="codewrapper sourceCode" id="cb10">
+<div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a></span>
-<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a></span>
-<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a></span>
-<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a></span>
+<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a></span>
+<span id="cb9-4"><a href="#cb9-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb9-5"><a href="#cb9-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb9-6"><a href="#cb9-6" tabindex="-1"></a></span>
+<span id="cb9-7"><a href="#cb9-7" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <p>Notice that when we run <code>test_text_to_duration_integer()</code>,
 nothing happens - there is no output. That is because our function is
@@ -752,75 +746,78 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <p>Let’s add another test to check what happens when duration is not an
 integer number and if our function can handle durations with a non-zero
 minute component, and rerun our test code.</p>
-<div class="codewrapper sourceCode" id="cb11">
+<div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb11-2"><a href="#cb11-2" tabindex="-1"></a></span>
-<span id="cb11-3"><a href="#cb11-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb11-4"><a href="#cb11-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:15"</span>) <span class="op">==</span> <span class="fl">10.25</span></span>
-<span id="cb11-5"><a href="#cb11-5" tabindex="-1"></a></span>
-<span id="cb11-6"><a href="#cb11-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb11-7"><a href="#cb11-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb11-8"><a href="#cb11-8" tabindex="-1"></a></span>
-<span id="cb11-9"><a href="#cb11-9" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb11-10"><a href="#cb11-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a></span>
+<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:15"</span>) <span class="op">==</span> <span class="fl">10.25</span></span>
+<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a></span>
+<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb10-8"><a href="#cb10-8" tabindex="-1"></a></span>
+<span id="cb10-9"><a href="#cb10-9" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb10-10"><a href="#cb10-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="error" tabindex="0"><code>(venv_spacewalks) $ python3 test_code.py
 Traceback (most recent call last):
-  File "/Users/user/work/SSI/lessons/astronaut-data-analysis/test_code.py", line 12, in &lt;module&gt;
+  File "/Users/user/Desktop/spacewalks/test_code.py", line 9, in &lt;module&gt;
     test_text_to_duration_float()
-  File "/Users/user/work/SSI/lessons/astronaut-data-analysis/test_code.py", line 5, in test_text_to_duration_float
+  File "/Users/user/Desktop/spacewalks/test_code.py", line 4, in test_text_to_duration_float
     assert text_to_duration("10:15") == 10.25
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-AssertionError
-</code></pre>
+AssertionError</code></pre>
 </div>
 <p>Notice that this time, our test
 <code>test_text_to_duration_float</code> fails. Our assert statement has
 raised an <code>AssertionError</code> - a clear signal that there is a
-problem in our code that we need to fix. Python helpfully tells us which
-line of our code is problematic:</p>
-<div class="codewrapper sourceCode" id="cb13">
+problem in our code that we need to fix. We know that duration
+<code>10:15</code> should be converted to number <code>10.25</code>.
+What is wrong with our code? If we look at our
+<code>text_to_duration</code> function, we may identify the following
+line of our code as problematic:</p>
+<div class="codewrapper sourceCode" id="cb12">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a>...</span>
-<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span> </span>
-<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="kw">def</span> text_to_duration(duration):</span>
+<span id="cb12-2"><a href="#cb12-2" tabindex="-1"></a>    ...</span>
+<span id="cb12-3"><a href="#cb12-3" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span> </span>
+<span id="cb12-4"><a href="#cb12-4" tabindex="-1"></a>    ...</span></code></pre>
 </div>
 <p>You may notice that our conversion code is wrong - the minutes
 component should have been divided by 60 and not 6. We were able to spot
 this tiny bug by testing our code.</p>
 <p>Let’s fix the problematic line and rerun out tests.</p>
-<div class="codewrapper sourceCode" id="cb14">
+<div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a>...</span>
-<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">60</span> </span>
-<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a>...</span>
+<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">60</span> </span>
+<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a>...</span></code></pre>
 </div>
 <p>This time our tests run without problem.</p>
 <p>Should we add more tests or the tests we have so far are enough? What
-happens if our duration value is <code>01:20</code> (one hour and 20
-minutes) and our result is not a rational floating point number like
-<code>10.25</code> but an irrational number such as
+happens if our duration value is <code>10:20</code> (ten hours and 20
+minutes) and our result is not a rational floating point number (like
+<code>10.25</code>) but an irrational number such as
 <code>10.333333333</code>? Let’s tests for this.</p>
-<div class="codewrapper sourceCode" id="cb15">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a></span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> <span class="fl">10.333333</span></span>
-<span id="cb15-5"><a href="#cb15-5" tabindex="-1"></a></span>
-<span id="cb15-6"><a href="#cb15-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb15-7"><a href="#cb15-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb15-8"><a href="#cb15-8" tabindex="-1"></a></span>
-<span id="cb15-9"><a href="#cb15-9" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb15-10"><a href="#cb15-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a></span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb14-4"><a href="#cb14-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> <span class="fl">10.333333</span></span>
+<span id="cb14-5"><a href="#cb14-5" tabindex="-1"></a></span>
+<span id="cb14-6"><a href="#cb14-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb14-7"><a href="#cb14-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb14-8"><a href="#cb14-8" tabindex="-1"></a></span>
+<span id="cb14-9"><a href="#cb14-9" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb14-10"><a href="#cb14-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -840,13 +837,13 @@ <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></
 (<code>==</code>) to compare the equality of floating point numbers.
 Instead, we check that our floating point numbers are equal within a
 very small tolerance (e.g. 1e-5). Hence, our code should look like:</p>
-<div class="codewrapper sourceCode" id="cb17">
+<div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a>...</span>
-<span id="cb17-2"><a href="#cb17-2" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb17-3"><a href="#cb17-3" tabindex="-1"></a>    <span class="cf">assert</span> <span class="bu">abs</span>(text_to_duration(<span class="st">"10:20"</span>) <span class="op">-</span> <span class="fl">10.33333333</span>) <span class="op">&lt;</span> <span class="fl">1e-5</span></span>
-<span id="cb17-4"><a href="#cb17-4" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a>...</span>
+<span id="cb16-2"><a href="#cb16-2" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb16-3"><a href="#cb16-3" tabindex="-1"></a>    <span class="cf">assert</span> <span class="bu">abs</span>(text_to_duration(<span class="st">"10:20"</span>) <span class="op">-</span> <span class="fl">10.33333333</span>) <span class="op">&lt;</span> <span class="fl">1e-5</span></span>
+<span id="cb16-4"><a href="#cb16-4" tabindex="-1"></a>...</span></code></pre>
 </div>
 <p>You may have noticed that we have to repeat a lot of code to add each
 individual test for each test case. You may also have noticed that our
@@ -865,10 +862,10 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 code coverage extension <code>pytest-cov</code>. To install these
 libraries into our virtual environment, from the command line terminal
 do:</p>
-<div class="codewrapper sourceCode" id="cb18">
+<div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip install pytest pytest-cov</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip install pytest pytest-cov</span></code></pre>
 </div>
 <p>Let’s make sure that our tests are ready to work with
 <code>pytest</code>.</p>
@@ -880,12 +877,12 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 requirements, so there is nothing to do here. However, our script does
 contain lines to run each of our test functions. These are no-longer
 required as pytest will run our tests so we can remove them:</p>
-<div class="codewrapper sourceCode" id="cb19">
+<div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="co"># Delete these 2 lines</span></span>
-<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="co"># Delete these 2 lines</span></span>
+<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 </li>
 <li><p>It is also conventional when working with a testing framework to
@@ -897,55 +894,57 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 test suite is currently located in the root folder of our project. Let’s
 move it to a dedicated test folder and rename our
 <code>test_code.py</code> file to <code>test_eva_analysis.py</code>.</p>
-<div class="codewrapper sourceCode" id="cb20">
+<p>You can do it from VS Code or by typing the following commands in the
+command line terminal:</p>
+<div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir tests</span>
-<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mv test_code.py tests/test_eva_analysis.py</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir tests</span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mv test_code.py tests/test_eva_analysis.py</span></code></pre>
 </div>
 <p>Before we re-run our tests using <code>pytest</code>, let’s update
 our second test to use <code>pytest</code>’s function
 <code>approx()</code> which is specifically intended for comparing
 floating point numbers within a tolerance.</p>
-<div class="codewrapper sourceCode" id="cb21">
+<div class="codewrapper sourceCode" id="cb20">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a></span>
-<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> pytest.approx(<span class="fl">10.33333333</span>)</span>
-<span id="cb21-6"><a href="#cb21-6" tabindex="-1"></a></span>
-<span id="cb21-7"><a href="#cb21-7" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb21-8"><a href="#cb21-8" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb20-3"><a href="#cb20-3" tabindex="-1"></a></span>
+<span id="cb20-4"><a href="#cb20-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb20-5"><a href="#cb20-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> pytest.approx(<span class="fl">10.33333333</span>)</span>
+<span id="cb20-6"><a href="#cb20-6" tabindex="-1"></a></span>
+<span id="cb20-7"><a href="#cb20-7" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb20-8"><a href="#cb20-8" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span></code></pre>
 </div>
 <p>Let’s also add some inline comments to clarify what each test is
 doing and expand our syntax to highlight the logic behind our
 approach:</p>
-<div class="codewrapper sourceCode" id="cb22">
+<div class="codewrapper sourceCode" id="cb21">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a></span>
-<span id="cb22-4"><a href="#cb22-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb22-5"><a href="#cb22-5" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb22-6"><a href="#cb22-6" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
-<span id="cb22-7"><a href="#cb22-7" tabindex="-1"></a><span class="co">    for typical durations with a non-zero minute component</span></span>
-<span id="cb22-8"><a href="#cb22-8" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb22-9"><a href="#cb22-9" tabindex="-1"></a>    actual_result <span class="op">=</span> text_to_duration(<span class="st">"10:20"</span>) </span>
-<span id="cb22-10"><a href="#cb22-10" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="fl">10.33333333</span></span>
-<span id="cb22-11"><a href="#cb22-11" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> pytest.approx(expected_result)</span>
-<span id="cb22-12"><a href="#cb22-12" tabindex="-1"></a>    </span>
-<span id="cb22-13"><a href="#cb22-13" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb22-14"><a href="#cb22-14" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb22-15"><a href="#cb22-15" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
-<span id="cb22-16"><a href="#cb22-16" tabindex="-1"></a><span class="co">    for typical whole hour durations </span></span>
-<span id="cb22-17"><a href="#cb22-17" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb22-18"><a href="#cb22-18" tabindex="-1"></a>    actual_result <span class="op">=</span>  text_to_duration(<span class="st">"10:00"</span>)</span>
-<span id="cb22-19"><a href="#cb22-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">10</span></span>
-<span id="cb22-20"><a href="#cb22-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb22-21"><a href="#cb22-21" tabindex="-1"></a>    </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a></span>
+<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb21-6"><a href="#cb21-6" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
+<span id="cb21-7"><a href="#cb21-7" tabindex="-1"></a><span class="co">    for typical durations with a non-zero minute component</span></span>
+<span id="cb21-8"><a href="#cb21-8" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb21-9"><a href="#cb21-9" tabindex="-1"></a>    actual_result <span class="op">=</span> text_to_duration(<span class="st">"10:20"</span>) </span>
+<span id="cb21-10"><a href="#cb21-10" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="fl">10.33333333</span></span>
+<span id="cb21-11"><a href="#cb21-11" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> pytest.approx(expected_result)</span>
+<span id="cb21-12"><a href="#cb21-12" tabindex="-1"></a>    </span>
+<span id="cb21-13"><a href="#cb21-13" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb21-14"><a href="#cb21-14" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb21-15"><a href="#cb21-15" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
+<span id="cb21-16"><a href="#cb21-16" tabindex="-1"></a><span class="co">    for typical whole hour durations </span></span>
+<span id="cb21-17"><a href="#cb21-17" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb21-18"><a href="#cb21-18" tabindex="-1"></a>    actual_result <span class="op">=</span>  text_to_duration(<span class="st">"10:00"</span>)</span>
+<span id="cb21-19"><a href="#cb21-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">10</span></span>
+<span id="cb21-20"><a href="#cb21-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb21-21"><a href="#cb21-21" tabindex="-1"></a>    </span></code></pre>
 </div>
 <p>Writing our tests this way highlights the key idea that each test
 should compare the actual results returned by our function with expected
@@ -953,23 +952,23 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <p>Similarly, writing inline comments for our tests that complete the
 sentence “Test that …” helps us to understand what each test is doing
 and why it is needed.</p>
-<p>Before running out tests with <code>putest</code>, let’s reintroduce
+<p>Before running out tests with <code>pytest</code>, let’s reintroduce
 our old bug in function <code>text_to_duration</code> that affects the
 durations with a non-zero minute component like “10:20” but not those
 that are whole hours, e.g. “10:00”:</p>
-<div class="codewrapper sourceCode" id="cb23">
+<div class="codewrapper sourceCode" id="cb22">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a>    ...</span>
-<span id="cb23-2"><a href="#cb23-2" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span>  <span class="co"># Divide by 6 instead of 60</span></span>
-<span id="cb23-3"><a href="#cb23-3" tabindex="-1"></a>    ...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a>    ...</span>
+<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span>  <span class="co"># Divide by 6 instead of 60</span></span>
+<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a>    ...</span></code></pre>
 </div>
 <p>Finally, let’s run our tests with <code>pytest</code> from our
 project’s root directory (and not <code>tests</code> directory):</p>
-<div class="codewrapper sourceCode" id="cb24">
+<div class="codewrapper sourceCode" id="cb23">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest </span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1022,6 +1021,7 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 
 =========================================== 2 passed in 0.63s =============================================</code></pre>
 </div>
+<p>This time, all out tests passed.</p>
 <div id="interpreting-pytest-output" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
@@ -1134,70 +1134,70 @@ <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 that alone is not enough to properly test code. We will now look into
 what makes a good test suite and good practices for testing code.</p>
 <p>Let’s start by considering the following scenario. A collaborator on
-our project has sent us the following code which adds a new column to
-our data containing the <code>crew_size</code> values capturing the
-number of astronauts participating in any given spacewalk. How do we
-know that it works as intended and that it will not break the rest of
-our code? For this, we need to write a test suite with a comprehensive
-coverage of the new code.</p>
-<div class="codewrapper sourceCode" id="cb28">
+our project has sent us the following code which adds a new column
+called <code>crew_size</code> to our data containing the number of
+astronauts participating in any given spacewalk. How do we know that it
+works as intended and that it will not break the rest of our code? For
+this, we need to write a test suite with a comprehensive coverage of the
+new code.</p>
+<div class="codewrapper sourceCode" id="cb27">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb28-1"><a href="#cb28-1" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb28-2"><a href="#cb28-2" tabindex="-1"></a><span class="im">import</span> pandas <span class="im">as</span> pd</span>
-<span id="cb28-3"><a href="#cb28-3" tabindex="-1"></a><span class="im">import</span> sys</span>
-<span id="cb28-4"><a href="#cb28-4" tabindex="-1"></a><span class="im">import</span> re <span class="co"># added this line</span></span>
-<span id="cb28-5"><a href="#cb28-5" tabindex="-1"></a></span>
-<span id="cb28-6"><a href="#cb28-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb28-7"><a href="#cb28-7" tabindex="-1"></a></span>
-<span id="cb28-8"><a href="#cb28-8" tabindex="-1"></a><span class="kw">def</span> main(input_file, output_file, graph_file):</span>
-<span id="cb28-9"><a href="#cb28-9" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--START--"</span>)</span>
-<span id="cb28-10"><a href="#cb28-10" tabindex="-1"></a></span>
-<span id="cb28-11"><a href="#cb28-11" tabindex="-1"></a>    eva_data <span class="op">=</span> read_json_to_dataframe(input_file)</span>
-<span id="cb28-12"><a href="#cb28-12" tabindex="-1"></a></span>
-<span id="cb28-13"><a href="#cb28-13" tabindex="-1"></a>    eva_data <span class="op">=</span> add_crew_size_column(eva_data) <span class="co"># added this line</span></span>
-<span id="cb28-14"><a href="#cb28-14" tabindex="-1"></a></span>
-<span id="cb28-15"><a href="#cb28-15" tabindex="-1"></a>    write_dataframe_to_csv(eva_data, output_file)</span>
-<span id="cb28-16"><a href="#cb28-16" tabindex="-1"></a></span>
-<span id="cb28-17"><a href="#cb28-17" tabindex="-1"></a>    plot_cumulative_time_in_space(eva_data, graph_file)</span>
-<span id="cb28-18"><a href="#cb28-18" tabindex="-1"></a></span>
-<span id="cb28-19"><a href="#cb28-19" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--END--"</span>)</span>
-<span id="cb28-20"><a href="#cb28-20" tabindex="-1"></a></span>
-<span id="cb28-21"><a href="#cb28-21" tabindex="-1"></a>... </span>
-<span id="cb28-22"><a href="#cb28-22" tabindex="-1"></a></span>
-<span id="cb28-23"><a href="#cb28-23" tabindex="-1"></a><span class="kw">def</span> calculate_crew_size(crew):</span>
-<span id="cb28-24"><a href="#cb28-24" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb28-25"><a href="#cb28-25" tabindex="-1"></a><span class="co">    Calculate the size of the crew for a single crew entry</span></span>
-<span id="cb28-26"><a href="#cb28-26" tabindex="-1"></a></span>
-<span id="cb28-27"><a href="#cb28-27" tabindex="-1"></a><span class="co">    Args:</span></span>
-<span id="cb28-28"><a href="#cb28-28" tabindex="-1"></a><span class="co">        crew (str): The text entry in the crew column containing a list of crew member names</span></span>
-<span id="cb28-29"><a href="#cb28-29" tabindex="-1"></a></span>
-<span id="cb28-30"><a href="#cb28-30" tabindex="-1"></a><span class="co">    Returns:</span></span>
-<span id="cb28-31"><a href="#cb28-31" tabindex="-1"></a><span class="co">        int: The crew size</span></span>
-<span id="cb28-32"><a href="#cb28-32" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb28-33"><a href="#cb28-33" tabindex="-1"></a>    <span class="cf">if</span> crew.split() <span class="op">==</span> []:</span>
-<span id="cb28-34"><a href="#cb28-34" tabindex="-1"></a>        <span class="cf">return</span> <span class="va">None</span></span>
-<span id="cb28-35"><a href="#cb28-35" tabindex="-1"></a>    <span class="cf">else</span>:</span>
-<span id="cb28-36"><a href="#cb28-36" tabindex="-1"></a>        <span class="cf">return</span> <span class="bu">len</span>(re.split(<span class="vs">r';'</span>, crew))<span class="op">-</span><span class="dv">1</span></span>
-<span id="cb28-37"><a href="#cb28-37" tabindex="-1"></a></span>
-<span id="cb28-38"><a href="#cb28-38" tabindex="-1"></a><span class="kw">def</span> add_crew_size_column(df):</span>
-<span id="cb28-39"><a href="#cb28-39" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb28-40"><a href="#cb28-40" tabindex="-1"></a><span class="co">    Add crew_size column to the dataset containing the value of the crew size</span></span>
-<span id="cb28-41"><a href="#cb28-41" tabindex="-1"></a></span>
-<span id="cb28-42"><a href="#cb28-42" tabindex="-1"></a><span class="co">    Args:</span></span>
-<span id="cb28-43"><a href="#cb28-43" tabindex="-1"></a><span class="co">        df (pd.DataFrame): The input data frame.</span></span>
-<span id="cb28-44"><a href="#cb28-44" tabindex="-1"></a></span>
-<span id="cb28-45"><a href="#cb28-45" tabindex="-1"></a><span class="co">    Returns:</span></span>
-<span id="cb28-46"><a href="#cb28-46" tabindex="-1"></a><span class="co">        df_copy (pd.DataFrame): A copy of df with the new crew_size variable added</span></span>
-<span id="cb28-47"><a href="#cb28-47" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb28-48"><a href="#cb28-48" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">'Adding crew size variable (crew_size) to dataset'</span>)</span>
-<span id="cb28-49"><a href="#cb28-49" tabindex="-1"></a>    df_copy <span class="op">=</span> df.copy()</span>
-<span id="cb28-50"><a href="#cb28-50" tabindex="-1"></a>    df_copy[<span class="st">"crew_size"</span>] <span class="op">=</span> df_copy[<span class="st">"crew"</span>].<span class="bu">apply</span>(</span>
-<span id="cb28-51"><a href="#cb28-51" tabindex="-1"></a>        calculate_crew_size</span>
-<span id="cb28-52"><a href="#cb28-52" tabindex="-1"></a>    )</span>
-<span id="cb28-53"><a href="#cb28-53" tabindex="-1"></a>    <span class="cf">return</span> df_copy</span>
-<span id="cb28-54"><a href="#cb28-54" tabindex="-1"></a>...</span>
-<span id="cb28-55"><a href="#cb28-55" tabindex="-1"></a>    </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb27-2"><a href="#cb27-2" tabindex="-1"></a><span class="im">import</span> pandas <span class="im">as</span> pd</span>
+<span id="cb27-3"><a href="#cb27-3" tabindex="-1"></a><span class="im">import</span> sys</span>
+<span id="cb27-4"><a href="#cb27-4" tabindex="-1"></a><span class="im">import</span> re <span class="co"># added this line</span></span>
+<span id="cb27-5"><a href="#cb27-5" tabindex="-1"></a></span>
+<span id="cb27-6"><a href="#cb27-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb27-7"><a href="#cb27-7" tabindex="-1"></a></span>
+<span id="cb27-8"><a href="#cb27-8" tabindex="-1"></a><span class="kw">def</span> main(input_file, output_file, graph_file):</span>
+<span id="cb27-9"><a href="#cb27-9" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--START--"</span>)</span>
+<span id="cb27-10"><a href="#cb27-10" tabindex="-1"></a></span>
+<span id="cb27-11"><a href="#cb27-11" tabindex="-1"></a>    eva_data <span class="op">=</span> read_json_to_dataframe(input_file)</span>
+<span id="cb27-12"><a href="#cb27-12" tabindex="-1"></a></span>
+<span id="cb27-13"><a href="#cb27-13" tabindex="-1"></a>    eva_data <span class="op">=</span> add_crew_size_column(eva_data) <span class="co"># added this line</span></span>
+<span id="cb27-14"><a href="#cb27-14" tabindex="-1"></a></span>
+<span id="cb27-15"><a href="#cb27-15" tabindex="-1"></a>    write_dataframe_to_csv(eva_data, output_file)</span>
+<span id="cb27-16"><a href="#cb27-16" tabindex="-1"></a></span>
+<span id="cb27-17"><a href="#cb27-17" tabindex="-1"></a>    plot_cumulative_time_in_space(eva_data, graph_file)</span>
+<span id="cb27-18"><a href="#cb27-18" tabindex="-1"></a></span>
+<span id="cb27-19"><a href="#cb27-19" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--END--"</span>)</span>
+<span id="cb27-20"><a href="#cb27-20" tabindex="-1"></a></span>
+<span id="cb27-21"><a href="#cb27-21" tabindex="-1"></a>... </span>
+<span id="cb27-22"><a href="#cb27-22" tabindex="-1"></a></span>
+<span id="cb27-23"><a href="#cb27-23" tabindex="-1"></a><span class="kw">def</span> calculate_crew_size(crew):</span>
+<span id="cb27-24"><a href="#cb27-24" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb27-25"><a href="#cb27-25" tabindex="-1"></a><span class="co">    Calculate the size of the crew for a single crew entry</span></span>
+<span id="cb27-26"><a href="#cb27-26" tabindex="-1"></a></span>
+<span id="cb27-27"><a href="#cb27-27" tabindex="-1"></a><span class="co">    Args:</span></span>
+<span id="cb27-28"><a href="#cb27-28" tabindex="-1"></a><span class="co">        crew (str): The text entry in the crew column containing a list of crew member names</span></span>
+<span id="cb27-29"><a href="#cb27-29" tabindex="-1"></a></span>
+<span id="cb27-30"><a href="#cb27-30" tabindex="-1"></a><span class="co">    Returns:</span></span>
+<span id="cb27-31"><a href="#cb27-31" tabindex="-1"></a><span class="co">        int: The crew size</span></span>
+<span id="cb27-32"><a href="#cb27-32" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb27-33"><a href="#cb27-33" tabindex="-1"></a>    <span class="cf">if</span> crew.split() <span class="op">==</span> []:</span>
+<span id="cb27-34"><a href="#cb27-34" tabindex="-1"></a>        <span class="cf">return</span> <span class="va">None</span></span>
+<span id="cb27-35"><a href="#cb27-35" tabindex="-1"></a>    <span class="cf">else</span>:</span>
+<span id="cb27-36"><a href="#cb27-36" tabindex="-1"></a>        <span class="cf">return</span> <span class="bu">len</span>(re.split(<span class="vs">r';'</span>, crew))<span class="op">-</span><span class="dv">1</span></span>
+<span id="cb27-37"><a href="#cb27-37" tabindex="-1"></a></span>
+<span id="cb27-38"><a href="#cb27-38" tabindex="-1"></a><span class="kw">def</span> add_crew_size_column(df):</span>
+<span id="cb27-39"><a href="#cb27-39" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb27-40"><a href="#cb27-40" tabindex="-1"></a><span class="co">    Add crew_size column to the dataset containing the value of the crew size</span></span>
+<span id="cb27-41"><a href="#cb27-41" tabindex="-1"></a></span>
+<span id="cb27-42"><a href="#cb27-42" tabindex="-1"></a><span class="co">    Args:</span></span>
+<span id="cb27-43"><a href="#cb27-43" tabindex="-1"></a><span class="co">        df (pd.DataFrame): The input data frame.</span></span>
+<span id="cb27-44"><a href="#cb27-44" tabindex="-1"></a></span>
+<span id="cb27-45"><a href="#cb27-45" tabindex="-1"></a><span class="co">    Returns:</span></span>
+<span id="cb27-46"><a href="#cb27-46" tabindex="-1"></a><span class="co">        df_copy (pd.DataFrame): A copy of df with the new crew_size variable added</span></span>
+<span id="cb27-47"><a href="#cb27-47" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb27-48"><a href="#cb27-48" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">'Adding crew size variable (crew_size) to dataset'</span>)</span>
+<span id="cb27-49"><a href="#cb27-49" tabindex="-1"></a>    df_copy <span class="op">=</span> df.copy()</span>
+<span id="cb27-50"><a href="#cb27-50" tabindex="-1"></a>    df_copy[<span class="st">"crew_size"</span>] <span class="op">=</span> df_copy[<span class="st">"crew"</span>].<span class="bu">apply</span>(</span>
+<span id="cb27-51"><a href="#cb27-51" tabindex="-1"></a>        calculate_crew_size</span>
+<span id="cb27-52"><a href="#cb27-52" tabindex="-1"></a>    )</span>
+<span id="cb27-53"><a href="#cb27-53" tabindex="-1"></a>    <span class="cf">return</span> df_copy</span>
+<span id="cb27-54"><a href="#cb27-54" tabindex="-1"></a>...</span>
+<span id="cb27-55"><a href="#cb27-55" tabindex="-1"></a>    </span></code></pre>
 </div>
 <div class="section level3">
 <h3 id="writing-good-tests">Writing good tests<a class="anchor" aria-label="anchor" href="#writing-good-tests"></a></h3>
@@ -1248,38 +1248,44 @@ <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
 <div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
 <div class="accordion-body">
 <p>We can add the following test functions to out test suite.</p>
-<div class="codewrapper sourceCode" id="cb30">
+<div class="codewrapper sourceCode" id="cb29">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb30-2"><a href="#cb30-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> (</span>
-<span id="cb30-3"><a href="#cb30-3" tabindex="-1"></a>    text_to_duration,</span>
-<span id="cb30-4"><a href="#cb30-4" tabindex="-1"></a>    calculate_crew_size</span>
-<span id="cb30-5"><a href="#cb30-5" tabindex="-1"></a>)</span>
-<span id="cb30-6"><a href="#cb30-6" tabindex="-1"></a></span>
-<span id="cb30-7"><a href="#cb30-7" tabindex="-1"></a>...</span>
-<span id="cb30-8"><a href="#cb30-8" tabindex="-1"></a></span>
-<span id="cb30-9"><a href="#cb30-9" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size():</span>
-<span id="cb30-10"><a href="#cb30-10" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb30-11"><a href="#cb30-11" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
-<span id="cb30-12"><a href="#cb30-12" tabindex="-1"></a><span class="co">    for typical crew values</span></span>
-<span id="cb30-13"><a href="#cb30-13" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb30-14"><a href="#cb30-14" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Valentina Tereshkova;"</span>)</span>
-<span id="cb30-15"><a href="#cb30-15" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">1</span></span>
-<span id="cb30-16"><a href="#cb30-16" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb30-17"><a href="#cb30-17" tabindex="-1"></a></span>
-<span id="cb30-18"><a href="#cb30-18" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Judith Resnik; Sally Ride;"</span>)</span>
-<span id="cb30-19"><a href="#cb30-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
-<span id="cb30-20"><a href="#cb30-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb30-21"><a href="#cb30-21" tabindex="-1"></a></span>
-<span id="cb30-22"><a href="#cb30-22" tabindex="-1"></a><span class="co"># Edge cases</span></span>
-<span id="cb30-23"><a href="#cb30-23" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size_edge_cases():</span>
-<span id="cb30-24"><a href="#cb30-24" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb30-25"><a href="#cb30-25" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
-<span id="cb30-26"><a href="#cb30-26" tabindex="-1"></a><span class="co">    for edge case where crew is an empty string</span></span>
-<span id="cb30-27"><a href="#cb30-27" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb30-28"><a href="#cb30-28" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">""</span>)</span>
-<span id="cb30-29"><a href="#cb30-29" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="kw">is</span> <span class="va">None</span></span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb29-2"><a href="#cb29-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> (</span>
+<span id="cb29-3"><a href="#cb29-3" tabindex="-1"></a>    text_to_duration,</span>
+<span id="cb29-4"><a href="#cb29-4" tabindex="-1"></a>    calculate_crew_size</span>
+<span id="cb29-5"><a href="#cb29-5" tabindex="-1"></a>)</span>
+<span id="cb29-6"><a href="#cb29-6" tabindex="-1"></a></span>
+<span id="cb29-7"><a href="#cb29-7" tabindex="-1"></a>...</span>
+<span id="cb29-8"><a href="#cb29-8" tabindex="-1"></a></span>
+<span id="cb29-9"><a href="#cb29-9" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size():</span>
+<span id="cb29-10"><a href="#cb29-10" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb29-11"><a href="#cb29-11" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
+<span id="cb29-12"><a href="#cb29-12" tabindex="-1"></a><span class="co">    for typical crew values</span></span>
+<span id="cb29-13"><a href="#cb29-13" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb29-14"><a href="#cb29-14" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Valentina Tereshkova;"</span>)</span>
+<span id="cb29-15"><a href="#cb29-15" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">1</span></span>
+<span id="cb29-16"><a href="#cb29-16" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb29-17"><a href="#cb29-17" tabindex="-1"></a></span>
+<span id="cb29-18"><a href="#cb29-18" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Judith Resnik; Sally Ride;"</span>)</span>
+<span id="cb29-19"><a href="#cb29-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
+<span id="cb29-20"><a href="#cb29-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb29-21"><a href="#cb29-21" tabindex="-1"></a></span>
+<span id="cb29-22"><a href="#cb29-22" tabindex="-1"></a><span class="co"># Edge cases</span></span>
+<span id="cb29-23"><a href="#cb29-23" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size_edge_cases():</span>
+<span id="cb29-24"><a href="#cb29-24" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb29-25"><a href="#cb29-25" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
+<span id="cb29-26"><a href="#cb29-26" tabindex="-1"></a><span class="co">    for edge case where crew is an empty string</span></span>
+<span id="cb29-27"><a href="#cb29-27" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb29-28"><a href="#cb29-28" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">""</span>)</span>
+<span id="cb29-29"><a href="#cb29-29" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="kw">is</span> <span class="va">None</span></span></code></pre>
+</div>
+<p>Let’s run out tests:</p>
+<div class="codewrapper sourceCode" id="cb30">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest</span></code></pre>
 </div>
 </div>
 </div>
@@ -1309,9 +1315,9 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <span id="cb31-11"><a href="#cb31-11" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
 <span id="cb31-12"><a href="#cb31-12" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span></code></pre>
 </div>
-<p>To avoid such repetitions in our test code, we can <strong>test
+<p>To avoid such repetitions in our test code, we use <strong>test
 parameterisation</strong>. This allows us to apply our test function to
-a list of input / expected output pairs without the need for repetition.
+a list of input/expected output pairs without the need for repetition.
 To parameterise the <code>test_calculate_crew_size</code> function, we
 can rewrite is as follows:</p>
 <div class="codewrapper sourceCode" id="cb32">
@@ -1609,7 +1615,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1631,8 +1637,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/08-code-correctness.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/08-code-correctness.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/09-code-documentation.html b/instructor/09-code-documentation.html
index 0d7d080d..41c6d43e 100644
--- a/instructor/09-code-documentation.html
+++ b/instructor/09-code-documentation.html
@@ -290,7 +290,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
       <div class="accordion-body">
         <ul><li><a href="#why-document-our-software">Why document our software?</a></li>
 <li><a href="#software-level-documentation">Software-level documentation</a></li>
-<li><a href="#just-enough-documentation">Just enough documentation</a></li>
+<li><a href="#project-level-documentation">Project-level documentation</a></li>
 <li><a href="#documentation-tools">Documentation tools</a></li>
 <li><a href="#documentation-guides">Documentation guides</a></li>
 <li><a href="#further-reading">Further reading</a></li>
@@ -303,7 +303,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -370,13 +370,13 @@ <h2 class="accordion-header" id="flush-headingTwelve">
           Previous: Code correctness
         </a>
         <a class="chapter-link float-end" href="../instructor/10-open-collaboration.html" rel="next">
-          Next: Open collaboration...
+          Next: Open code &amp;...
           <i aria-hidden="true" class="small-arrow" data-feather="arrow-right"></i>
         </a>
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code documentation</h1>
-        <p>Last updated on 2024-09-26 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/09-code-documentation.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -443,8 +443,8 @@ <h3 class="callout-title">Activate your virtual environment</h3>
 <div class="codewrapper sourceCode" id="cb1">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="ex">$</span> source venv_spacewalks/bin/activate <span class="co"># Mac or Linux</span></span>
-<span id="cb1-2"><a href="#cb1-2" tabindex="-1"></a><span class="ex">$</span> source venv_spacewalks/Scripts/activate <span class="co"># Windows</span></span>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> source venv_spacewalks/bin/activate <span class="co"># Mac or Linux</span></span>
+<span id="cb1-2"><a href="#cb1-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> source venv_spacewalks/Scripts/activate <span class="co"># Windows</span></span>
 <span id="cb1-3"><a href="#cb1-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span></span></code></pre>
 </div>
 </div>
@@ -489,10 +489,9 @@ <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square">
 </ul></section><section><h2 class="section-heading" id="software-level-documentation">Software-level documentation<a class="anchor" aria-label="anchor" href="#software-level-documentation"></a></h2>
 <hr class="half-width"><p>In previous episodes we encountered several different forms of
 in-code documentation aspects, including in-line comments and
-docstrings.</p>
-<p>These are an excellent way to improve the readability of our code,
-but by themselves are insufficient to ensure that our code is easy to
-use, understand and modify - this requires additional software-level
+docstrings. These are an excellent way to improve the readability of our
+code, but by themselves are insufficient to ensure that our code is easy
+to use, understand and modify - this requires additional software-level
 documentation.</p>
 <p>There are many different types of software-level documentation.</p>
 <div class="section level3">
@@ -507,14 +506,19 @@ <h3 id="technical-documentation">Technical documentation<a class="anchor" aria-l
 <li>Explanation - conceptual discussion of the code to help users
 understand implementation decisions</li>
 </ul></div>
+</section><section><h2 class="section-heading" id="project-level-documentation">Project-level documentation<a class="anchor" aria-label="anchor" href="#project-level-documentation"></a></h2>
+<hr class="half-width"><p>Project-level documentation includes various information and metadata
+about software that help to discover it, explain the legal terms of
+reusing it, describe its functionality on a high level and how to
+install, run and contribute to it.</p>
 <div class="section level3">
 <h3 id="repository-metadata-files">Repository metadata files<a class="anchor" aria-label="anchor" href="#repository-metadata-files"></a></h3>
-<p>In addition to software-level technical documentation, it is also
-common to see repository metadata files included in a code repository.
-Many of these files can be described as “social documentation” i.e. they
-indicate how users should “behave” in relation to our software project.
-Some common examples of repository metadata files and their role are
-tabulated below:</p>
+<p>A common way to to provide project-level documentation is to include
+various metadata files in the software repository together with code.
+Many of these files can be described as “social documentation”,
+i.e. they indicate how users should “behave” in relation to our software
+project. Some common examples of repository metadata files and their
+role are explained below:</p>
 <table class="table"><colgroup><col width="7%"><col width="92%"></colgroup><thead><tr class="header"><th>File</th>
 <th>Description</th>
 </tr></thead><tbody><tr class="odd"><td>README</td>
@@ -535,11 +539,20 @@ <h3 id="repository-metadata-files">Repository metadata files<a class="anchor" ar
 </tr><tr class="even"><td>AUTHORS</td>
 <td>Provides information on who authored the code (can also be included
 in CITATION)</td>
-</tr></tbody></table></div>
-</section><section><h2 class="section-heading" id="just-enough-documentation">Just enough documentation<a class="anchor" aria-label="anchor" href="#just-enough-documentation"></a></h2>
-<hr class="half-width"><p>For many small projects the following three pieces of documentation
-may be sufficient: README, LICENSE and CITATION.</p>
+</tr></tbody></table><div id="just-enough-documentation" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="just-enough-documentation" class="callout-inner">
+<h3 class="callout-title">Just enough documentation</h3>
+<div class="callout-content">
+<p>For many small projects the following three pieces of project-level
+documentation may be sufficient: README, LICENSE and CITATION.</p>
+</div>
+</div>
+</div>
 <p>Let’s look at each of these files in turn.</p>
+</div>
 <div class="section level3">
 <h3 id="readme-file">README file<a class="anchor" aria-label="anchor" href="#readme-file"></a></h3>
 <p>A README file acts as a “landing page” for your code repository on
@@ -633,23 +646,20 @@ <h4 id="optional">Optional<a class="anchor" aria-label="anchor" href="#optional"
 </div>
 </div>
 </div>
-<p>Let’s create a simple README for our repository.</p>
-<div class="codewrapper sourceCode" id="cb2">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="ex">$</span> cd ~/Desktop/Spacewalks</span>
-<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="ex">$</span> touch README.md</span></code></pre>
-</div>
-<p>Let’s start by adding a one-liner that explains the purpose of our
+<p>Let’s create a simple README for our repository - from VS Code or
+command line terminal create file <code>README.md</code> (in Markdown
+format) or <code>README.txt</code> (in plain text format).</p>
+<p>We can start by adding a one-liner that explains the purpose of our
 code and who it is for.</p>
 <pre class="code"><code># Spacewalks
 
 ## Overview
-Spacewalks is a python-based analysis tool for researchers to generate visualisations
+Spacewalks is a Python analysis tool for researchers to generate visualisations
 and statistical summaries of NASA's extravehicular activity datasets.</code></pre>
 <p>Now let’s add a list of Spacewalks’ key features:</p>
 <pre class="code"><code>## Features
 Key features of Spacewalks:
+
 - Generates a CSV table of summary statistics of extravehicular activity crew sizes
 - Generates a line plot to show the cumulative duration of space walks over time</code></pre>
 <p>Now let’s tell users about any pre-requisites required to run the
@@ -672,9 +682,10 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div id="spacewalks-readme" class="callout-inner">
 <h3 class="callout-title">Spacewalks README</h3>
 <div class="callout-content">
-<p>Extend the README for Spacewalks by adding a. Installation
-instructions b. A simple usage example</p>
-</div>
+<p>Extend the README for Spacewalks by adding:</p>
+<ol style="list-style-type: decimal"><li>Installation instructions</li>
+<li>A simple usage example</li>
+</ol></div>
 </div>
 </div>
 <div id="accordionSolution2" class="accordion challenge-accordion accordion-flush">
@@ -686,39 +697,40 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <div class="accordion-body">
 <p>Installation instructions:</p>
 <p>NB: In the solution below the back ticks of each code block have been
-escaped to avoid rendering issues.</p>
-<pre class="text"><code># Installation instructions
+escaped to avoid rendering issues (if you are copying and pasting the
+text, make sure you unescape them).</p>
+<pre class="text"><code>## Installation instructions
 
 + Clone the Spacewalks repository to your local machine using Git.
 If you don't have Git installed, you can download it from the official Git website.
 
-\`\`\`bash
+\`\`\`
 git clone https://github.com/your-repository-url/spacewalks.git
 cd spacewalks
 \`\`\`
 
 + Install the necessary dependencies:
-\`\`\`bash
-pip install pandas==2.2.2 matplotlib==3.8.4 numpy==2.0.0 pytest==7.4.2
+\`\`\`
+python3 -m pip install pandas==2.2.2 matplotlib==3.8.4 numpy==2.0.0 pytest==7.4.2
 \`\`\`
 
 + To ensure everything is working correctly, run the tests using pytest.
 
-\`\`\`bash
-python -m pytest
+\`\`\`
+python3 -m pytest
 \`\`\`</code></pre>
 <p>Usage instructions:</p>
-<pre class="text"><code># Usage Example
+<pre class="text"><code>## Usage Example
 
 To run an analysis using the eva_data_analysis.py script from the command line terminal,
 launch the script using Python as follows:
 
-\`\`\`python
+\`\`\`
 # Usage Examples
-python eva_data_analysis.py eva-data.json eva-data.csv
+python3 eva_data_analysis.py eva-data.json eva-data.csv
 \`\`\`
 
-The first argument is path to the Json data file.
+The first argument is path to the JSON data file.
 The second argument is the path the CSV output file.</code></pre>
 </div>
 </div>
@@ -839,146 +851,124 @@ <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 <h3 id="citation-file">CITATION file<a class="anchor" aria-label="anchor" href="#citation-file"></a></h3>
 <p>We can add a citation file to our repository to provide instructions
 on how and when to cite our code. A citation file can be a plain text
-(CITATION.txt) or a Markdown file (CITATION.md), but there are certain
-benefits to use a special file format called the Citation File Format
-(CFF) which provides a way to include richer metadata about software or
-datasets we want to cite, making it easy for both humans and machines to
-use this information.</p>
+(<code>CITATION.txt</code>) or a Markdown file
+(<code>CITATION.md</code>), but there are certain benefits to use a
+special file format called the Citation File Format (CFF) which provides
+a way to include richer metadata about software or datasets we want to
+cite, making it easy for both humans and machines to use this
+information.</p>
 <div class="section level4">
 <h4 id="why-use-cff">Why use CFF?<a class="anchor" aria-label="anchor" href="#why-use-cff"></a></h4>
 <p>For developers, using a CFF file can help to automate the process of
-publishing new releases on Zenodo via GitHub. GitHub also “understands”
-CFF, and will display citation information prominently on the landing
-page of a repository that contains citation info in CFF.</p>
+publishing new releases on <a href="https://zenodo.org/" class="external-link">Zenodo</a> via
+GitHub. GitHub also “understands” CFF, and will display citation
+information prominently on the landing page of a repository that
+contains citation info in CFF.</p>
 <p>For users, having a CFF file makes it easy to cite the software or
 dataset with formatted citation information available for copy-paste and
 direct import from GitHub into reference managers like Zotero.</p>
 </div>
 <div class="section level4">
-<h4 id="creating-a-cff-file">Creating a CFF file<a class="anchor" aria-label="anchor" href="#creating-a-cff-file"></a></h4>
+<h4 id="cff-file-format">CFF file format<a class="anchor" aria-label="anchor" href="#cff-file-format"></a></h4>
 <p>A CFF file is using the <a href="https://yaml.org/" class="external-link">YAML</a>
 key-value pair format. At a minimum a CFF file must contain the title of
 the software/data, the type of asset (software or data) and at least one
 author:</p>
-<div class="codewrapper sourceCode" id="cb8">
+<div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
-<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb8-10"><a href="#cb8-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
-<span id="cb8-11"><a href="#cb8-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
+<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
+<span id="cb7-3"><a href="#cb7-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb7-4"><a href="#cb7-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
+<span id="cb7-5"><a href="#cb7-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb7-6"><a href="#cb7-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb7-7"><a href="#cb7-7" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb7-8"><a href="#cb7-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb7-9"><a href="#cb7-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb7-10"><a href="#cb7-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
+<span id="cb7-11"><a href="#cb7-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span></code></pre>
 </div>
 <p>Additional and optional metadata includes an abstract, repository URL
 and more.</p>
 </div>
 <div class="section level4">
-<h4 id="steps-to-make-your-software-citable">Steps to make your software citable<a class="anchor" aria-label="anchor" href="#steps-to-make-your-software-citable"></a></h4>
-<p>We can create (and update) a CFF file for our software using an
-online application called <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a>.</p>
-<p>Let’s create a dummy citation file for a project called “Spacetravel”
-with Author “Max Hypothesis” by following these steps:</p>
-<ol style="list-style-type: decimal"><li>First, head to <code>cffinit</code> online at <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a>.</li>
-<li>Then, let’s work through the metadata input form to complete the
-minimum information needed to generate a CFF. We’ll also add the
-following abstract:
-<code>"Spacetravel - a simple python script to calculate time spent in Space by individual NASA astronauts"</code>
+<h4 id="creating-cff-file-and-making-your-software-citable">Creating CFF file and making your software citable<a class="anchor" aria-label="anchor" href="#creating-cff-file-and-making-your-software-citable"></a></h4>
+<p>We can create (and later update) a CFF file for our software using an
+online application called <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a> by following
+these steps:</p>
+<ol style="list-style-type: decimal"><li><p>Head to <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code>
+online tool</a>.</p></li>
+<li>
+<p>Then, work through the metadata input form to complete the
+minimum information needed to generate a CFF.</p>
+<p>We can use the following description as an “Abstract”: “A Python
+script to analyse NASA extravehicular activity data”</p>
+<p>Add the URL of the code repository as a “Related Resources”.</p>
+<p>Add at least two key words under the “Keywords” section.</p>
 </li>
-<li>At the end of the process, download the CFF file and inspect it. It
-should look like this:</li>
-</ol><div class="codewrapper sourceCode" id="cb9">
+<li><p>At the end of the process, download the CFF file and inspect it.
+It should look like this:</p></li>
+</ol><div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a></span>
-<span id="cb9-4"><a href="#cb9-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb9-5"><a href="#cb9-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacetravel</span></span>
-<span id="cb9-6"><a href="#cb9-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb9-7"><a href="#cb9-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb9-8"><a href="#cb9-8" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb9-9"><a href="#cb9-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb9-10"><a href="#cb9-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb9-11"><a href="#cb9-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Hypothesis</span></span>
-<span id="cb9-12"><a href="#cb9-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Max</span></span>
-<span id="cb9-13"><a href="#cb9-13" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb9-14"><a href="#cb9-14" tabindex="-1"></a>    A simple python script to calculate time spent in Space by individual NASA astronauts</span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
+<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
+<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a></span>
+<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
+<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb8-10"><a href="#cb8-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb8-11"><a href="#cb8-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
+<span id="cb8-12"><a href="#cb8-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
+<span id="cb8-13"><a href="#cb8-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
+<span id="cb8-14"><a href="#cb8-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
+<span id="cb8-15"><a href="#cb8-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
+<span id="cb8-16"><a href="#cb8-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
+<span id="cb8-17"><a href="#cb8-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-18"><a href="#cb8-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
+<span id="cb8-19"><a href="#cb8-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-20"><a href="#cb8-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
+<span id="cb8-21"><a href="#cb8-21" tabindex="-1"></a>  data</span>
+<span id="cb8-22"><a href="#cb8-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
+<span id="cb8-23"><a href="#cb8-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
+<span id="cb8-24"><a href="#cb8-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span></code></pre>
 </div>
+<p>CFF files can also be updated using the <code>cffinit</code> online
+tool by pasting the previous version of CFF file and working through the
+form to update various fields.</p>
 </div>
 <div class="section level4">
-<h4 id="updating-and-citing">Updating and citing<a class="anchor" aria-label="anchor" href="#updating-and-citing"></a></h4>
-<p>CFF files can also be updated using the <code>cffinit</code> online
-tool.</p>
+<h4 id="citing">Citing<a class="anchor" aria-label="anchor" href="#citing"></a></h4>
 <p>To cite our software (or dataset), once a CFF file has been pushed to
 our remote repository, GitHub’s “Cite this repository” button can be
 used to generate a citation in various formats (APA, BibTeX).</p>
-</div>
-<div class="section level4">
-<h4 id="tools">Tools<a class="anchor" aria-label="anchor" href="#tools"></a></h4>
-<p>Command line tools are also available for creating, validating, and
-converting CFF files. Further information is available from the <a href="https://book.the-turing-way.org/communication/citable/citable-cff.html" class="external-link">Turing
-Way’s guide to software citation</a>.</p>
-<div id="spacewalks-software-citation" class="callout challenge">
+<div id="section" class="callout">
 <div class="callout-square">
-<i class="callout-icon" data-feather="zap"></i>
+<i class="callout-icon" data-feather="bell"></i>
 </div>
-<div id="spacewalks-software-citation" class="callout-inner">
-<h3 class="callout-title">Spacewalks software citation</h3>
+<div id="section" class="callout-inner">
+<h3 class="callout-title"></h3>
 <div class="callout-content">
-<p>Write a software citation file for our Spacewalks software and add it
-to the root folder of our project.</p>
-<ul><li>Add the URL of the code repository as a “Related Resources”</li>
-<li>Add a one-line description of the code under the “Abstract”
-section</li>
-<li>Add at least two key words under the “Keywords” section</li>
-</ul></div>
+<p>Further information is available from the <a href="https://book.the-turing-way.org/communication/citable/citable-cff.html" class="external-link">Turing
+Way’s guide to software citation</a>.</p>
 </div>
 </div>
-<div id="accordionSolution4" class="accordion challenge-accordion accordion-flush">
-<div class="accordion-item">
-<button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution4" aria-expanded="false" aria-controls="collapseSolution4">
-  <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
-</button>
-<div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
-<div class="accordion-body">
-<p>Use <a href="https://citation-file-format.github.io/cff-initializer-javascript/#/version-specific" class="external-link">cffinit</a>,
-a web application to create your citation file using a series of online
-forms.</p>
-<div class="codewrapper sourceCode" id="cb10">
-<h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a></span>
-<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
-<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb10-8"><a href="#cb10-8" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb10-9"><a href="#cb10-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb10-10"><a href="#cb10-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb10-11"><a href="#cb10-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
-<span id="cb10-12"><a href="#cb10-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
-<span id="cb10-13"><a href="#cb10-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
-<span id="cb10-14"><a href="#cb10-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
-<span id="cb10-15"><a href="#cb10-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
-<span id="cb10-16"><a href="#cb10-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
-<span id="cb10-17"><a href="#cb10-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-18"><a href="#cb10-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
-<span id="cb10-19"><a href="#cb10-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-20"><a href="#cb10-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
-<span id="cb10-21"><a href="#cb10-21" tabindex="-1"></a>  data</span>
-<span id="cb10-22"><a href="#cb10-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
-<span id="cb10-23"><a href="#cb10-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
-<span id="cb10-24"><a href="#cb10-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span></code></pre>
 </div>
+<div id="spacewalks-software-citation" class="callout discussion">
+<div class="callout-square">
+<i class="callout-icon" data-feather="message-circle"></i>
 </div>
+<div id="spacewalks-software-citation" class="callout-inner">
+<h3 class="callout-title">Spacewalks software citation</h3>
+<div class="callout-content">
+<p>Add the citation file for our Spacewalks software to the root folder
+of our repository on GitHub. You can either do it directly on GitHub or
+creating the file locally and the committing and pushing to GitHub from
+the command line.</p>
 </div>
 </div>
 </div>
@@ -987,40 +977,33 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 </section><section><h2 class="section-heading" id="documentation-tools">Documentation tools<a class="anchor" aria-label="anchor" href="#documentation-tools"></a></h2>
 <hr class="half-width"><p>Once our project reaches a certain size or level of complexity we may
 want to add additional documentation such as a standalone tutorial or
-“Background” explaining our methodological choices.</p>
+“background” explaining our methodological choices.</p>
 <p>Once we move beyond using a README as our primary source of
 documentation, we need to consider how we will distribute our
-documentation to our users.</p>
-<p>Options include:</p>
-<ul><li>A <code>docs/</code> folder of Markdown files.</li>
-<li>Adding a Wiki to our repository.</li>
+documentation to our users. Options include:</p>
+<ul><li>A <code>docs/</code> folder of Markdown files</li>
+<li>Adding a Wiki to our repository</li>
 <li>Creating a set of web pages for our documentation using a static
-site generator for our documentation such as Sphinx or MkDocs</li>
+site generator for our documentation such as Sphinx or MkDocs.</li>
 </ul><p>Creating a static site is a popular solution as it has the key
 benefit being able to automatically generate a reference manual from any
 docstrings we have added to our code.</p>
 <div class="section level3">
 <h3 id="mkdocs">MkDocs<a class="anchor" aria-label="anchor" href="#mkdocs"></a></h3>
 <p>Let’s setup the static documentation site generator tool MkDocs.</p>
-<div class="codewrapper sourceCode" id="cb11">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install mkdocs</span>
-<span id="cb11-2"><a href="#cb11-2" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install <span class="st">"mkdocstrings[python]"</span></span>
-<span id="cb11-3"><a href="#cb11-3" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install mkdocs-material</span></code></pre>
-</div>
-<p>Let’s check that MkDocs has been setup correctly:</p>
-<div class="codewrapper sourceCode" id="cb12">
+<div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip list</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install mkdocs</span>
+<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install <span class="st">"mkdocstrings[python]"</span></span>
+<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install mkdocs-material</span></code></pre>
 </div>
-<p>Let’s creates a new MkDocs project in the current directory</p>
-<div class="codewrapper sourceCode" id="cb13">
+<p>Let’s creates a new MkDocs project in the current directory:</p>
+<div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="co"># In ~/Desktop/spacewalks</span></span>
-<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a><span class="ex">mkdocs</span> new .    </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="co"># In ~/Desktop/spacewalks</span></span>
+<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="ex">mkdocs</span> new .    </span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1030,72 +1013,76 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 <p>This command creates a new MkDocs project in the current directory
 with a <code>docs</code> folder containing an <code>index.md</code> file
-and a <code>mkdocs.yml</code> configuration file.</p>
-<p>Now, let’s fill in the configuration file for our project.</p>
-<div class="codewrapper sourceCode" id="cb15">
+and a <code>mkdocs.yml</code> configuration file in the root of our
+project.</p>
+<p>Now, let’s fill in the <code>mkdocs.yml</code> configuration file for
+our project.</p>
+<div class="codewrapper sourceCode" id="cb12">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a></span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
-<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
-<span id="cb15-5"><a href="#cb15-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
-<span id="cb15-6"><a href="#cb15-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
-<span id="cb15-7"><a href="#cb15-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
-<span id="cb15-8"><a href="#cb15-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
-<span id="cb15-9"><a href="#cb15-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
-<span id="cb15-10"><a href="#cb15-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
-<span id="cb15-11"><a href="#cb15-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span></code></pre>
-</div>
-<p>Note font-false is for GDPR compliance.</p>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
+<span id="cb12-2"><a href="#cb12-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb12-3"><a href="#cb12-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
+<span id="cb12-4"><a href="#cb12-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
+<span id="cb12-5"><a href="#cb12-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb12-6"><a href="#cb12-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
+<span id="cb12-7"><a href="#cb12-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
+<span id="cb12-8"><a href="#cb12-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
+<span id="cb12-9"><a href="#cb12-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
+<span id="cb12-10"><a href="#cb12-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
+<span id="cb12-11"><a href="#cb12-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span></code></pre>
+</div>
+<p>Note <code>font: false</code> variable is for GDPR compliance;
+<code>use_directory_url: false</code> variable tells MKDocs tools how to
+handle URLs for documentation that is served as a website (we will cover
+this in a moment).</p>
 <p>Let’s add support for <code>mkdocstrings</code> - this will allow us
 to automatically our docstrings into our documentation using a simple
 tag.</p>
-<div class="codewrapper sourceCode" id="cb16">
+<div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
-<span id="cb16-2"><a href="#cb16-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
-<span id="cb16-3"><a href="#cb16-3" tabindex="-1"></a></span>
-<span id="cb16-4"><a href="#cb16-4" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
-<span id="cb16-5"><a href="#cb16-5" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
-<span id="cb16-6"><a href="#cb16-6" tabindex="-1"></a></span>
-<span id="cb16-7"><a href="#cb16-7" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
-<span id="cb16-8"><a href="#cb16-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
-<span id="cb16-9"><a href="#cb16-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
-<span id="cb16-10"><a href="#cb16-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
-<span id="cb16-11"><a href="#cb16-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
-<span id="cb16-12"><a href="#cb16-12" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span>
-<span id="cb16-13"><a href="#cb16-13" tabindex="-1"></a></span>
-<span id="cb16-14"><a href="#cb16-14" tabindex="-1"></a><span class="fu">plugins</span><span class="kw">:</span></span>
-<span id="cb16-15"><a href="#cb16-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> mkdocstrings</span></span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
+<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
+<span id="cb13-4"><a href="#cb13-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
+<span id="cb13-5"><a href="#cb13-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb13-6"><a href="#cb13-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
+<span id="cb13-7"><a href="#cb13-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
+<span id="cb13-8"><a href="#cb13-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
+<span id="cb13-9"><a href="#cb13-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
+<span id="cb13-10"><a href="#cb13-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
+<span id="cb13-11"><a href="#cb13-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span>
+<span id="cb13-12"><a href="#cb13-12" tabindex="-1"></a></span>
+<span id="cb13-13"><a href="#cb13-13" tabindex="-1"></a><span class="fu">plugins</span><span class="kw">:</span></span>
+<span id="cb13-14"><a href="#cb13-14" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> mkdocstrings</span></span></code></pre>
 </div>
 <p>Let’s populate our <code>docs/</code> folder to match our
 configuration file.</p>
-<div class="codewrapper sourceCode" id="cb17">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="fu">touch</span> docs/tutorials.md</span>
-<span id="cb17-2"><a href="#cb17-2" tabindex="-1"></a><span class="fu">touch</span> docs/how-to-guides.md</span>
-<span id="cb17-3"><a href="#cb17-3" tabindex="-1"></a><span class="fu">touch</span> docs/reference.md</span>
-<span id="cb17-4"><a href="#cb17-4" tabindex="-1"></a><span class="fu">touch</span> docs/explanation.md</span></code></pre>
-</div>
-<p>Let’s populate our reference file with some preamble to include
-before the reference manual that will be generated from the docstrings
-we created.</p>
-<div class="codewrapper sourceCode" id="cb18">
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/tutorials.md</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/how-to-guides.md</span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/reference.md</span>
+<span id="cb14-4"><a href="#cb14-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/explanation.md</span></code></pre>
+</div>
+<p>Let’s populate our reference file <code>reference.md</code> with some
+preamble to include before the reference manual that will be generated
+from the docstrings we created.</p>
+<div class="codewrapper sourceCode" id="cb15">
 <h3 class="code-label">MARKDOWN<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode markdown" tabindex="0"><code class="sourceCode markdown"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a>This file documents the key functions in the Spacewalks tool.</span>
-<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a>It is provided as a reference manual.</span>
-<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a></span>
-<span id="cb18-4"><a href="#cb18-4" tabindex="-1"></a>::: eva_data_analysis</span></code></pre>
+<pre class="sourceCode markdown" tabindex="0"><code class="sourceCode markdown"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a>This file documents the key functions in the Spacewalks tool.</span>
+<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a>It is provided as a reference manual.</span>
+<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a></span>
+<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a>::: eva_data_analysis</span></code></pre>
 </div>
 <p>Finally, let’s build our documentation.</p>
-<div class="codewrapper sourceCode" id="cb19">
+<div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="ex">mkdocs</span> build</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs build</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1108,25 +1095,43 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 INFO    -  Documentation built in 0.31 seconds</code></pre>
 </div>
 <p>Once the build step is completed, our documentation site is saved to
-a <code>site</code> folder in the root of our project folder.</p>
-<p>These files will be distributed with our code. We can either direct
-users to read these files locally on their own device using their
-browser, or we can choose to host our documentation as a website that
-our uses can navigate to.</p>
+a <code>site</code> folder in the root of our project folder. These
+files will be distributed with our code. We can either direct users to
+read these files locally on their own device using their browser, or we
+can choose to host our documentation as a website that our uses can
+navigate to.</p>
 <p>Note that we used the setting <code>use_directory_urls: false</code>
 in the <code>mkdocs.yml</code> file. This setting ensures that the
 documentation site is generated with URLs that are easy to navigate
 locally on a user’s device.</p>
-<p>Finally let us commit our documentation to the main branch of our git
-repository and push the changes to GitHub</p>
-<div class="codewrapper sourceCode" id="cb21">
+<div id="explore-your-documentation" class="callout discussion">
+<div class="callout-square">
+<i class="callout-icon" data-feather="message-circle"></i>
+</div>
+<div id="explore-your-documentation" class="callout-inner">
+<h3 class="callout-title">Explore your documentation</h3>
+<div class="callout-content">
+<p>Explore documentation in <code>site/</code> folder built with MkDocs
+for your project, starting from <code>index.html</code> file.</p>
+<p>For example, check <code>site/reference.html</code> to see how
+docstrings from your functions are provided here as a reference
+manual.</p>
+</div>
+</div>
+</div>
+<p>Finally, let us commit our documentation to the main branch of our
+git repository and push the changes to GitHub.</p>
+<div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="fu">git</span> add mkdocs.yml </span>
-<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="fu">git</span> add docs/</span>
-<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a><span class="fu">git</span> add site/</span>
-<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
-<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add mkdocs.yml </span>
+<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add docs/</span>
+<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add site/</span>
+<span id="cb18-4"><a href="#cb18-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
+<span id="cb18-5"><a href="#cb18-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip freeze <span class="op">&gt;</span> requirements.txt</span>
+<span id="cb18-6"><a href="#cb18-6" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add requirements.txt </span>
+<span id="cb18-7"><a href="#cb18-7" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Added mkdocs plugin"</span></span>
+<span id="cb18-8"><a href="#cb18-8" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 <div id="hosting-documentation" class="callout">
 <div class="callout-square">
@@ -1135,9 +1140,8 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div id="hosting-documentation" class="callout-inner">
 <h3 class="callout-title">Hosting documentation</h3>
 <div class="callout-content">
-<p>In the previous section, we saw how Mkdocs documentation can be
-distributed with our repository and viewed “offline” using a
-browser.</p>
+<p>We saw how MkDocs documentation can be distributed with our
+repository and viewed “offline” using a browser.</p>
 <p>We can also make our documentation available as a live website by
 deploying our documentation to a hosting service.</p>
 <div id="accordionSpoiler1" class="accordion spoiler-accordion accordion-flush">
@@ -1155,10 +1159,11 @@ <h3 id="github-pages">GitHub Pages<a class="anchor" aria-label="anchor" href="#g
 <p>There are two types of GitHub Pages: project pages and
 user/organization Pages. While similar, they have different deployment
 workflows, and we will only discuss project pages here. For information
-about deploying to user/organisational pages, see [MkDocs Deployment
-pages][mkdocs-deploy].</p>
-<p>Project Pages deploy site files to a branch within the project
-repository (default is gh-pages). To deploy our documentation:</p>
+about deploying to user/organisational pages, see <a href="https://www.mkdocs.org/user-guide/deploying-your-docs/" class="external-link">MkDocs
+Deployment pages</a>.</p>
+<p>Project Pages deploy site files to a branch (by default the
+<code>gh-pages</code> branch, but it can be any other branch) within the
+project repository. To deploy our documentation:</p>
 <blockquote>
 <p><strong>Warning!</strong> Before we proceed to the next step, we MUST
 ensure that there are no uncommitted changes or untracked files in our
@@ -1167,25 +1172,26 @@ <h3 id="github-pages">GitHub Pages<a class="anchor" aria-label="anchor" href="#g
 them in our documentation!</p>
 </blockquote>
 <ol style="list-style-type: decimal"><li>(If not done already), let us commit our documentation to the main
-branch of our git repository and push the changes to GitHub</li>
-</ol><div class="codewrapper sourceCode" id="cb22">
+branch of our git repository and push the changes to GitHub.</li>
+</ol><div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="fu">git</span> add mkdocs.yml </span>
-<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a><span class="fu">git</span> add docs/</span>
-<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a><span class="fu">git</span> add site/</span>
-<span id="cb22-4"><a href="#cb22-4" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
-<span id="cb22-5"><a href="#cb22-5" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add mkdocs.yml </span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add docs/</span>
+<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add site/</span>
+<span id="cb19-4"><a href="#cb19-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
+<span id="cb19-5"><a href="#cb19-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 <ol start="2" style="list-style-type: decimal"><li>Once we are on the main branch and all our changes are up to date,
-run the following command to deploy our documentation to GitHub.</li>
-</ol><div class="codewrapper sourceCode" id="cb23">
+run the following command from the command line termindal to deploy our
+documentation to GitHub.</li>
+</ol><div class="codewrapper sourceCode" id="cb20">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="co"># Important: </span></span>
-<span id="cb23-2"><a href="#cb23-2" tabindex="-1"></a><span class="co"># - This command will push the documentation to the gh-pages branch of your repository</span></span>
-<span id="cb23-3"><a href="#cb23-3" tabindex="-1"></a><span class="co"># - It will ALSO include uncommitted changes and untracked files (read the warning above!!) &lt;- VERY IMPORTANT!!</span></span>
-<span id="cb23-4"><a href="#cb23-4" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="co"># Important: </span></span>
+<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="co"># - This command will push the documentation to the gh-pages branch of your repository</span></span>
+<span id="cb20-3"><a href="#cb20-3" tabindex="-1"></a><span class="co"># - It will ALSO include uncommitted changes and untracked files (read the warning above!!) &lt;- VERY IMPORTANT!!</span></span>
+<span id="cb20-4"><a href="#cb20-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs gh-deploy</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -1215,13 +1221,14 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 INFO    -  Your documentation should shortly be available at: https://kkh451.github.io/spacewalks/</code></pre>
 </div>
 <p>This command will build our documentation with MkDocs, then commit
-and push the files to the gh-pages branch using the GitHub ghp-import
-tool which is installed as a dependency of MkDocs.</p>
+and push the files to the <code>gh-pages</code> branch using the GitHub
+<code>ghp-import</code> tool which is installed as a dependency of
+MkDocs.</p>
 <p>For more options, use:</p>
-<div class="codewrapper sourceCode" id="cb25">
+<div class="codewrapper sourceCode" id="cb22">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy <span class="at">--help</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy <span class="at">--help</span></span></code></pre>
 </div>
 <p>Notice that the deploy command did not allow us to preview the site
 before it was pushed to GitHub; so, it is a good idea to check changes
@@ -1230,8 +1237,8 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="section level3">
 <h3 id="other-options">Other options<a class="anchor" aria-label="anchor" href="#other-options"></a></h3>
 <p>You can find out about other deployment options including free
-documentation hosting service ReadTheDocs on the [MkDocs deployment
-pages][mkdocs-deploy].</p>
+documentation hosting service ReadTheDocs on the <a href="https://www.mkdocs.org/user-guide/deploying-your-docs/" class="external-link">MkDocs
+deployment pages</a>.</p>
 </div>
 </div>
 </div>
@@ -1243,8 +1250,8 @@ <h3 id="other-options">Other options<a class="anchor" aria-label="anchor" href="
 </div>
 </section><section><h2 class="section-heading" id="documentation-guides">Documentation guides<a class="anchor" aria-label="anchor" href="#documentation-guides"></a></h2>
 <hr class="half-width"><p>Once we start to consider other forms of documentation beyond the
-README, we can also increase the re-usability of our code by ensuring
-that the content and style of our documentation matches its purpose.</p>
+README, we can also increase reusability of our code by ensuring that
+the content and style of our documentation matches its purpose.</p>
 <p>Documentation guides such as <a href="https://www.writethedocs.org/" class="external-link">Write the Docs</a>, <a href="https://www.thegooddocsproject.dev/" class="external-link">The Good Docs Project</a> and
 the <a href="https://diataxis.fr/" class="external-link">Diataxis framework</a> provide a
 range of resources including documentation templates to help to help us
@@ -1259,8 +1266,9 @@ <h3 class="callout-title">Spacewalks how-to guide</h3>
 <ol style="list-style-type: lower-alpha"><li><p>Review the Diataxis guidance page on writing a How-to guide.
 Identify three features of an effective how-to guide.</p></li>
 <li><p>Following the Diataxis guidelines, add a how-to guide to the
-<code>docs</code> folder that show users how to change the destination
-filename for the output dataset generated by Spacewalks.</p></li>
+<code>docs/how-to-guides.md</code> file in your documentation folder to
+show users how to change the destination filename for the output CSV
+dataset generated by the Spacewalks software.</p></li>
 </ol><div id="accordionSpoiler2" class="accordion spoiler-accordion accordion-flush">
 <div class="accordion-item">
 <button class="accordion-button spoiler-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSpoiler2" aria-expanded="false" aria-controls="collapseSpoiler2">
@@ -1273,21 +1281,30 @@ <h3 class="accordion-header" id="headingSpoiler2">  <div class="note-square"><i
 <li>avoid teaching or explanation</li>
 <li>use appropriate language e.g. conditional imperatives</li>
 <li>have an informative title</li>
-</ul><p>An example how-to guide:</p>
+</ul><p>An example how-to guide for our project to the file
+<code>docs/how-to-guides.md</code>:</p>
 <pre><code># How to change the file path of Spacewalk's output dataset
 
 This guide shows you how to set the file path for Spacewalk's output
 data set to a location of your choice.
 
-By default, the cleaned data set generated by Spacewalk is saved to the current
-working directory with file name `eva-data.csv`.
+By default, the cleaned data set in CSV format, generated by the Spacewalk software, is saved to the `results/`
+folder within the working directory with file name `eva-data.csv`.
 
 If you would like to modify the name or location of the output dataset, set the
 second command line argument to your chosen file path.
+For example, if you want to save the output data set to the subfolder `data/clean/` you can
+invoke the script as:
 
-`python eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv`
+`(venv_spacewalks) $ python3 eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv`
 
-The specified destination folder must exist before running spacewalks analysis script.</code></pre>
+The specified destination folder `data/clean/` must exist before running spacewalks analysis script.</code></pre>
+<p>Remember to rebuild your documentation:</p>
+<div class="codewrapper sourceCode" id="cb24">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs build</span></code></pre>
+</div>
 </div>
 </div>
 </div>
@@ -1320,8 +1337,9 @@ <h3 class="accordion-header" id="headingSpoiler3">  <div class="note-square"><i
 <div class="section level4">
 <h4 id="introduction">Introduction<a class="anchor" aria-label="anchor" href="#introduction"></a></h4>
 <p>In this tutorial, we will learn how to change the file path for the
-output dataset generated by Spacewalk. By the end of this tutorial, you
-will be able to specify a custom file path for the cleaned dataset.</p>
+output dataset generated by the Spacewalk software. By the end of this
+tutorial, you will be able to specify a custom file path for the cleaned
+dataset.</p>
 </div>
 <div class="section level4">
 <h4 id="prerequisites">Prerequisites<a class="anchor" aria-label="anchor" href="#prerequisites"></a></h4>
@@ -1332,34 +1350,35 @@ <h4 id="prerequisites">Prerequisites<a class="anchor" aria-label="anchor" href="
 </ul></div>
 <div class="section level4">
 <h4 id="prepare-the-destination-directory">Prepare the destination directory<a class="anchor" aria-label="anchor" href="#prepare-the-destination-directory"></a></h4>
-<p>First, let us decide where we want to save the cleaned dataset. and
+<p>First, let us decide where we want to save the cleaned dataset and
 make sure the directory exists.</p>
-<p>For this tutorial, we will use data/clean as the destination
-folder.</p>
-<p>Let’s create the directory if it does not exist:</p>
-<div class="codewrapper sourceCode" id="cb27">
+<p>For this tutorial, we will use <code>data/clean/</code> as the
+destination folder.</p>
+<p>Let’s create the directory if it does not exist - e.g. from the
+command line do:</p>
+<div class="codewrapper sourceCode" id="cb25">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="fu">mkdir</span> <span class="at">-p</span> data/clean</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir <span class="at">-p</span> data/clean</span></code></pre>
 </div>
 </div>
 <div class="section level4">
-<h4 id="run-the-analysis-script-with-custom-path">Run the analysis script with custom path<a class="anchor" aria-label="anchor" href="#run-the-analysis-script-with-custom-path"></a></h4>
+<h4 id="run-the-analysis-script-with-a-custom-path">Run the analysis script with a custom path<a class="anchor" aria-label="anchor" href="#run-the-analysis-script-with-a-custom-path"></a></h4>
 <p>Next, execute the Spacewalk script and specify the custom file path
 for the output dataset:</p>
-<div class="codewrapper sourceCode" id="cb28">
+<div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb28-1"><a href="#cb28-1" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py <span class="op">&lt;</span>input-file<span class="op">&gt;</span> <span class="op">&lt;</span>output-file<span class="op">&gt;</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py <span class="op">&lt;</span>input-file<span class="op">&gt;</span> <span class="op">&lt;</span>output-file<span class="op">&gt;</span></span></code></pre>
 </div>
-<p>Replace <input-file> with your input dataset (eva-data.json) and
-<output-file> with your desired output path
-(data/clean/eva-data-clean.csv).</output-file></input-file></p>
+<p>Replace <input-file> with your input dataset
+(<code>data/eva-data.json</code>) and <output-file> with your desired
+output path (<code>data/clean/eva-data-clean.csv</code>).</output-file></input-file></p>
 <p>Here is the complete command:</p>
-<div class="codewrapper sourceCode" id="cb29">
+<div class="codewrapper sourceCode" id="cb27">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py data/eva-data.json data/clean/eva-data-clean.csv</span></code></pre>
 </div>
 <p>Notice how the output to the command line clearly indicates that we
 are using a custom output file path.</p>
@@ -1367,44 +1386,45 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="output" tabindex="0"><code>Using custom input and output filenames
-Reading JSON file eva-data.json
+Reading JSON file data/eva-data.json
 Saving to CSV file data/clean/eva-data-clean.csv
 Adding crew size variable (crew_size) to dataset
 Saving to CSV file data/clean/eva-data-clean.csv
-Plotting cumulative spacewalk duration and saving to ./cumulative_eva_graph.png</code></pre>
+Plotting cumulative spacewalk duration and saving to results/cumulative_eva_graph.png</code></pre>
 </div>
-<p>After running the script, let us check the data/clean directory to
-ensure the cleaned dataset has been saved correctly.</p>
-<div class="codewrapper sourceCode" id="cb31">
+<p>After running the script, let us check the <code>data/clean</code>
+directory to ensure the cleaned dataset has been saved correctly.</p>
+<div class="codewrapper sourceCode" id="cb29">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" tabindex="-1"></a><span class="fu">ls</span> data/clean</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> ls data/clean</span></code></pre>
 </div>
-<p>You should see eva-data-clean.csv listed in the data/clean folder</p>
+<p>You should see <code>eva-data-clean.csv</code> file listed in the
+<code>data/clean</code> folder.</p>
 </div>
 <div class="section level4">
 <h4 id="exercise-custom-output-path">Exercise: custom output path<a class="anchor" aria-label="anchor" href="#exercise-custom-output-path"></a></h4>
-<ul><li>Create a new directory named output/data in your working
-directory.</li>
+<ul><li>Create a new directory named <code>output/data</code> in your
+working directory.</li>
 <li>Run the Spacewalk script to save the cleaned dataset in the newly
-created output/data directory with the filename
-cleaned-eva-data.csv.</li>
+created <code>output/data</code> directory with the filename
+<code>cleaned-eva-data.csv</code>.</li>
 <li>Verify that the dataset has been saved correctly.</li>
 </ul><div class="section level5">
 <h5 id="solution-1">Solution<a class="anchor" aria-label="anchor" href="#solution-1"></a></h5>
-<div class="codewrapper sourceCode" id="cb32">
+<div class="codewrapper sourceCode" id="cb30">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb32-1"><a href="#cb32-1" tabindex="-1"></a><span class="co"># Create the directory:</span></span>
-<span id="cb32-2"><a href="#cb32-2" tabindex="-1"></a><span class="fu">mkdir</span> <span class="at">-p</span> output/data</span>
-<span id="cb32-3"><a href="#cb32-3" tabindex="-1"></a></span>
-<span id="cb32-4"><a href="#cb32-4" tabindex="-1"></a><span class="co"># Run the script:</span></span>
-<span id="cb32-5"><a href="#cb32-5" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py eva-data.json output/data/cleaned-eva-data.csv</span>
-<span id="cb32-6"><a href="#cb32-6" tabindex="-1"></a></span>
-<span id="cb32-7"><a href="#cb32-7" tabindex="-1"></a><span class="co"># Verify the output:</span></span>
-<span id="cb32-8"><a href="#cb32-8" tabindex="-1"></a><span class="fu">ls</span> output/data</span>
-<span id="cb32-9"><a href="#cb32-9" tabindex="-1"></a></span>
-<span id="cb32-10"><a href="#cb32-10" tabindex="-1"></a><span class="co"># You should see cleaned-eva-data.csv listed</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="co"># Create the directory:</span></span>
+<span id="cb30-2"><a href="#cb30-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir <span class="at">-p</span> output/data</span>
+<span id="cb30-3"><a href="#cb30-3" tabindex="-1"></a></span>
+<span id="cb30-4"><a href="#cb30-4" tabindex="-1"></a><span class="co"># Run the script:</span></span>
+<span id="cb30-5"><a href="#cb30-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py data/eva-data.json output/data/cleaned-eva-data.csv</span>
+<span id="cb30-6"><a href="#cb30-6" tabindex="-1"></a></span>
+<span id="cb30-7"><a href="#cb30-7" tabindex="-1"></a><span class="co"># Verify the output:</span></span>
+<span id="cb30-8"><a href="#cb30-8" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> ls output/data</span>
+<span id="cb30-9"><a href="#cb30-9" tabindex="-1"></a></span>
+<span id="cb30-10"><a href="#cb30-10" tabindex="-1"></a><span class="co"># You should see cleaned-eva-data.csv listed</span></span></code></pre>
 </div>
 <p>Congratulations! You have successfully changed the file path for
 Spacewalks output dataset and completed an exercise to practice the
@@ -1459,24 +1479,14 @@ <h4 id="language">Language<a class="anchor" aria-label="anchor" href="#language"
 </div>
 </div>
 </div>
-<div id="commit-and-push-your-changes" class="callout">
-<div class="callout-square">
-<i class="callout-icon" data-feather="bell"></i>
-</div>
-<div id="commit-and-push-your-changes" class="callout-inner">
-<h3 class="callout-title">Commit and push your changes</h3>
-<div class="callout-content">
-<p>Do not forget to commit any uncommited changes you may have and then
+<p>Do not forget to commit any uncommitted changes you may have and then
 push your work to GitHub.</p>
-<div class="codewrapper sourceCode" id="cb33">
+<div class="codewrapper sourceCode" id="cb31">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb33-1"><a href="#cb33-1" tabindex="-1"></a><span class="fu">git</span> add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
-<span id="cb33-2"><a href="#cb33-2" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
-<span id="cb33-3"><a href="#cb33-3" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
-</div>
-</div>
-</div>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
+<span id="cb31-2"><a href="#cb31-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
+<span id="cb31-3"><a href="#cb31-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a></h2>
 <hr class="half-width"><p>We recommend the following resources for some additional reading on
@@ -1540,7 +1550,7 @@ <h3 class="callout-title">Key Points</h3>
           Previous: Code correctness
         </a>
         <a class="chapter-link float-end" href="../instructor/10-open-collaboration.html" rel="next">
-          Next: Open collaboration...
+          Next: Open code &amp;...
           <i aria-hidden="true" class="small-arrow" data-feather="arrow-right"></i>
         </a>
       </div>
@@ -1564,7 +1574,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1586,8 +1596,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/09-code-documentation.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/09-code-documentation.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/10-open-collaboration.html b/instructor/10-open-collaboration.html
index 58e1e4fb..6d41d117 100644
--- a/instructor/10-open-collaboration.html
+++ b/instructor/10-open-collaboration.html
@@ -1,5 +1,5 @@
 <!DOCTYPE html>
-<!-- START: inst/pkgdown/templates/layout.html --><!-- Generated by pkgdown: do not edit by hand --><html lang="en" data-bs-theme="auto"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="utf-8"><title>Tools and practices for FAIR research software: Open collaboration on code</title><meta name="viewport" content="width=device-width, initial-scale=1"><script src="../assets/themetoggle.js"></script><link rel="stylesheet" type="text/css" href="../assets/styles.css"><script src="../assets/scripts.js" type="text/javascript"></script><!-- mathjax --><script type="text/x-mathjax-config">
+<!-- START: inst/pkgdown/templates/layout.html --><!-- Generated by pkgdown: do not edit by hand --><html lang="en" data-bs-theme="auto"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="utf-8"><title>Tools and practices for FAIR research software: Open code &amp; collaboration</title><meta name="viewport" content="width=device-width, initial-scale=1"><script src="../assets/themetoggle.js"></script><link rel="stylesheet" type="text/css" href="../assets/styles.css"><script src="../assets/scripts.js" type="text/javascript"></script><!-- mathjax --><script type="text/x-mathjax-config">
     MathJax.Hub.Config({
       config: ["MMLorHTML.js"],
       jax: ["input/TeX","input/MathML","output/HTML-CSS","output/NativeMML", "output/PreviewHTML"],
@@ -290,7 +290,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
       <button class="accordion-button" type="button" data-bs-toggle="collapse" data-bs-target="#flush-collapsecurrent" aria-expanded="true" aria-controls="flush-collapsecurrent">
         <span class="visually-hidden">Current Chapter</span>
         <span class="current-chapter">
-        10. Open collaboration on code
+        10. Open code &amp; collaboration
         </span>
       </button>
     </div><!--/div.accordion-header-->
@@ -372,8 +372,8 @@ <h2 class="accordion-header" id="flush-headingTwelve">
         </a>
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
-        <h1>Open collaboration on code</h1>
-        <p>Last updated on 2024-09-24 |
+        <h1>Open code &amp; collaboration</h1>
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/10-open-collaboration.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -419,9 +419,16 @@ <h3 class="card-title">Objectives</h3>
 </div>
 </div>
 </div>
-<p>In addition to adding a license and other metadata to our code
-(covered in previous episode) there are several other important steps to
-consider before sharing the code publicly.</p>
+<p>Sharing code openly promotes collaboration, transparency, and
+innovation by allowing others to review, use, and improve the code. It
+fosters knowledge exchange, accelerates scientific progress, and
+enhances the reproducibility of research. Additionally, open sharing
+encourages community contributions and can lead to better-maintained,
+more reliable software.</p>
+<p>Adding a <a href="licensing.html">license</a> and other metadata to
+our code (covered in the previous episode) are the first steps towards
+sharing the code publicly. There are several other important steps to
+consider which we will cover here.</p>
 <div id="activate-your-virtual-environment" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
@@ -441,85 +448,99 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 </div>
 </div>
 </div>
+<div id="accordionInstructor1" class="accordion instructor-note accordion-flush">
+<div class="accordion-item">
+<button class="accordion-button instructor-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseInstructor1" aria-expanded="false" aria-controls="collapseInstructor1">
+  <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square"><i aria-hidden="true" class="callout-icon" data-feather="edit-2"></i></div> Instructor Note </h3>
+</button>
+<div id="collapseInstructor1" class="accordion-collapse collapse" aria-labelledby="headingInstructor1" data-bs-parent="#accordionInstructor1">
+<div class="accordion-body">
+<p>At this point, the code in your local software project’s directory
+should be as in: <a href="https://github.com/carpentries-incubator/astronaut-data-analysis-not-so-fair/tree/10-open-collaboration" class="external-link uri">https://github.com/carpentries-incubator/astronaut-data-analysis-not-so-fair/tree/10-open-collaboration</a></p>
+</div>
+</div>
+</div>
+</div>
 <section><h2 class="section-heading" id="sharing-code-to-encourage-collaboration">Sharing code to encourage collaboration<a class="anchor" aria-label="anchor" href="#sharing-code-to-encourage-collaboration"></a></h2>
 <hr class="half-width"><div class="section level3">
 <h3 id="making-the-code-public">Making the code public<a class="anchor" aria-label="anchor" href="#making-the-code-public"></a></h3>
-<p>By default repositories created on Github are private and only their
-creator can see them. If we’re going to be adding an open source license
-to our repository we probably want to make sure people can actually
-access it too!</p>
-<p>Go to the Github webpage of your repository
-(<code>https://github.com/&lt;yourusername&gt;/&lt;yourrepsoitoryname&gt;</code>)
-and click on the Settings link near the top right corner. Then scroll
-down to the bottom of the page and the “Danger Zone” settings. Click on
-“Change Visibility” and you should see a message saying “Change to
-public”, if it says “Change to private” then the repository is already
-public. You’ll then be asked to confirm that you want to make the
-repository public and agree to the warning that the code will now be
-publicly visible. As a security measure you’ll then have to put in your
-Github password.</p>
+<p>By default repositories created on GitHub are private and only their
+creator can see them. Since we added an open source license to our
+repository we probably want to make sure people can actually access
+it.</p>
+<p>To make your repository public, if it is not already, go to your
+repository on GitHub and click on the <code>Settings</code> link near
+the top right corner. Then scroll down to the bottom of the page and the
+“Danger Zone” settings. Click on “Change Visibility” and you should see
+a message saying “Change to public”. If it says “Change to private” then
+the repository is already public. You will then be asked to confirm that
+you indeed want to make the repository public and agree to the warning
+that the code will now be publicly visible. As a security measure, you
+will then have to put in your GitHub password.</p>
 </div>
 <div class="section level3">
 <h3 id="transferring-to-an-organisation">Transferring to an organisation<a class="anchor" aria-label="anchor" href="#transferring-to-an-organisation"></a></h3>
-<p>Currently our repository is under the Github “namespace” of our
-individual user. This is ok for individual projects where we are the
-sole or at least main author, but for bigger and more complex projects
-it is common to use a Github organisation named after our project. If we
-are a member of an organisation and have the appropriate permissions
-then we can transfer a repository from our personal namespace to the
-organisation’s. This can be done with another option in the “Danger
-Zone” settings, the “Transfer ownership” button. Pressing this will then
-prompt us as to which organisation we want to transfer the repository
-to.</p>
+<p>Currently our repository is under the GitHub “namespace” of our
+individual user. This is OK for individual projects where we are the
+sole or at least the main code author, but for bigger and more complex
+projects it is common to use a GitHub organisation named after our
+project. If we are a member of an organisation and have the appropriate
+permissions then we can transfer a repository from our personal
+namespace to the organisation’s. This can be done with another option in
+the “Danger Zone” settings, the “Transfer ownership” button. Pressing
+this will then prompt us as to which organisation we want to transfer
+the repository to.</p>
 </div>
 <div class="section level3">
-<h3 id="archiving-to-zenodo-and-obtaining-a-doi">Archiving to Zenodo and obtaining a DOI<a class="anchor" aria-label="anchor" href="#archiving-to-zenodo-and-obtaining-a-doi"></a></h3>
-<p>Zenodo is a data archive run by CERN. Anybody can upload datasets up
-to 50GB to it and receive a Digital Object Identifier (DOI). Zenodo’s
-definition of a dataset is quite broad and can include code. This gives
-us a way to obtain a DOI for our code. We can archive our Github
-repository to Zenodo by doing the following:</p>
+<h3 id="archiving-code-to-zenodo-and-obtaining-a-doi">Archiving code to Zenodo and obtaining a DOI<a class="anchor" aria-label="anchor" href="#archiving-code-to-zenodo-and-obtaining-a-doi"></a></h3>
+<p><a href="https://zenodo.org/" class="external-link">Zenodo</a> is a data archive run by
+CERN. Anybody can upload datasets up to 50GB to it and receive a Digital
+Object Identifier (DOI). Zenodo’s definition of a dataset is quite broad
+and can include code - which gives us a way to obtain a DOI for our
+software. We can archive our GitHub repository to Zenodo by doing the
+following:</p>
 <ol style="list-style-type: decimal"><li>Go to the <a href="https://zenodo.org/login" class="external-link">Zenodo Login page</a>
-and choose to login with Github.</li>
-<li>Authorise Zenodo to connect to Github.</li>
-<li>Go to the <a href="https://zenodo.org/account/settings/github/" class="external-link">Github page</a> in
+and choose to login with GitHub.</li>
+<li>Authorise Zenodo to connect to GitHub.</li>
+<li>Go to the <a href="https://zenodo.org/account/settings/github/" class="external-link">GitHub page</a> in
 your Zenodo account. This can be found in the pull down menu with your
 user name in the top right corner of the screen.</li>
-<li>You’ll now have a list of all of your Github repositories. Next to
+<li>You’ll now have a list of all of your GitHub repositories. Next to
 each will be an “On” button. If you have created a new repository you
 might need to press the “Sync” button to update the list of repositories
 Zenodo knows about.</li>
 <li>Press the “On” button for the repository you want to archive. If
-this was successful you’ll be told to refresh the page.</li>
-<li>The repository should now appear in the list of Enabled repositories
-at the top of the screen. But it doesn’t yet have a DOI. To get one we
-have to make a release on Github. Click on the repository and then press
-the green button to create a release. This will take you to Github’s
-release page where you’ll be asked to give a title and description of
-the release. You will also have to create a tag, this is a way of having
-a friendly name for the version of some code in Git instead of using a
-long hash code. Often we’ll create a sequential version number for each
-release of the software and have the tag name match this, for example
-v1.0 or just 1.0.</li>
+this was successful you will be told to refresh the page.</li>
+<li>The repository should now appear in the list of “Enabled”
+repositories at the top of the screen, but it does not yet have a DOI.
+To get one we have to make a “release” on GitHub. Click on the
+repository and then press the green button to create a release. This
+will take you to GitHub’s release page where you will be asked to give a
+title and description of the release. You will also have to create a
+“tag” for your release - a way of having a friendly name for the version
+of some code in Git instead of using a long hash code. Often we will
+create a sequential version number for each release of the software and
+have the tag name match this, for example v1.0 or just 1.0.</li>
 <li>If we now refresh the Zenodo page for this repository we will see
 that it has been assigned a DOI.</li>
-</ol><p>The DOI doesn’t just link to Github, Zenodo will have taken a copy of
-our repository at the point where we tagged the release. This means that
-even if we delete it from Github or even if Github were ever to go away
-or remove it, they’ll still be a copy on Zenodo. Zenodo will allow
-people to download the entire repository as a single Zip file.</p>
+</ol><p>The DOI does not just link to GitHub, Zenodo will have taken a copy
+(a snapshot) of our repository at the point where we tagged the release.
+This means that even if we delete it from GitHub or even if GitHub were
+ever to go away or remove it, there will still be a copy on Zenodo.
+Zenodo will allow people to download the entire repository as a single
+<code>zip</code> file.</p>
 <p>Zenodo will have actually created two DOIs for you. One represents
 the latest version of the software and will always represent the latest
-if you make more releases. The other is specfic to the release you made
+if you make more releases. The other is specific to the release you made
 and will always point to that version. We can see both of these by
-clicking on the DOI link in the Zenodo page for the repository. One of
-the things which is displayed on this page is a badge image that you can
-copy the link for and add to the README file in your Git repository so
-that people can find the Zenodo version of the repository. If you click
-on the DOI image in the Details section of the Zenodo page then you will
-be shown instructions for obtaining a link to the DOI badge in various
-formats including Markdown. Here is the badge for this repository and
-the corresponding Markdown:</p>
+clicking on the DOI link in the Zenodo page for the repository.</p>
+<p>One of the things which is displayed on this page is a badge image
+that you can copy the link for and add to the README file in your GitHub
+repository so that people can find the Zenodo version of the repository.
+If you click on the DOI image in the Details section of the Zenodo page
+then you will be shown instructions for obtaining a link to the DOI
+badge in various formats including Markdown. Here is the badge for this
+repository and the corresponding Markdown:</p>
 <p><a href="https://doi.org/10.5281/zenodo.11869450" class="external-link"><img src="https://zenodo.org/badge/DOI/10.5281/zenodo.11869450.svg" alt="DOI" class="figure"></a></p>
 <pre class="text"><code>[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.11869450.svg)](https://doi.org/10.5281/zenodo.11869450)</code></pre>
 <div id="archive-your-repository-to-zenodo" class="callout discussion">
@@ -529,7 +550,11 @@ <h3 id="archiving-to-zenodo-and-obtaining-a-doi">Archiving to Zenodo and obtaini
 <div id="archive-your-repository-to-zenodo" class="callout-inner">
 <h3 class="callout-title">Archive your repository to Zenodo</h3>
 <div class="callout-content">
-<ul><li>Create an account on Zenodo that is linked to your Github
+<p>Note: for this exercise, you should use the <a href="https://sandbox.zenodo.org/" class="external-link">Sandbox Zenodo</a> (which is a
+version of Zenodo for testing and playing with before minting a real
+DOI) to avoid polluting the DOI space with test repositories we use for
+this course.</p>
+<ul><li>Create an account on Zenodo that is linked to your GitHub
 account.</li>
 <li>Use Zenodo to create a release for your repository and obtain a DOI
 for it.</li>
@@ -545,12 +570,12 @@ <h3 class="callout-title">Archive your repository to Zenodo</h3>
 <i class="callout-icon" data-feather="bell"></i>
 </div>
 <div id="problems-with-github-and-zenodo-integration" class="callout-inner">
-<h3 class="callout-title">Problems with Github and Zenodo integration</h3>
+<h3 class="callout-title">Problems with GitHub and Zenodo integration</h3>
 <div class="callout-content">
-<p>The integration between Github and Zenodo does not interact well with
+<p>The integration between GitHub and Zenodo does not interact well with
 some browser privacy features and extensions. Firefox can be
 particularly problematic with this and might open new tabs to login to
-Github and then give an error saying:
+GitHub and then give an error saying:
 <code>Your browser did something unexpected.  Please try again. If the error continues, try disabling all browser extensions.</code>
 If this happens try disabling the extra privacy features/extensions or
 using another browser such as Chrome.</p>
@@ -561,35 +586,49 @@ <h3 class="callout-title">Problems with Github and Zenodo integration</h3>
 <div class="section level3">
 <h3 id="adding-a-doi-and-orcid-to-the-citation-file">Adding a DOI and ORCID to the citation file<a class="anchor" aria-label="anchor" href="#adding-a-doi-and-orcid-to-the-citation-file"></a></h3>
 <p>Now that we have our DOI it is good practice to include this
-information in our citation file. In the previous part of this lesson we
-created a <code>CITATION.cff</code> file with information about how to
-cite our code. There are a few fields we can add which are related to
-the DOI, one of these is the <code>version</code> file which covers the
+information in our citation file. Earlier we created a
+<code>CITATION.cff</code> file with information about how to cite our
+code. There are a few fields we can add now which are related to the
+DOI; one of these is the <code>version</code> file which covers the
 version number of the software. We can add a DOI to the file in the
 <code>identifiers</code> section with a type of <code>doi</code> and
-<code>value</code> with the URL. Optionally we can also add a
+<code>value</code> of the Zenodo URL. Optionally we can also add a
 <code>date-released</code> field indicating the date we released this
-software. Here is an updated version of our CITATION.cff from the
-previous episode with a version number, DOI and release date added.</p>
+software. Here is an updated version of our <code>CITATION.cff</code>
+from the previous episode with a version number, DOI and release date
+added.</p>
 <div class="codewrapper sourceCode" id="cb3">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb3-1"><a href="#cb3-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
 <span id="cb3-2"><a href="#cb3-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb3-3"><a href="#cb3-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb3-4"><a href="#cb3-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
-<span id="cb3-5"><a href="#cb3-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb3-6"><a href="#cb3-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb3-7"><a href="#cb3-7" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb3-8"><a href="#cb3-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb3-9"><a href="#cb3-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb3-10"><a href="#cb3-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
-<span id="cb3-11"><a href="#cb3-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span>
-<span id="cb3-12"><a href="#cb3-12" tabindex="-1"></a><span class="fu">version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.0.1</span></span>
-<span id="cb3-13"><a href="#cb3-13" tabindex="-1"></a><span class="fu">identifiers</span><span class="kw">:</span></span>
-<span id="cb3-14"><a href="#cb3-14" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> doi</span></span>
-<span id="cb3-15"><a href="#cb3-15" tabindex="-1"></a><span class="at">    </span><span class="fu">value</span><span class="kw">:</span><span class="at"> 10.5281/zenodo.1234</span></span>
-<span id="cb3-16"><a href="#cb3-16" tabindex="-1"></a><span class="fu">date-released</span><span class="kw">:</span><span class="at"> 2024-06-01</span></span></code></pre>
+<span id="cb3-3"><a href="#cb3-3" tabindex="-1"></a></span>
+<span id="cb3-4"><a href="#cb3-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb3-5"><a href="#cb3-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
+<span id="cb3-6"><a href="#cb3-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-7"><a href="#cb3-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb3-8"><a href="#cb3-8" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb3-9"><a href="#cb3-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb3-10"><a href="#cb3-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb3-11"><a href="#cb3-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
+<span id="cb3-12"><a href="#cb3-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
+<span id="cb3-13"><a href="#cb3-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
+<span id="cb3-14"><a href="#cb3-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
+<span id="cb3-15"><a href="#cb3-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
+<span id="cb3-16"><a href="#cb3-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
+<span id="cb3-17"><a href="#cb3-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-18"><a href="#cb3-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
+<span id="cb3-19"><a href="#cb3-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-20"><a href="#cb3-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
+<span id="cb3-21"><a href="#cb3-21" tabindex="-1"></a>  data</span>
+<span id="cb3-22"><a href="#cb3-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
+<span id="cb3-23"><a href="#cb3-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
+<span id="cb3-24"><a href="#cb3-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span>
+<span id="cb3-25"><a href="#cb3-25" tabindex="-1"></a><span class="fu">version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.0.1</span></span>
+<span id="cb3-26"><a href="#cb3-26" tabindex="-1"></a><span class="fu">identifiers</span><span class="kw">:</span></span>
+<span id="cb3-27"><a href="#cb3-27" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> doi</span></span>
+<span id="cb3-28"><a href="#cb3-28" tabindex="-1"></a><span class="at">    </span><span class="fu">value</span><span class="kw">:</span><span class="at"> 10.5281/zenodo.1234</span></span>
+<span id="cb3-29"><a href="#cb3-29" tabindex="-1"></a><span class="fu">date-released</span><span class="kw">:</span><span class="at"> 2024-06-01</span></span></code></pre>
 </div>
 <div id="add-a-doi-to-your-citation-file" class="callout discussion">
 <div class="callout-square">
@@ -599,10 +638,11 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="callout-title">Add a DOI to your citation file</h3>
 <div class="callout-content">
 <p>Add the DOI you were allocated in the previous exercise to your
-CITATION.cff file and commit/push the updated version to your Github
-repository. You can remove the <code>commit</code> field from the
-CITATION.cff file as the DOI is a better way to point to given version
-of the code.</p>
+<code>CITATION.cff</code> file and then commit and push the updated
+version to your GitHub repository. If you used the <code>commit</code>
+field in your <code>CITATION.cff</code> file before to point to a given
+version of the code - you can now remove it as using the DOI field is
+better for this job.</p>
 </div>
 </div>
 </div>
@@ -631,24 +671,24 @@ <h3 class="callout-title">Going further with publishing code</h3>
 </div>
 </div>
 </section><section><h2 class="section-heading" id="working-with-collaborators">Working with collaborators<a class="anchor" aria-label="anchor" href="#working-with-collaborators"></a></h2>
-<hr class="half-width"><p>The strength of online collaboration tools such as Github doesn’t
-just lie in the ability to share code. They also allow us to track
+<hr class="half-width"><p>The strength of online collaboration platforms such as GitHub does
+not just lie in the ability to share code. They also allow us to track
 problems with that code, for multiple developers to work on it
 independently and bring their changes together and to review those
 changes before they are accepted.</p>
 <div class="section level3">
 <h3 id="tracking-issues-with-code">Tracking issues with code<a class="anchor" aria-label="anchor" href="#tracking-issues-with-code"></a></h3>
-<p>A key feature of Github (as opposed to Git itself) is the issue
+<p>A key feature of GitHub (as opposed to Git itself) is the issue
 tracker. This provides us with a place to keep track of any problems or
 bugs in the code and to discuss them with other developers. Sometimes
 advanced users will also use issue trackers of public projects to report
 problems they are having (and sometimes this is misused by users seeking
 help using documented features of the program).</p>
 <p>The code from the testing chapter earlier has a bug with an extra
-bracket in eva_data_analysis.py (and if you’ve fixed that a missing
+bracket in eva_data_analysis.py (and if you have fixed that a missing
 import of summarise_categorical in the test). Let’s go ahead and create
-a new issue in our Github repository to describe this problem. We can
-find the issue tracker on the “Issues” tab in the top left of the Github
+a new issue in our GitHub repository to describe this problem. We can
+find the issue tracker on the “Issues” tab in the top left of the GitHub
 page for the repository. Click on this and then click on the green “New
 Issue” button on the right hand side of the screen. We can then enter a
 title and description of our issue.</p>
@@ -671,7 +711,7 @@ <h3 class="callout-title">Write an issue to describe our bug</h3>
 <div class="callout-content">
 <p>Create a new issue in your repository’s issue tracker by doing the
 following:</p>
-<ul><li>Go to the Github webpage for your code</li>
+<ul><li>Go to the GitHub webpage for your code</li>
 <li>Click on the Issues tab</li>
 <li>Click on the “New issue” button</li>
 <li>Enter a title and description for the issue</li>
@@ -692,7 +732,7 @@ <h3 id="discussing-an-issue">Discussing an issue<a class="anchor" aria-label="an
 <div class="section level3">
 <h3 id="closing-an-issue">Closing an issue<a class="anchor" aria-label="anchor" href="#closing-an-issue"></a></h3>
 <p>Once an issue is solved then it can be closed. This can be done
-either by pressing the “Close” button in the Github web interface or by
+either by pressing the “Close” button in the GitHub web interface or by
 making a commit which includes the word “fixes”, “fixed”, “close”,
 “closed” or “closes” followed by a # symbol and the issue number.</p>
 </div>
@@ -703,36 +743,37 @@ <h3 id="working-in-parallel-with-git-branches">Working in parallel with Git bran
 with another. Branches are commonly used as a way for one developer to
 work on a new feature or a bug fix while other developers work on other
 features. When those new features or bug fixes are complete, the branch
-will be merged back with the main (sometimes called master) branch.</p>
+will be merged back with the <code>main</code> (sometimes called the
+<code>master</code>) branch.</p>
 <div class="section level4">
 <h4 id="creating-a-new-branch">Creating a new branch<a class="anchor" aria-label="anchor" href="#creating-a-new-branch"></a></h4>
-<p>New git branches are created with the <code>git branch</code>
+<p>New Git branches are created with the <code>git branch</code>
 command. This should be followed by the name of the branch to create. It
 is common practice when the bug we are fixing has a corresponding issue
 to name the branch after the issue number and name. For example, we
-might call the branch <code>01-extra-brakcet-bug</code> instead of
+might call the branch <code>01-extra-bracket-bug</code> instead of
 something less descriptive like <code>bugfix</code>.</p>
 <p>For example, the command:</p>
 <div class="codewrapper sourceCode" id="cb4">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="fu">git</span> branch 01-extra-brakcet-bug</span></code></pre>
-</div>
-<p>will create a new branch called <code>01-extra-brakcet-bug</code>. We
-can view the names of all the branches, by default there should be one
-branch called <code>main</code> or perhaps <code>master</code> and our
-new <code>01-extra-brakcet-bug</code> branch. by running
-<code>git branch</code> with no parameters. This will put <code>*</code>
-next to the currently active branch.</p>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git branch 01-extra-bracket-bug</span></code></pre>
+</div>
+<p>will create a new branch called <code>01-extra-bracket-bug</code>. We
+can view the names of all the branches by running
+<code>git branch</code> with no parameters. By default there should be
+one branch called <code>main</code> (formerly <code>master</code>) and
+our new <code>01-extra-bracket-bug</code> branch. The command will put
+<code>*</code> next to the currently active branch.</p>
 <div class="codewrapper sourceCode" id="cb5">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" tabindex="-1"></a><span class="fu">git</span> branch</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git branch</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="output" tabindex="0"><code>  01-extra-brakcet-bug
+<pre class="output" tabindex="0"><code>  01-extra-bracket-bug
 * main</code></pre>
 </div>
 <p>We can see that creating a new branch has not activated that branch.
@@ -742,27 +783,27 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="fu">git</span> switch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch 01-extra-bracket-bug</span></code></pre>
 </div>
 <p>To create a branch and change to it in a single command we can use
 <code>git switch</code> with the <code>-c</code> option (or
-<code>git checkout</code> with the <code>-b</code> option,
-<code>git switch</code> is only found in more recent versions of
-Git).</p>
+<code>git checkout</code> with the <code>-b</code> option). Note that
+<code>git switch</code> command is only available in more recent
+versions of Git.</p>
 <div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="fu">git</span> switch <span class="at">-c</span> 02-another-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch <span class="at">-c</span> 02-another-bug</span></code></pre>
 </div>
 </div>
 <div class="section level4">
 <h4 id="committing-to-a-branch">Committing to a branch<a class="anchor" aria-label="anchor" href="#committing-to-a-branch"></a></h4>
 <p>Once we have switched to a branch any further commits that are made
-will go to that branch. When we run a <code>git commit</code> command
-we’ll see the name of the branch we’re committing to in the output of
+will go to that branch. When we run a <code>git commit</code> command we
+will see the name of the branch we are committing to in the output of
 <code>git commit</code>. Let’s edit our code and fix the lack of default
 values bug that we entered into the issue tracker earlier on.</p>
-<p>Change your code from</p>
+<p>Change your code from:</p>
 <div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -778,7 +819,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb11">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"fixed bug"</span> eva_data_analysis.py</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"fixed bug"</span> eva_data_analysis.py</span></code></pre>
 </div>
 <p>In the output of <code>git commit -m</code> the first part of the
 output line will show the name of the branch we just made the commit
@@ -794,14 +835,14 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">git</span> switch main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch main</span></code></pre>
 </div>
-<p>And if we go back to the <code>01-extra-brakcet-bug</code> branch it
+<p>And if we go back to the <code>01-extra-bracket-bug</code> branch it
 will re-appear.</p>
 <div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="fu">git</span> switch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch 01-extra-bracket-bug</span></code></pre>
 </div>
 <p>If we want to push our changes to a remote such as GitHub we have to
 tell the <code>git push</code> command which branch to push to. If the
@@ -810,18 +851,18 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="codewrapper sourceCode" id="cb15">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">git</span> push origin 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin 01-extra-bracket-bug</span></code></pre>
 </div>
-<p>If we now refresh the Github webpage for this repository we should
+<p>If we now refresh the GitHub webpage for this repository we should
 see the bugfix branch has appeared in the list of branches.</p>
 <p>If we needed to pull changes from a branch on a remote (for example
-if we’ve made changes on another computer or via Github’s web based
+if we have made changes on another computer or via GitHub’s web based
 editor), then we can specify a branch on a <code>git pull</code>
 command.</p>
 <div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">git</span> pull origin 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">git</span> pull origin 01-extra-bracket-bug</span></code></pre>
 </div>
 </div>
 </div>
@@ -830,19 +871,19 @@ <h3 id="merging-branches">Merging branches<a class="anchor" aria-label="anchor"
 <p>When we have completed working on a branch (for example fixing a bug)
 then we can merge our branch back into the main one (or any other
 branch). This is done with the <code>git merge</code> command.</p>
-<p>This must be run on the <em>TARGET</em> branch of the merge, so we’ll
-have to use a <code>git switch</code> command to set this.</p>
+<p>This must be run on the <em>TARGET</em> branch of the merge, so we
+will have to use a <code>git switch</code> command to set this.</p>
 <div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="fu">git</span> switch main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch main</span></code></pre>
 </div>
-<p>Now we’re back on the main branch we can go ahead and merge the
+<p>Now we are back on the main branch we can go ahead and merge the
 changes from the bugfix branch:</p>
 <div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="fu">git</span> merge 01-extra-bracket-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git merge 01-extra-bracket-bug</span></code></pre>
 </div>
 </div>
 <div class="section level3">
@@ -850,25 +891,26 @@ <h3 id="pull-requests">Pull requests<a class="anchor" aria-label="anchor" href="
 <p>On larger projects we might need to have a code review process before
 changes are merged, especially before they are merged onto the main
 branch that might be what is being released as the public version of the
-software. Github has a process for this that it calls a “Pull Request”,
-other Git services such as GitLab have different names for this, GitLab
-calls them “Merge Requests”. Pull requests are where one developer
-requests that another merge code from a branch (or “pull” it from
-another copy of the repository). The person receiving the request then
-has the chance to review the code, write comments suggesting changes or
-even change the code themselves before merging it. It is also very
-common for automated checks of code to be run on a pull request to
-ensure the code is of good quality and is passing automated tests.</p>
+software. GitHub has a process for this that is called a <strong>pull
+request</strong>. Other Git services such as GitLab have different names
+for this; GitLab calls them <strong>merge requests</strong>. Pull
+requests are situations where one developer requests that another merges
+code from a branch (or “pull” it from another copy of the repository).
+The person receiving the request then has the chance to review the code,
+write comments suggesting changes or even change the code themselves
+before merging it. It is also very common for automated checks of code
+to be run on a pull request to ensure the code is of good quality and is
+passing automated tests.</p>
 <p>As a simple example of a pull request, we can now create a pull
 request for the changes we made on our <code>01-extra-bracket-bug</code>
-branch and pushed to Github earlier on. The Github webpage for our
-repository will now be saying something like “bugfix had recent pushes n
-minutes ago - Compare &amp; Pull request”. Click on this button and
-create a new pull request.</p>
+branch and pushed to GitHub earlier on. The GitHub webpage for our
+repository will now be saying something like “bugfix had recent pushes
+<code>n</code> minutes ago - Compare &amp; Pull request”. Click on this
+button and create a new pull request.</p>
 <p>Give the pull request a title and write a brief description of it,
-then click the green “Create pull request” button. Github will then
-check if we can merge this pull request without any problems. We’ll look
-at what to do when this isn’t possible later on.</p>
+then click the green “Create pull request” button. GitHub will then
+check if we can merge this pull request without any problems. We will
+look at what to do when this is not possible later on.</p>
 <p>There should be a green “Merge pull request” button, but if we click
 on the down arrow inside this button there are three options on how to
 handle this request:</p>
@@ -890,66 +932,57 @@ <h3 id="pull-requests">Pull requests<a class="anchor" aria-label="anchor" href="
 kind of merge they will prefer. For the purposes of this exercise we’ll
 stick with the default merge commit.</p>
 <p>Go ahead and click on “Merge pull request”, then “Confirm merge”. The
-changes will now be merged together. Github gives us the option to
-delete the branch we were working on, since it’s history is preserved in
-the main branch there isn’t any reason to keep it.</p>
+changes will now be merged together. GitHub gives us the option to
+delete the branch we were working on, since its history is preserved in
+the main branch there is no reason to keep it.</p>
 <div class="section level4">
 <h4 id="using-forks-instead-of-branches">Using forks instead of branches<a class="anchor" aria-label="anchor" href="#using-forks-instead-of-branches"></a></h4>
 <p>A fork is similar to a branch, but instead of it being part of the
 same repository it is a entirely new copy of the repository. Forks are
-commonly used by Github users who wish to work on a project that they’re
-not a member of. Typically forking will copy the repository to our own
-namespace (e.g. github.com/username/reponame instead of
+commonly used by Github users who wish to work on a project that they
+are not a member of. Typically forking will copy the repository to our
+own namespace (e.g. github.com/username/reponame instead of
 github.com/projectname/reponame)</p>
 <p>To create a fork on github use the “Fork” button to the right of the
 repository name. After we create our fork we can make some changes and
 these could even be on the main branch inside our forked repository.
-Github will track that a fork has been made displays a “Contribute”
+GitHub will track that a fork has been made displays a “Contribute”
 button to create a pull request back to the original repository. Using
 this we can request that the changes on our fork are incorporated by the
 upstream project.</p>
-<div id="pull-request-exercise" class="callout discussion">
+<div id="practice-pull-requests" class="callout discussion">
 <div class="callout-square">
 <i class="callout-icon" data-feather="message-circle"></i>
 </div>
-<div id="pull-request-exercise" class="callout-inner">
-<h3 class="callout-title">Pull request exercise</h3>
+<div id="practice-pull-requests" class="callout-inner">
+<h3 class="callout-title">Practice pull requests</h3>
 <div class="callout-content">
-<p>Q: Work in pairs for this exercise. Share the Github link of your
+<p>Q: Work in pairs for this exercise. Share the GitHub link of your
 repository with your partner. If you have set your repository to
-private, you’ll need to add them as a collaborator. Go to the settings
-page on your Github repository’s webpage, click on Collaborators from
+private, you will need to add them as a collaborator. Go to the settings
+page on your GitHub repository’s webpage, click on Collaborators from
 the left hand menu and then click the green “Add People” button and
-enter the Github username or email address of your partner. They will
-get an email and an alert within Github to accept your invitation to
+enter the GitHub username or email address of your partner. They will
+get an email and an alert within GitHub to accept your invitation to
 work on this repository, without doing this they won’t be able to access
 it.</p>
 <ul><li>Now make a fork of your partners repository.</li>
-<li>Edit the CITATION.cff file and add your name to it.</li>
+<li>Edit the <code>CITATION.cff</code> file and add your name to
+it.</li>
 <li>Commit these changes to your fork</li>
 <li>Create a pull request back to the original repository</li>
 <li>Your partner will now receive your pull request and can review</li>
 </ul></div>
 </div>
 </div>
-<div id="commit-and-push-your-changes" class="callout">
-<div class="callout-square">
-<i class="callout-icon" data-feather="bell"></i>
-</div>
-<div id="commit-and-push-your-changes" class="callout-inner">
-<h3 class="callout-title">Commit and push your changes</h3>
-<div class="callout-content">
-<p>Do not forget to commit any uncommited changes you may have and then
+<p>Do not forget to commit any uncommitted changes you may have and then
 push your work to GitHub.</p>
 <div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="fu">git</span> add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
-<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
-<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
-</div>
-</div>
-</div>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
+<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 </div>
 </div>
@@ -959,7 +992,7 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <ul><li>Licencing and citation episodes from the <a href="https://swcarpentry.github.io/git-novice" class="external-link">Software Carpentry’s Git
 Novice lesson</a>
 </li>
-<li>Carpentries Github Skill ups for <a href="https://carpentries-incubator.github.io/github-skill-up-instructors/" class="external-link">instructors</a>
+<li>Carpentries GitHub Skill ups for <a href="https://carpentries-incubator.github.io/github-skill-up-instructors/" class="external-link">instructors</a>
 and <a href="https://carpentries.github.io/github-skill-up-maintainers/" class="external-link">maintainers</a>
 </li>
 <li>
@@ -982,26 +1015,13 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="callout-inner">
 <h3 class="callout-title">Key Points</h3>
 <div class="callout-content">
-<ul><li>Open source applies Copyright licenses permitting others to reuse
-and adapt your code or data.</li>
-<li>Permissive licenses allow code to be used in other products
-providing the copyright statement is displayed.</li>
-<li>Copyleft licenses require the source code of any modifications to be
-released under a copyleft license.</li>
-<li>Creative commons licenses are suitable for non-code files such as
-documentation and images.</li>
-<li>Open source software can be sold, but you must supply the source
-code and the people you sell it to can give it away to somebody
-else.</li>
-<li>Add license file to your repository and add a license to each file
-in case it gets detached.</li>
-<li>Zenodo can be used to archive a Github repository and obtain a DOI
+<ul><li>Zenodo can be used to archive a GitHub repository and obtain a DOI
 for it.</li>
-<li>We can include a CITATION file to tell people how to cite our
-code.</li>
-<li>Github can track bugs or issues with a program.</li>
+<li>We include a CITATION file with our code to tell people how to cite
+it.</li>
+<li>GitHub can help us track bugs or issues with software.</li>
 <li>Git branches can be used to allow multiple developers to work on the
-same part of a program in parallel.</li>
+same part of code in parallel.</li>
 <li>The <code>git branch</code> command shows the list of branches and
 can create new branches.</li>
 <li>The <code>git switch</code> command changes which branch we are
@@ -1054,7 +1074,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1071,13 +1091,13 @@ <h3 class="callout-title">Key Points</h3>
   "dct:conformsTo": "https://bioschemas.org/profiles/TrainingMaterial/1.0-RELEASE",
   "description": "A Carpentries Lesson teaching foundational data and coding skills to researchers worldwide",
   "keywords": "software, FAIR, reproducibility, sustainability, open, research, lesson, The Carpentries",
-  "name": "Open collaboration on code",
+  "name": "Open code &amp;amp; collaboration",
   "creativeWorkStatus": "active",
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/10-open-collaboration.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/10-open-collaboration.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-09-24",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/11-wrap-up.html b/instructor/11-wrap-up.html
index c106dcd8..8197ea13 100644
--- a/instructor/11-wrap-up.html
+++ b/instructor/11-wrap-up.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -363,7 +363,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       <div class="d-none d-sm-none d-md-block">
         <a class="chapter-link" href="../instructor/10-open-collaboration.html" rel="prev">
           <i aria-hidden="true" class="small-arrow" data-feather="arrow-left"></i>
-          Previous: Open collaboration
+          Previous: Open code &amp;
         </a>
         <a class="chapter-link float-end" href="../instructor/index.html" rel="next">
           Home
@@ -474,7 +474,7 @@ <h3 class="callout-title">Key Points</h3>
       <div class="d-none d-sm-none d-md-block">
         <a class="chapter-link" href="../instructor/10-open-collaboration.html" rel="prev">
           <i aria-hidden="true" class="small-arrow" data-feather="arrow-left"></i>
-          Previous: Open collaboration
+          Previous: Open code &amp;
         </a>
         <a class="chapter-link float-end" href="../instructor/index.html" rel="next">
           Home
@@ -501,7 +501,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -524,7 +524,7 @@ <h3 class="callout-title">Key Points</h3>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/11-wrap-up.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-09-17",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/404.html b/instructor/404.html
index 386964c5..30106323 100644
--- a/instructor/404.html
+++ b/instructor/404.html
@@ -310,7 +310,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="https://softwaresaved.github.io/fair-research-software/10-open-collaboration.html" class="external-link">10. Open collaboration on code</a>
+        <a href="https://softwaresaved.github.io/fair-research-software/10-open-collaboration.html" class="external-link">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -415,7 +415,7 @@ <h1>Page not found</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -437,8 +437,8 @@ <h1>Page not found</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/404.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/404.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/AUTHORS.html b/instructor/AUTHORS.html
index ad333648..bdce558f 100644
--- a/instructor/AUTHORS.html
+++ b/instructor/AUTHORS.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -418,7 +418,7 @@ <h1>Authors</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -441,7 +441,7 @@ <h1>Authors</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/AUTHORS.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-03-04",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/CODE_OF_CONDUCT.html b/instructor/CODE_OF_CONDUCT.html
index 01a790bf..e30073e7 100644
--- a/instructor/CODE_OF_CONDUCT.html
+++ b/instructor/CODE_OF_CONDUCT.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -423,7 +423,7 @@ <h1>Contributor Code of Conduct</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -446,7 +446,7 @@ <h1>Contributor Code of Conduct</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/CODE_OF_CONDUCT.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/LICENSE.html b/instructor/LICENSE.html
index 49135bf1..5bc6ff73 100644
--- a/instructor/LICENSE.html
+++ b/instructor/LICENSE.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -471,7 +471,7 @@ <h1>Licenses</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -494,7 +494,7 @@ <h1>Licenses</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/LICENSE.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/aio.html b/instructor/aio.html
index 7195664d..2469f74a 100644
--- a/instructor/aio.html
+++ b/instructor/aio.html
@@ -355,7 +355,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -759,7 +759,7 @@ <h3 class="callout-title">What does open and reproducible research mean
  -->
 </section></section><section id="aio-02-fair-research-software"><p>Content from <a href="02-fair-research-software.html">FAIR research software</a></p>
 <hr>
-<p>Last updated on 2024-07-04 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/02-fair-research-software.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 60 minutes</p>
@@ -849,48 +849,66 @@ <h3 class="callout-title">Motivation</h3>
 below is not exhaustive, but any of the practices that you employ in
 your research software workflow will bring you closer to the gold
 standard of a fully reproducible research.</p>
+<div class="section level3">
+<h3 id="findable">Findable<a class="anchor" aria-label="anchor" href="#findable"></a>
+</h3>
+<p>In order to make your software more findable, you should:</p>
 <ul>
-<li>Findable
-<ul>
-<li>Create a description of your software</li>
+<li>Create a description of your software to make it discoverable by
+search engines and other search tools</li>
 <li>Place your software in a public software repository (and ideally
-register it in a <a href="https://github.com/NLeSC/awesome-research-software-registries" class="external-link">software
-registry</a>)</li>
+register it in a [general-purpose or domain-specific software
+registry][software-registries])</li>
 <li>Use a unique and persistent identifier (DOI) for your software
-(e.g. by depositing your code on Zenodo), which is also useful for
+(e.g. by depositing your code on <a href="https://zenodo.org/" class="external-link">Zenodo</a>), which is also useful for
 citations - note that depositing your data/code on GitHub and similar
 software repositories may not be enough as they may change their open
-access model or disappear completely in the future</li>
+access model or disappear completely in the future, so archiving your
+code means it stands a better chance at being preserved</li>
 </ul>
-</li>
-<li>Accessible
+</div>
+<div class="section level3">
+<h3 id="accessible">Accessible<a class="anchor" aria-label="anchor" href="#accessible"></a>
+</h3>
+<p>In order to make your software more accessible, you should:</p>
 <ul>
 <li>Make sure people can freely, legally and easily get a copy your
 software</li>
-<li>Use coding conventions and comments to make your code readable and
-understandable by people (once they get a copy of it)</li>
+<li>Use code style conventions and code structure patterns, use comments
+and create documentation to make your code comprehensible by people
+(once they get a copy of it) - i.e. make your code accessible in the
+<em>intelligible</em> sense</li>
 </ul>
-</li>
-<li>Interoperable
+</div>
+<div class="section level3">
+<h3 id="interoperable">Interoperable<a class="anchor" aria-label="anchor" href="#interoperable"></a>
+</h3>
+<p>In order to make your software more interoperable, you should:</p>
 <ul>
-<li>Explain the functionality of your software</li>
+<li>Explain the functionality of your software, so others can understand
+how other tools can interoperate with it</li>
 <li>Use standard formats for inputs and outputs</li>
 <li>Communicate with other software via standard protocols and APIs</li>
 </ul>
-</li>
-<li>Reusable
+</div>
+<div class="section level3">
+<h3 id="reusable">Reusable<a class="anchor" aria-label="anchor" href="#reusable"></a>
+</h3>
+<p>In order to make your software more reusable, you should:</p>
 <ul>
 <li>Document your software (including its functionality, and how to
-install and run it)</li>
-<li>Follow best practices for software development (including coding
-conventions, code readability and verifying its correctness)</li>
+install and run it) to make it more understandable by others who may
+wish to reuse or extend it</li>
+<li>Follow best practices for software development (including code
+conventions, structure, readability and correctness)</li>
 <li>Test your software and make sure it works on different
-platforms/operating systems</li>
+platforms/operating systems to make it more reusable</li>
 <li>Give a licence to your software clearly stating how it can be
 reused</li>
-<li>State how to cite your software</li>
-</ul>
-</li>
+<li>State how to cite your software, so people can give you credit when
+they reuse it</li>
+<li>Include a contributor policy so that others can contribute to your
+code and credit for contributions is provided</li>
 </ul>
 <div id="fair-is-a-process-not-a-perfect-metric" class="callout">
 <div class="callout-square">
@@ -899,7 +917,7 @@ <h3 class="callout-title">Motivation</h3>
 <div id="fair-is-a-process-not-a-perfect-metric" class="callout-inner">
 <h3 class="callout-title">FAIR is a process, not a perfect metric</h3>
 <div class="callout-content">
-<p>FAIR is not a binary metric - there is no such thing as “FAIR or not
+<p>FAIR is not a binary metric - there is no such thing as “FAIR or”not
 FAIR”.</p>
 <p>FAIR is not a perfect metric, nor does it provide a full and
 exhaustive software quality checklist. Software may be FAIR but still
@@ -944,15 +962,17 @@ <h3 class="callout-title">Challenge</h3>
 </div>
 </div>
 </div>
+</div>
 </section><section><h2 class="section-heading" id="software-and-data-used-in-this-course">Software and data used in this course<a class="anchor" aria-label="anchor" href="#software-and-data-used-in-this-course"></a>
 </h2>
 <hr class="half-width">
 <p>We are going to follow a fairly typical experience of a new PhD or
 postdoc joining a research group. They were emailed some data and
 analysis code bundled in a <code>.zip</code> archive and written by
-another group member who works on similar things. They need to be able
-to install and run this code on their machine, check they understand it
-and then adapt it to their own project.</p>
+another group member who worked on similar things but has since left the
+group. They need to be able to install and run this code on their
+machine, check they can understand it and then adapt it to their own
+project.</p>
 <p>As part of the <a href="./index.html#astronaut-data-and-analysis-code">setup for this
 course</a>, you should have downloaded a <code>.zip</code> archive
 containing the software project the new research team member was given.
@@ -987,10 +1007,11 @@ <h3 class="callout-title">Challenge</h3>
 <div class="callout-inner">
 <h3 class="callout-title">Discussion</h3>
 <div class="callout-content">
-<p>Compare this data and code to the software you chose earlier. Do you
-think it is Findable, Accessible, Interoperable and Reusable? Give it a
-score from 1 to 5 in each category, as in the previous exercise, and
-then we will discuss it together.</p>
+<p>Look at our code in VS Code and compare this data and code to the
+software you chose earlier (or assess it on its own). Do you think it is
+Findable, Accessible, Interoperable and Reusable? Give it a score from 1
+to 5 in each category, as in the previous exercise, and then we will
+discuss it together.</p>
 </div>
 </div>
 </div>
@@ -1164,7 +1185,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-03-tools"><p>Content from <a href="03-tools.html">Tools and practices for FAIR research software development</a></p>
 <hr>
-<p>Last updated on 2024-09-24 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/03-tools.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 90 minutes</p>
@@ -1204,181 +1225,146 @@ <h3 class="card-title">Objectives</h3>
 <p>In this course we will introduce you to a group of tools and
 practices that are commonly used in research to help you develop
 software in a FAIR way. You should already have these tools installed on
-your machine following the setup instructions. Here we will give an
-overview of the tools, how they help you achieve the aims of FAIR
-research software and how they work together. In later episodes we will
-describe some of these tools in more detail.</p>
-<section><h2 class="section-heading" id="development-environment">Development environment<a class="anchor" aria-label="anchor" href="#development-environment"></a>
-</h2>
-<hr class="half-width">
-<p>One of the first choices we make when writing code is what tool to
-use to do the writing. You can use a simple text editor such as Notepad,
-a terminal based editor with syntax highlighting such as Vim or Emacs,
-or one of many Integrated Development Environments (IDEs) which give you
-the tools to write, run and debug your code and inspect the output all
-in one place. Note that you should not use word processing software such
-as Microsoft Word or Apple Pages to write code - these tools are
-designed to create nicely formatted text for humans to read, so they may
-add or change formatting, or insert invisible characters that the
-programming language cannot interpret. Try opening a Word document in
-Notepad to see an example.</p>
-<p>This is mostly a personal choice as an experienced user of any of
-these tools can write good, FAIR software efficiently, but IDEs are
-popular because they are designed specifically for writing and running
-code. There are some language specific IDEs such as PyCharm, and some
-that can work with many languages like VS Code (Visual Studio Code).
-IDEs also have add-ons that provide extra functionality, such as
-checking your code as you type (similar to a spell-checker in Word),
-highlighting when you are not following best practice, or even
-automatically generating bits of code for you.</p>
-<div id="accordionInstructor1" class="accordion instructor-note accordion-flush">
-<div class="accordion-item">
-<button class="accordion-button instructor-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseInstructor1" aria-expanded="false" aria-controls="collapseInstructor1">
-  <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square"><i aria-hidden="true" class="callout-icon" data-feather="edit-2"></i></div> Instructor Note </h3>
-</button>
-<div id="collapseInstructor1" class="accordion-collapse collapse" aria-labelledby="headingInstructor1" data-bs-parent="#accordionInstructor1">
-<div class="accordion-body">
-<p>At this point you could open the Python file or another file in VS
-Code to show all the squiggly lines suggesting improvements.</p>
+your machine following the <a href="./index.html#astronaut-data-and-analysis-code">setup
+instructions</a>. Here we will give an overview of the tools, how they
+help you achieve the aims of FAIR research software and how they work
+together. In later episodes we will describe some of these tools in more
+detail.</p>
+<div class="section level3">
+<h3 id="development-environments">Development environments<a class="anchor" aria-label="anchor" href="#development-environments"></a>
+</h3>
+<p>Virtual and integrated development environments (IDEs), such as VS
+Code or PyCharm, help with running, testing, and debugging code. Virtual
+environments further enable us to share our working environments with
+others, making it easier to access, reuse and extend our code. IDEs
+often provide integrations with other tools, e.g. version control and
+command line terminals, enabling you to do many tasks from a single
+environment, saving time in switching between different tools.</p>
 </div>
+<div class="section level3">
+<h3 id="command-line-terminals">Command line terminals<a class="anchor" aria-label="anchor" href="#command-line-terminals"></a>
+</h3>
+<p>Command line terminals (e.g. Bash, GitBash) enable us to run and test
+our code without graphical user interfaces (GUI) afforded to us by IDEs
+- this is sometimes needed for accessing and running our code remotely
+on servers and high-performance systems without a GUI provision, where
+time, memory and processing power are expensive or in high demand.</p>
+<p>Version control systems are typically provided as command line tools,
+making them often only accessible from command line terminals to enter
+commands and access remote version control servers to backing up and
+sharing our work.</p>
+<p>Finally, command line tools use standard protocols for passing
+parameters, inputs and outputs. This makes it easier to integrate ours
+with other command line tools, allowing us to chain them and build up
+complex and reproducible workflows and analysis pipelines using several
+programs in different steps. If we write our software in a way which
+provides such an interoperable command line interface - we will be able
+to integrate it with other command line tools to automate and speed up
+our work.</p>
 </div>
+<div class="section level3">
+<h3 id="standard-inputoutput-formats-and-communication-protocols">Standard input/output formats and communication protocols<a class="anchor" aria-label="anchor" href="#standard-inputoutput-formats-and-communication-protocols"></a>
+</h3>
+<p>Using standard data exchange, input and output formats and
+communication protocols helps create interoperable software that can
+more readily integrate with other tools into more complex pipelines -
+increasing its interoperability and reusability.</p>
 </div>
+<div class="section level3">
+<h3 id="version-control-tools">Version control tools<a class="anchor" aria-label="anchor" href="#version-control-tools"></a>
+</h3>
+<p>Version control means knowing what changes were made to your code,
+when and by whom - promoting code ownership, responsibility and credit.
+When combined with software sharing and collaborative platforms such as
+GitHub or GitLab, it facilitates code publication, sharing and
+findability, teamwork and discussions about software and design
+decisions, provides backup facilities for your code and speeds up
+collaboration on shared code by allowing edits by more than one person
+at a time.</p>
 </div>
-<p>In this course we will use VS Code IDE, as it is free, available on
-Windows, Mac and Linux operating systems, and can be used with many
-programming languages. It is a single tool in which we can:</p>
-<ul>
-<li>view our file system</li>
-<li>open many kinds of files</li>
-<li>edit, compile, run and debug code</li>
-<li>open a terminal to run command line tools (including version control
-tool Git) or view code outputs</li>
-</ul>
-<p>Use VS Code to open the Python script and the data file from our
-project.</p>
-</section><section><h2 class="section-heading" id="command-line-toolshell">Command line tool/shell<a class="anchor" aria-label="anchor" href="#command-line-toolshell"></a>
-</h2>
-<hr class="half-width">
-<p>In VS Code and similar IDEs you can often run the code by clicking a
-button or pressing some keyboard shortcut. If you gave your code to a
-colleague or collaborator they might use the same IDE or something
-different, so you cannot guarantee that they will have the same buttons
-and shortcuts as you.</p>
-<p>In the previous episode we mentioned that interoperable software
-should use standard protocols so that it can integrate with other tools.
-One of these standard protocols/tools is using the inputs and outputs
-via the command line terminal or shell. Command line terminal provides
-one of the oldest ways of interacting with operating system so many
-programs will have command line interfaces. Command line terminals, such
-as Bash and Zsh, have their own language syntax that allow you to write
-scripts and/or group and chain commands together to build up complex
-workflows using several programs in different steps. They also use less
-resources than a graphical user interface tool like an IDE, so are
-commonly used on high-performance computers and other shared systems
-where time, memory and processing power are expensive or in high
-demand.</p>
-<p>In this course we will use the Bash shell, which is one of the most
-common and comes already installed on Mac and Linux operating systems.
-You can create a command line interface to your program which will allow
-it to be run on any system that has a Bash shell, and allow users to
-change things like input and output files or choose different settings
-or parameters without editing your code. With a command line interface,
-your code can be built into automated workflows so that the whole
-process from data gathering to analysis to saving publication-quality
-results can be written in one Bash script and saved and reused.</p>
-</section><section><h2 class="section-heading" id="version-control">Version control<a class="anchor" aria-label="anchor" href="#version-control"></a>
-</h2>
-<hr class="half-width">
-<p>Version control means knowing what changes were made to your code and
-when. Many people who have worked on large documents such as essays
-start doing this by saving files called <code>essay_draft</code>,
-<code>essay_version1.doc</code>, <code>essay_version2.doc</code>, and so
-on. This can work on a small scale but most people find it quickly gets
-confusing which version a certain change was made, or which version is
-the one that you got feedback from a supervisor on. Using a version
-control system helps you keep track of changes, including when you might
-be working on shared code being edited by more than one person at a
-time.</p>
-<p>It also lets you assign version numbers or tags to particular
-versions so you can then use those to refer back to them later. For
-example, you can run your code and output some results and add a comment
-to your output that those results were produced by version 2.4 of your
-code, so if you try to run the same thing later and find it is
-different, you can check if it is a change in the code due to using a
-newer version, or a change in the data, or something else.</p>
-<p>We will be using the Git version control system, which can be used
-through the command line terminal, in a browser or in a desktop
-application.</p>
-</section><section><h2 class="section-heading" id="code-structure-and-style-guidelines">Code structure and style guidelines<a class="anchor" aria-label="anchor" href="#code-structure-and-style-guidelines"></a>
-</h2>
-<hr class="half-width">
-<p>TODO</p>
-</section><section><h2 class="section-heading" id="code-correctness">Code correctness<a class="anchor" aria-label="anchor" href="#code-correctness"></a>
-</h2>
-<hr class="half-width">
+<div class="section level3">
+<h3 id="code-style-and-structure-conventions">Code style and structure conventions<a class="anchor" aria-label="anchor" href="#code-style-and-structure-conventions"></a>
+</h3>
+<p>Following code style conventions for your programming language and
+standard code structure patterns that are agreed upon by the community
+and other programmers are important practices to ensure that others find
+it easy to read your code, reuse or extend it in their own examples and
+applications.</p>
+</div>
+<div class="section level3">
+<h3 id="code-testing">Code testing<a class="anchor" aria-label="anchor" href="#code-testing"></a>
+</h3>
 <p>Testing ensures that your code is correct and does what it is set out
 to do. When you write code you often feel very confident that it is
 perfect, but when writing bigger codes or code that is meant to do
 complex operations it is very hard to consider all possible edge cases
 or notice every single typing mistake. Testing also gives other people
 confidence in your code as they can see an example of how it is meant to
-run and be assured that it does work correctly on their machine.</p>
-<p>We will show different ways to test your code for different purposes.
-You need to think about what it is that is important to you and any
-future users or collaborators to decide what kind of testing is most
-useful for you.</p>
-</section><section><h2 class="section-heading" id="documentation">Documentation<a class="anchor" aria-label="anchor" href="#documentation"></a>
-</h2>
-<hr class="half-width">
-<p>Documentation comes in many forms - from the names of variables and
-functions in your code, additional comments that explain some lines, up
-to a whole website full of documentation with function definitions,
-usage examples, tutorials and guides. You many not need as much
-documentation as a large commercial software product, but making your
-code reusable relies on other people being able to understand what your
-code does and how to use it.</p>
-</section><section><h2 class="section-heading" id="licences-and-citation">Licences and citation<a class="anchor" aria-label="anchor" href="#licences-and-citation"></a>
-</h2>
-<hr class="half-width">
-<p>A licence states what people can legally do with your code, and what
-restrictions you have placed on it. Whenever you want to use someone
-else’s code you should check what license they have and make sure your
-use is legal. You may be restricted by your institution, your grant
-funding, or by other tools you use that require certain licenses for you
-to be compatible with them.</p>
-<p>Having a citation instructions is not a legal requirement but if you
-want to get academic credit for your work, you can make other people’s
-life much easier by telling them how you would like to be credited.
-Similarly, follow citation instructions ensures that when you use
-others’ code in your research they will be credited accordingly.</p>
-<p>Both licensing law and citation procedures can vary depending on your
-country and institution, so remember to check with a local team where
-you are. Your local research IT support or library teams would be a good
-place to start.</p>
-</section><section><h2 class="section-heading" id="code-repositories-and-registries">Code repositories and registries<a class="anchor" aria-label="anchor" href="#code-repositories-and-registries"></a>
-</h2>
-<hr class="half-width">
+run and be assured that it does work correctly on their machine -
+helping with code understanding and reusability.</p>
+</div>
+<div class="section level3">
+<h3 id="software--and-project--level-documentation">Software- and project- level documentation<a class="anchor" aria-label="anchor" href="#software--and-project--level-documentation"></a>
+</h3>
+<p>Documentation comes in many forms - from <strong>software-level
+documentation</strong> including docstrings describing functions and
+classes and in-line comments that explain lines of your code, to
+<strong>project-level documentation</strong> and
+<strong>metadata</strong> (including README, LICENCE, CITATION,
+CONTRIBUTING, etc. files) that help to discover it, explain the legal
+terms of reusing it, describe its functionality and how to install, run
+and contribute to it, to whole websites full of documentation with
+function definitions, usage examples, tutorials and guides. You many not
+need as much documentation as a large commercial software product, but
+making your code reusable relies on other people being able to
+understand what your code does and how to use it.</p>
+</div>
+<div class="section level3">
+<h3 id="software-repositories-and-registries">Software repositories and registries<a class="anchor" aria-label="anchor" href="#software-repositories-and-registries"></a>
+</h3>
 <p>Having somewhere to share your code is fundamental to making it
-Findable. Your institution might have a code repository, your research
-field may have a practice of sharing code via a specific website or
-journal, or your version control system might include an online
-component that makes sharing different versions of your code easy.
-Again, remember to check the rules of your institution and grant on
-publishing code, and any licenses for code you depend on or reuse.</p>
-<p>We will discuss later how to share your code on GitHub and make it
-easy for others to find and use.</p>
-</section><section><h2 class="section-heading" id="summary-of-tools-practices">Summary of tools &amp; practices<a class="anchor" aria-label="anchor" href="#summary-of-tools-practices"></a>
-</h2>
-<hr class="half-width">
-<p>The table below summarises some tools and practices that can help
-with each of the FAIR software principles.</p>
+findable and accessible. Your institution might have a code repository,
+your research field may have a practice of sharing code via a specific
+website, archive or journal, or your version control system might
+include an online component that makes sharing different versions of
+your code easy. You should check the rules or guidelines of your
+institution, grant or domain on publishing code, as well as any licenses
+of the code your software depends on or reuses.</p>
+<p>Some examples of commonly used software repositories and registries
+include:</p>
+<ul>
+<li>general-purpose software repositories, such as <a href="https://github.com" class="external-link">GitHub</a> and <a href="https://about.gitlab.com/" class="external-link">GitLab</a>
+</li>
+<li>programming language-specific software repositories, such as <a href="https://pypi.org/" class="external-link">PyPi</a> (for Python) and <a href="https://cran.r-project.org/web/packages/" class="external-link">CRAN</a> (for R)</li>
+<li>software registries, such as <a href="https://biotools.us/" class="external-link">BioTools</a> (for biosciences) and <a href="https://github.com/NLeSC/awesome-research-software-registries" class="external-link">Awesome
+Research Software Registries</a> (providing a list of research software
+registries by country, organisation, domain and programming language)
+where research software can be registered to help promote its
+discovery</li>
+</ul>
+</div>
+<div class="section level3">
+<h3 id="persistent-identifiers">Persistent identifiers<a class="anchor" aria-label="anchor" href="#persistent-identifiers"></a>
+</h3>
+<p>Unique persistent identifiers, such as Digital Object Identifiers
+(DOIs) provided by <a href="https://zenodo.org/" class="external-link">Zenodo</a>, <a href="https://figshare.com/" class="external-link">FigShare</a> and similar digital archiving
+services, and commits/tags/releases used by GitHub and similar code
+sharing platforms, help with findability and accessibility of your
+software, and can help you get credit for your work by providing citable
+references.</p>
+</div>
+<div class="section level3">
+<h3 id="tools-and-practices-summary">Tools and practices summary<a class="anchor" aria-label="anchor" href="#tools-and-practices-summary"></a>
+</h3>
+<p>The table below provides a summary of how different tools and
+practices help with the FAIR software principles.</p>
 <table class="table">
 <colgroup>
-<col width="67%">
-<col width="6%">
-<col width="8%">
-<col width="10%">
-<col width="6%">
+<col width="71%">
+<col width="5%">
+<col width="7%">
+<col width="9%">
+<col width="5%">
 </colgroup>
 <thead><tr class="header">
 <th>Tools and practices</th>
@@ -1389,30 +1375,42 @@ <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square">
 </tr></thead>
 <tbody>
 <tr class="odd">
-<td>Virtual development environments, programming language and
-dependencies - run, test, debug, share</td>
+<td>Virtual development environments</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
 </tr>
 <tr class="even">
-<td>Integrated development environments/IDEs (e.g. VS Code, PyCharm) -
-run, test, debug</td>
+<td>Integrated development environments/IDEs</td>
 <td></td>
 <td></td>
 <td></td>
 <td>x</td>
 </tr>
 <tr class="odd">
-<td>Command line terminal (e.g. Bash, GitBash) - reproducible
-workflows/pipelines</td>
+<td>Command line terminals - automated and reproducible pipelines</td>
 <td></td>
 <td></td>
 <td>x</td>
 <td>x</td>
 </tr>
 <tr class="even">
+<td>Standard formats - e.g. for data exchange (CSV, YAML)</td>
+<td></td>
+<td>x</td>
+<td>x</td>
+<td>x</td>
+</tr>
+<tr class="odd">
+<td>Communication protocols - Command Line Interface (CLI) or
+Application Programming Interface (API)</td>
+<td></td>
+<td>x</td>
+<td>x</td>
+<td>x</td>
+</tr>
+<tr class="even">
 <td>Version control tools</td>
 <td>x</td>
 <td></td>
@@ -1420,76 +1418,71 @@ <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square">
 <td></td>
 </tr>
 <tr class="odd">
-<td>Testing - code correctness and reproducibility</td>
+<td>Code testing and correctness</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
 </tr>
 <tr class="even">
-<td>Coding conventions and documentation</td>
+<td>Code style conventions</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
 </tr>
 <tr class="odd">
-<td>Explaining functionality/installation/running - README, inline
-comments and documentation</td>
+<td>Software-level documentation (comments and docstrings, explaining
+functionality)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
 </tr>
 <tr class="even">
-<td>Standard formats - e.g. for data exchange (CSV, YAML)</td>
+<td>Project-level documentation (READMEs, explaining
+functionality/installation/running)</td>
 <td></td>
 <td>x</td>
 <td>x</td>
 <td>x</td>
 </tr>
 <tr class="odd">
-<td>Communication protocols - Command Line Interface (CLI) or
-Application Programming Interface (API)</td>
-<td></td>
-<td>x</td>
-<td>x</td>
-<td>x</td>
-</tr>
-<tr class="even">
-<td>License</td>
+<td>License - code sharing and reuse</td>
 <td></td>
 <td>x</td>
 <td></td>
 <td>x</td>
 </tr>
-<tr class="odd">
-<td>Citation</td>
+<tr class="even">
+<td>Citation - code reuse and credit</td>
 <td>x</td>
 <td></td>
 <td></td>
 <td>x</td>
 </tr>
-<tr class="even">
-<td>Software repositories (e.g. GitHub, PyPi) or registries
-(e.g. BioTools)</td>
+<tr class="odd">
+<td>Software repositories and registries - code sharing</td>
 <td>x</td>
 <td>x</td>
 <td></td>
 <td></td>
 </tr>
-<tr class="odd">
-<td>Unique persistent identifier (e.g. DOIs, commits/tags/releases) -
-Zenodo, FigShare GitHub</td>
+<tr class="even">
+<td>Unique persistent identifiers - finding and citing software</td>
 <td>x</td>
 <td>x</td>
 <td></td>
 <td></td>
 </tr>
 </tbody>
-</table></section><section><h2 class="section-heading" id="checking-your-setup">Checking your setup<a class="anchor" aria-label="anchor" href="#checking-your-setup"></a>
+</table>
+</div>
+<section><h2 class="section-heading" id="checking-your-setup">Checking your setup<a class="anchor" aria-label="anchor" href="#checking-your-setup"></a>
 </h2>
 <hr class="half-width">
+<p>Let’s check your setup now to make sure you are ready for the rest of
+this course.</p>
 <div id="checking-your-setup-1" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
@@ -1645,7 +1638,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-04-version-control"><p>Content from <a href="04-version-control.html">Version control</a></p>
 <hr>
-<p>Last updated on 2024-09-24 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/04-version-control.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 90 minutes</p>
@@ -2106,14 +2099,13 @@ <h3 id="rename-our-data-and-output-files">Rename our data and output files<a cla
 <li>choose informative file names for our output data file and
 plot.</li>
 </ol>
-<p>First let’s update file names in our script.</p>
+<p>First let’s update file names in our script using VS Code.</p>
 <div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb26-2"><a href="#cb26-2" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb26-3"><a href="#cb26-3" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
-<span id="cb26-4"><a href="#cb26-4" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>   </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb26-2"><a href="#cb26-2" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
+<span id="cb26-3"><a href="#cb26-3" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>   </span></code></pre>
 </div>
 <p>Now, let’s actually rename our files on the file system using git and
 commit our changes.</p>
@@ -2543,7 +2535,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-05-code-environment"><p>Content from <a href="05-code-environment.html">Reproducible development environment</a></p>
 <hr>
-<p>Last updated on 2024-09-24 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/05-code-environment.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 30 minutes</p>
@@ -2977,6 +2969,18 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 file accordingly by re-issuing <code>pip freeze</code> command and
 propagate the updated <code>requirements.txt</code> file to your
 collaborators via your code sharing platform.</p>
+</section><section><h2 class="section-heading" id="running-the-code">Running the code<a class="anchor" aria-label="anchor" href="#running-the-code"></a>
+</h2>
+<hr class="half-width">
+<p>We are now setup to run our code from the newly created virtual
+environment:</p>
+<div class="codewrapper sourceCode" id="cb25">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py</span></code></pre>
+</div>
+<p>You should get a pop up window with a graph. Let’s inspect the code
+in a more detail, see if we can understand and improve it.</p>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a>
 </h2>
 <hr class="half-width">
@@ -3016,7 +3020,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-06-code-readability"><p>Content from <a href="06-code-readability.html">Code readability</a></p>
 <hr>
-<p>Last updated on 2024-09-26 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/06-code-readability.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 90 minutes</p>
@@ -3123,69 +3127,67 @@ <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square">
 <div class="codewrapper sourceCode" id="cb2">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a></span>
-<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb2-3"><a href="#cb2-3" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb2-4"><a href="#cb2-4" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
-<span id="cb2-5"><a href="#cb2-5" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span>  </span>
-<span id="cb2-6"><a href="#cb2-6" tabindex="-1"></a></span>
-<span id="cb2-7"><a href="#cb2-7" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
-<span id="cb2-8"><a href="#cb2-8" tabindex="-1"></a></span>
-<span id="cb2-9"><a href="#cb2-9" tabindex="-1"></a>data<span class="op">=</span>[]</span>
-<span id="cb2-10"><a href="#cb2-10" tabindex="-1"></a><span class="im">import</span> json</span>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="im">import</span> json</span>
+<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="im">import</span> csv</span>
+<span id="cb2-3"><a href="#cb2-3" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
+<span id="cb2-4"><a href="#cb2-4" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb2-5"><a href="#cb2-5" tabindex="-1"></a></span>
+<span id="cb2-6"><a href="#cb2-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb2-7"><a href="#cb2-7" tabindex="-1"></a>data_f <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb2-8"><a href="#cb2-8" tabindex="-1"></a>data_t <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>,<span class="st">'w'</span>)</span>
+<span id="cb2-9"><a href="#cb2-9" tabindex="-1"></a>g_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span> </span>
+<span id="cb2-10"><a href="#cb2-10" tabindex="-1"></a></span>
 <span id="cb2-11"><a href="#cb2-11" tabindex="-1"></a></span>
-<span id="cb2-12"><a href="#cb2-12" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> <span class="bu">range</span>(<span class="dv">374</span>):</span>
-<span id="cb2-13"><a href="#cb2-13" tabindex="-1"></a>    line<span class="op">=</span>data_f.readline()</span>
-<span id="cb2-14"><a href="#cb2-14" tabindex="-1"></a>    <span class="bu">print</span>(line)</span>
-<span id="cb2-15"><a href="#cb2-15" tabindex="-1"></a>    data.append(json.loads(line[<span class="dv">1</span>:<span class="op">-</span><span class="dv">1</span>]))</span>
-<span id="cb2-16"><a href="#cb2-16" tabindex="-1"></a><span class="co">#data.pop(0)</span></span>
-<span id="cb2-17"><a href="#cb2-17" tabindex="-1"></a><span class="co">## Comment out this bit if you don't want the spreadsheet</span></span>
-<span id="cb2-18"><a href="#cb2-18" tabindex="-1"></a><span class="im">import</span> csv</span>
-<span id="cb2-19"><a href="#cb2-19" tabindex="-1"></a></span>
-<span id="cb2-20"><a href="#cb2-20" tabindex="-1"></a>w<span class="op">=</span>csv.writer(data_t)</span>
-<span id="cb2-21"><a href="#cb2-21" tabindex="-1"></a></span>
-<span id="cb2-22"><a href="#cb2-22" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
-<span id="cb2-23"><a href="#cb2-23" tabindex="-1"></a></span>
-<span id="cb2-24"><a href="#cb2-24" tabindex="-1"></a>time <span class="op">=</span> []</span>
-<span id="cb2-25"><a href="#cb2-25" tabindex="-1"></a>date <span class="op">=</span>[]</span>
-<span id="cb2-26"><a href="#cb2-26" tabindex="-1"></a></span>
-<span id="cb2-27"><a href="#cb2-27" tabindex="-1"></a>j<span class="op">=</span><span class="dv">0</span></span>
-<span id="cb2-28"><a href="#cb2-28" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> data:</span>
-<span id="cb2-29"><a href="#cb2-29" tabindex="-1"></a>    <span class="bu">print</span>(data[j])</span>
-<span id="cb2-30"><a href="#cb2-30" tabindex="-1"></a>    <span class="co"># and this bit</span></span>
-<span id="cb2-31"><a href="#cb2-31" tabindex="-1"></a>    w.writerow(data[j].values())</span>
-<span id="cb2-32"><a href="#cb2-32" tabindex="-1"></a>    <span class="cf">if</span> <span class="st">'duration'</span> <span class="kw">in</span> data[j].keys():</span>
-<span id="cb2-33"><a href="#cb2-33" tabindex="-1"></a>        tt<span class="op">=</span>data[j][<span class="st">'duration'</span>]</span>
-<span id="cb2-34"><a href="#cb2-34" tabindex="-1"></a>        <span class="cf">if</span> tt <span class="op">==</span> <span class="st">''</span>:</span>
-<span id="cb2-35"><a href="#cb2-35" tabindex="-1"></a>            <span class="cf">pass</span></span>
-<span id="cb2-36"><a href="#cb2-36" tabindex="-1"></a>        <span class="cf">else</span>:</span>
-<span id="cb2-37"><a href="#cb2-37" tabindex="-1"></a>            t<span class="op">=</span>dt.datetime.strptime(tt,<span class="st">'%H:%M'</span>)</span>
-<span id="cb2-38"><a href="#cb2-38" tabindex="-1"></a>            ttt <span class="op">=</span> dt.timedelta(hours<span class="op">=</span>t.hour, minutes<span class="op">=</span>t.minute, seconds<span class="op">=</span>t.second).total_seconds()<span class="op">/</span>(<span class="dv">60</span><span class="op">*</span><span class="dv">60</span>)</span>
-<span id="cb2-39"><a href="#cb2-39" tabindex="-1"></a>            <span class="bu">print</span>(t,ttt)</span>
-<span id="cb2-40"><a href="#cb2-40" tabindex="-1"></a>            time.append(ttt)</span>
-<span id="cb2-41"><a href="#cb2-41" tabindex="-1"></a>            <span class="cf">if</span> <span class="st">'date'</span> <span class="kw">in</span> data[j].keys():</span>
-<span id="cb2-42"><a href="#cb2-42" tabindex="-1"></a>                date.append(dt.datetime.strptime(data[j][<span class="st">'date'</span>][<span class="dv">0</span>:<span class="dv">10</span>], <span class="st">'%Y-%m-</span><span class="sc">%d</span><span class="st">'</span>))</span>
-<span id="cb2-43"><a href="#cb2-43" tabindex="-1"></a>                <span class="co">#date.append(data[j]['date'][0:10])</span></span>
-<span id="cb2-44"><a href="#cb2-44" tabindex="-1"></a></span>
-<span id="cb2-45"><a href="#cb2-45" tabindex="-1"></a>            <span class="cf">else</span>:</span>
-<span id="cb2-46"><a href="#cb2-46" tabindex="-1"></a>                time.pop(<span class="dv">0</span>)</span>
-<span id="cb2-47"><a href="#cb2-47" tabindex="-1"></a>    j<span class="op">+=</span><span class="dv">1</span></span>
-<span id="cb2-48"><a href="#cb2-48" tabindex="-1"></a></span>
-<span id="cb2-49"><a href="#cb2-49" tabindex="-1"></a>t<span class="op">=</span>[<span class="dv">0</span>]</span>
-<span id="cb2-50"><a href="#cb2-50" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> time:</span>
-<span id="cb2-51"><a href="#cb2-51" tabindex="-1"></a>    t.append(t[<span class="op">-</span><span class="dv">1</span>]<span class="op">+</span>i)</span>
-<span id="cb2-52"><a href="#cb2-52" tabindex="-1"></a></span>
-<span id="cb2-53"><a href="#cb2-53" tabindex="-1"></a>date,time <span class="op">=</span> <span class="bu">zip</span>(<span class="op">*</span><span class="bu">sorted</span>(<span class="bu">zip</span>(date, time)))</span>
-<span id="cb2-54"><a href="#cb2-54" tabindex="-1"></a></span>
-<span id="cb2-55"><a href="#cb2-55" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb2-56"><a href="#cb2-56" tabindex="-1"></a></span>
-<span id="cb2-57"><a href="#cb2-57" tabindex="-1"></a>plt.plot(date,t[<span class="dv">1</span>:], <span class="st">'ko-'</span>)</span>
-<span id="cb2-58"><a href="#cb2-58" tabindex="-1"></a>plt.xlabel(<span class="st">'Year'</span>)</span>
-<span id="cb2-59"><a href="#cb2-59" tabindex="-1"></a>plt.ylabel(<span class="st">'Total time spent in space to date (hours)'</span>)</span>
-<span id="cb2-60"><a href="#cb2-60" tabindex="-1"></a>plt.tight_layout()</span>
-<span id="cb2-61"><a href="#cb2-61" tabindex="-1"></a>plt.savefig(g_file)</span>
-<span id="cb2-62"><a href="#cb2-62" tabindex="-1"></a>plt.show()</span>
-<span id="cb2-63"><a href="#cb2-63" tabindex="-1"></a></span></code></pre>
+<span id="cb2-12"><a href="#cb2-12" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
+<span id="cb2-13"><a href="#cb2-13" tabindex="-1"></a></span>
+<span id="cb2-14"><a href="#cb2-14" tabindex="-1"></a>data<span class="op">=</span>[]</span>
+<span id="cb2-15"><a href="#cb2-15" tabindex="-1"></a></span>
+<span id="cb2-16"><a href="#cb2-16" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> <span class="bu">range</span>(<span class="dv">374</span>):</span>
+<span id="cb2-17"><a href="#cb2-17" tabindex="-1"></a>    line<span class="op">=</span>data_f.readline()</span>
+<span id="cb2-18"><a href="#cb2-18" tabindex="-1"></a>    <span class="bu">print</span>(line)</span>
+<span id="cb2-19"><a href="#cb2-19" tabindex="-1"></a>    data.append(json.loads(line[<span class="dv">1</span>:<span class="op">-</span><span class="dv">1</span>]))</span>
+<span id="cb2-20"><a href="#cb2-20" tabindex="-1"></a><span class="co">#data.pop(0)</span></span>
+<span id="cb2-21"><a href="#cb2-21" tabindex="-1"></a><span class="co">## Comment out this bit if you don't want the spreadsheet</span></span>
+<span id="cb2-22"><a href="#cb2-22" tabindex="-1"></a></span>
+<span id="cb2-23"><a href="#cb2-23" tabindex="-1"></a>w<span class="op">=</span>csv.writer(data_t)</span>
+<span id="cb2-24"><a href="#cb2-24" tabindex="-1"></a></span>
+<span id="cb2-25"><a href="#cb2-25" tabindex="-1"></a>time <span class="op">=</span> []</span>
+<span id="cb2-26"><a href="#cb2-26" tabindex="-1"></a>date <span class="op">=</span>[]</span>
+<span id="cb2-27"><a href="#cb2-27" tabindex="-1"></a></span>
+<span id="cb2-28"><a href="#cb2-28" tabindex="-1"></a>j<span class="op">=</span><span class="dv">0</span></span>
+<span id="cb2-29"><a href="#cb2-29" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> data:</span>
+<span id="cb2-30"><a href="#cb2-30" tabindex="-1"></a>    <span class="bu">print</span>(data[j])</span>
+<span id="cb2-31"><a href="#cb2-31" tabindex="-1"></a>    <span class="co"># and this bit</span></span>
+<span id="cb2-32"><a href="#cb2-32" tabindex="-1"></a>    w.writerow(data[j].values())</span>
+<span id="cb2-33"><a href="#cb2-33" tabindex="-1"></a>    <span class="cf">if</span> <span class="st">'duration'</span> <span class="kw">in</span> data[j].keys():</span>
+<span id="cb2-34"><a href="#cb2-34" tabindex="-1"></a>        tt<span class="op">=</span>data[j][<span class="st">'duration'</span>]</span>
+<span id="cb2-35"><a href="#cb2-35" tabindex="-1"></a>        <span class="cf">if</span> tt <span class="op">==</span> <span class="st">''</span>:</span>
+<span id="cb2-36"><a href="#cb2-36" tabindex="-1"></a>            <span class="cf">pass</span></span>
+<span id="cb2-37"><a href="#cb2-37" tabindex="-1"></a>        <span class="cf">else</span>:</span>
+<span id="cb2-38"><a href="#cb2-38" tabindex="-1"></a>            t<span class="op">=</span>dt.datetime.strptime(tt,<span class="st">'%H:%M'</span>)</span>
+<span id="cb2-39"><a href="#cb2-39" tabindex="-1"></a>            ttt <span class="op">=</span> dt.timedelta(hours<span class="op">=</span>t.hour, minutes<span class="op">=</span>t.minute, seconds<span class="op">=</span>t.second).total_seconds()<span class="op">/</span>(<span class="dv">60</span><span class="op">*</span><span class="dv">60</span>)</span>
+<span id="cb2-40"><a href="#cb2-40" tabindex="-1"></a>            <span class="bu">print</span>(t,ttt)</span>
+<span id="cb2-41"><a href="#cb2-41" tabindex="-1"></a>            time.append(ttt)</span>
+<span id="cb2-42"><a href="#cb2-42" tabindex="-1"></a>            <span class="cf">if</span> <span class="st">'date'</span> <span class="kw">in</span> data[j].keys():</span>
+<span id="cb2-43"><a href="#cb2-43" tabindex="-1"></a>                date.append(dt.datetime.strptime(data[j][<span class="st">'date'</span>][<span class="dv">0</span>:<span class="dv">10</span>], <span class="st">'%Y-%m-</span><span class="sc">%d</span><span class="st">'</span>))</span>
+<span id="cb2-44"><a href="#cb2-44" tabindex="-1"></a>                <span class="co">#date.append(data[j]['date'][0:10])</span></span>
+<span id="cb2-45"><a href="#cb2-45" tabindex="-1"></a></span>
+<span id="cb2-46"><a href="#cb2-46" tabindex="-1"></a>            <span class="cf">else</span>:</span>
+<span id="cb2-47"><a href="#cb2-47" tabindex="-1"></a>                time.pop(<span class="dv">0</span>)</span>
+<span id="cb2-48"><a href="#cb2-48" tabindex="-1"></a>    j<span class="op">+=</span><span class="dv">1</span></span>
+<span id="cb2-49"><a href="#cb2-49" tabindex="-1"></a></span>
+<span id="cb2-50"><a href="#cb2-50" tabindex="-1"></a>t<span class="op">=</span>[<span class="dv">0</span>]</span>
+<span id="cb2-51"><a href="#cb2-51" tabindex="-1"></a><span class="cf">for</span> i <span class="kw">in</span> time:</span>
+<span id="cb2-52"><a href="#cb2-52" tabindex="-1"></a>    t.append(t[<span class="op">-</span><span class="dv">1</span>]<span class="op">+</span>i)</span>
+<span id="cb2-53"><a href="#cb2-53" tabindex="-1"></a></span>
+<span id="cb2-54"><a href="#cb2-54" tabindex="-1"></a>date,time <span class="op">=</span> <span class="bu">zip</span>(<span class="op">*</span><span class="bu">sorted</span>(<span class="bu">zip</span>(date, time)))</span>
+<span id="cb2-55"><a href="#cb2-55" tabindex="-1"></a></span>
+<span id="cb2-56"><a href="#cb2-56" tabindex="-1"></a>plt.plot(date,t[<span class="dv">1</span>:], <span class="st">'ko-'</span>)</span>
+<span id="cb2-57"><a href="#cb2-57" tabindex="-1"></a>plt.xlabel(<span class="st">'Year'</span>)</span>
+<span id="cb2-58"><a href="#cb2-58" tabindex="-1"></a>plt.ylabel(<span class="st">'Total time spent in space to date (hours)'</span>)</span>
+<span id="cb2-59"><a href="#cb2-59" tabindex="-1"></a>plt.tight_layout()</span>
+<span id="cb2-60"><a href="#cb2-60" tabindex="-1"></a>plt.savefig(g_file)</span>
+<span id="cb2-61"><a href="#cb2-61" tabindex="-1"></a>plt.show()</span></code></pre>
 </div>
 <p>Let’s make sure we commit our changes.</p>
 <div class="codewrapper sourceCode" id="cb3">
@@ -3273,7 +3275,7 @@ <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
 <div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
 <div class="accordion-body">
-<p>Yes, <span class="math display">\[9.81 m/s^2 \]</span> is the <a href="https://en.wikipedia.org/wiki/Gravity_of_Earth" class="external-link">gravitational
+<p><span class="math display">\[ 9.81 m/s^2 \]</span> is the <a href="https://en.wikipedia.org/wiki/Gravity_of_Earth" class="external-link">gravitational
 force exerted by the Earth</a>. It is often referred to as “little g” to
 distinguish it from “big G” which is the <a href="https://en.wikipedia.org/wiki/Gravitational_constant" class="external-link">Gravitational
 Constant</a>. A more descriptive name for this variable therefore might
@@ -3287,12 +3289,12 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 </div>
 </div>
-<div id="challenge2" class="callout challenge">
+<div id="rename-our-variables-to-be-more-descriptive" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
 </div>
-<div class="callout-inner">
-<h3 class="callout-title">Challenge</h3>
+<div id="rename-our-variables-to-be-more-descriptive" class="callout-inner">
+<h3 class="callout-title">Rename our variables to be more descriptive</h3>
 <div class="callout-content">
 <p>Let’s apply this to <code>eva_data_analysis.py</code>.</p>
 <ol style="list-style-type: lower-alpha">
@@ -3323,16 +3325,16 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <div class="codewrapper sourceCode" id="cb6">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a></span>
-<span id="cb6-2"><a href="#cb6-2" tabindex="-1"></a><span class="im">import</span> json</span>
-<span id="cb6-3"><a href="#cb6-3" tabindex="-1"></a><span class="im">import</span> csv</span>
-<span id="cb6-4"><a href="#cb6-4" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
-<span id="cb6-5"><a href="#cb6-5" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb6-6"><a href="#cb6-6" tabindex="-1"></a></span>
-<span id="cb6-7"><a href="#cb6-7" tabindex="-1"></a><span class="co"># Data source: https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb6-8"><a href="#cb6-8" tabindex="-1"></a>input_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
-<span id="cb6-9"><a href="#cb6-9" tabindex="-1"></a>output_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>, <span class="st">'w'</span>)</span>
-<span id="cb6-10"><a href="#cb6-10" tabindex="-1"></a>graph_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span></span>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb6-1"><a href="#cb6-1" tabindex="-1"></a><span class="im">import</span> json</span>
+<span id="cb6-2"><a href="#cb6-2" tabindex="-1"></a><span class="im">import</span> csv</span>
+<span id="cb6-3"><a href="#cb6-3" tabindex="-1"></a><span class="im">import</span> datetime <span class="im">as</span> dt</span>
+<span id="cb6-4"><a href="#cb6-4" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb6-5"><a href="#cb6-5" tabindex="-1"></a></span>
+<span id="cb6-6"><a href="#cb6-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb6-7"><a href="#cb6-7" tabindex="-1"></a>input_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.json'</span>, <span class="st">'r'</span>)</span>
+<span id="cb6-8"><a href="#cb6-8" tabindex="-1"></a>output_file <span class="op">=</span> <span class="bu">open</span>(<span class="st">'./eva-data.csv'</span>, <span class="st">'w'</span>)</span>
+<span id="cb6-9"><a href="#cb6-9" tabindex="-1"></a>graph_file <span class="op">=</span> <span class="st">'./cumulative_eva_graph.png'</span></span>
+<span id="cb6-10"><a href="#cb6-10" tabindex="-1"></a></span>
 <span id="cb6-11"><a href="#cb6-11" tabindex="-1"></a></span>
 <span id="cb6-12"><a href="#cb6-12" tabindex="-1"></a>fieldnames <span class="op">=</span> (<span class="st">"EVA #"</span>, <span class="st">"Country"</span>, <span class="st">"Crew    "</span>, <span class="st">"Vehicle"</span>, <span class="st">"Date"</span>, <span class="st">"Duration"</span>, <span class="st">"Purpose"</span>)</span>
 <span id="cb6-13"><a href="#cb6-13" tabindex="-1"></a></span>
@@ -3650,19 +3652,20 @@ <h3 class="callout-title">Callout</h3>
 functionality:</p>
 <ol style="list-style-type: decimal">
 <li>reading the data from a JSON file</li>
+<li>converting and saving the data in the CSV format</li>
 <li>processing/cleaning the data and preparing it for analysis</li>
 <li>data analysis and visualising the results</li>
-<li>converting and saving the data in the CSV format</li>
 </ol>
 <p>Let’s refactor our code so that reading the data in JSON format into
 a dataframe (step 1.) and converting it and saving to the CSV format
-(step 4.) are extracted into separate functions. Let’s name those
+(step 2.) are extracted into separate functions. Let’s name those
 functions <code>read_json_to_dataframe</code> and
 <code>write_dataframe_to_csv</code> respectively. The main part of the
 script should then be simplified to invoke these new functions, while
 the functions themselves contain the complexity of each of these two
-steps.</p>
-<p>Our code may look something like the following.</p>
+steps. We will continue to work on steps 3. and 4. above later on.</p>
+<p>After the initial refactoring, our code may look something like the
+following.</p>
 <div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -3714,19 +3717,23 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <span id="cb17-46"><a href="#cb17-46" tabindex="-1"></a></span>
 <span id="cb17-47"><a href="#cb17-47" tabindex="-1"></a><span class="bu">print</span>(<span class="st">"--END--"</span>)</span></code></pre>
 </div>
-<p>We have chosen to create function for reading in and writing out data
-files since this is a very common task within research software. While
-these functions do not contain that many lines of code due to using the
-<code>pandas</code> in-built methods that do all the complex data
-reading, converting and writing operations, it can be useful to package
-these steps together into reusable functions if you need to read in or
-write out a lot of similarly structured files and process them in the
-same way.</p>
+<p>We have chosen to create functions for reading in and writing out
+data files since this is a very common task within research software.
+While these functions do not contain that many lines of code due to
+using the <code>pandas</code> in-built methods that do all the complex
+data reading, converting and writing operations, it can be useful to
+package these steps together into reusable functions if you need to read
+in or write out a lot of similarly structured files and process them in
+the same way.</p>
 </section><section><h2 class="section-heading" id="use-docstrings-to-document-functions">Use docstrings to document functions<a class="anchor" aria-label="anchor" href="#use-docstrings-to-document-functions"></a>
 </h2>
 <hr class="half-width">
-<p>Docstrings are a specific type of documentation that are provided
-within functions and <a href="https://docs.python.org/3/tutorial/classes.html" class="external-link">Python
+<p>Now that we have written some functions, it is time to document them
+so that we can quickly recall (and others looking at our code in the
+future can understand) what the functions doe without having to read the
+code.</p>
+<p><em>Docstrings</em> are a specific type of documentation that are
+provided within functions and <a href="https://docs.python.org/3/tutorial/classes.html" class="external-link">Python
 classes</a>. A function docstring should explain what that particular
 code is doing, what parameters the function needs (inputs) and what form
 they should take, what the function outputs (you may see words like
@@ -4000,7 +4007,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-07-code-structure"><p>Content from <a href="07-code-structure.html">Code structure</a></p>
 <hr>
-<p>Last updated on 2024-09-26 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/07-code-structure.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 90 minutes</p>
@@ -4015,7 +4022,7 @@ <h2 class="card-header">Overview</h2>
 <div class="inner">
 <h3 class="card-title">Questions</h3>
 <ul>
-<li>How can we bests structure code?</li>
+<li>How can we best structure code?</li>
 <li>What is a common code structure (pattern) for creating software that
 can read input from command line?</li>
 <li>What are conventional places to store data, code, results, tests,
@@ -4288,7 +4295,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 set by the Python interpreter before the execution of any code in the
 source file. What value is given by the interpreter to
 <code>__name__</code> is determined by the manner in which the script is
-loaded.</p>
+invoked.</p>
 <p>If we run the source file directly using the Python interpreter,
 e.g.:</p>
 <div class="codewrapper sourceCode" id="cb5">
@@ -4313,7 +4320,8 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="im">import</span> eva_data_analysis</span></code></pre>
 </div>
 <p>then the Python interpreter will assign the name “eva_data_analysis”
-from the import statement to the <code>__name__</code> variable:</p>
+from the import statement to the <code>__name__</code> variable (note
+that import statement matches our script’s name):</p>
 <div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -4331,7 +4339,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 to do this:</p>
 <ul>
 <li>for testing of your code, you can have your testing framework import
-the main script, and run special test functions which then call the
+your script, and run special test functions which then call the
 <code>main</code> function directly;</li>
 <li>where you want to not only be able to run your script from the
 command-line, but also provide a programmer-friendly application
@@ -4473,7 +4481,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python eva_data_analysis.py eva_data.json eva_data.csv</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python eva_data_analysis.py eva-data.json eva-data.csv</span></code></pre>
 </div>
 <p>Remember to commit our changes.</p>
 <div class="codewrapper sourceCode" id="cb11">
@@ -4536,7 +4544,9 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <li>Code and data should be version controlled; you can also version
 control manuscripts, results, etc.</li>
 <li>If data files are too large (or contain sensitive information) to
-track by version control, untrack them using .gitignore</li>
+track by version control, untrack them using
+<code>.gitignore</code>
+</li>
 <li>Use tags/releases to mark specific versions of results (a version
 submitted to a journal, dissertation version, poster version, etc.) so
 as to avoid using version numbers in file names and proliferation of
@@ -4578,7 +4588,8 @@ <h3 class="callout-title">Challenge</h3>
 <div class="callout-content">
 <p>Refactor your software project so that input data is stored in
 <code>data/</code> directory and results (the graph and CSV data files)
-saved in <code>results/</code> directory.</p>
+saved in <code>results/</code> directory. Remember to create the
+<code>results/</code> directory or your code will fail.</p>
 </div>
 </div>
 </div>
@@ -4719,20 +4730,13 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 </div>
 </div>
-<p>After the above exercise, you will be invoking your script from
-command line as:</p>
-<div class="codewrapper sourceCode" id="cb14">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python data/eva_data_analysis.py eva_data.json results/eva_data.csv</span></code></pre>
-</div>
 <p>Remember to commit your latest changes:</p>
-<div class="codewrapper sourceCode" id="cb15">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git status</span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add eva_data_analysis.py data results</span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Update project's directory structure"</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git status</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add eva_data_analysis.py data results</span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Update project's directory structure"</span></span></code></pre>
 </div>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a>
 </h2>
@@ -4770,7 +4774,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-08-code-correctness"><p>Content from <a href="08-code-correctness.html">Code correctness</a></p>
 <hr>
-<p>Last updated on 2024-09-26 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/08-code-correctness.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 90 minutes</p>
@@ -4952,7 +4956,7 @@ <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </h2>
 <hr class="half-width">
 <p>How should we test our code? One approach is to copy/paste the code
-or a function into a Python terminal (different from command line
+or a function into a Python terminal (different from a command line
 terminal), which allows you to interact with the Python interpreter more
 directly.<br>
 From the Python terminal we can then run one function or a piece of code
@@ -5097,35 +5101,29 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </ul>
 <p>Let’s explore this process by writing some formal tests for our
 <code>text_to_duration</code> function.</p>
-<p>Let’s create a new Python file <code>test_code.py</code> in the root
-of our project directory to store our tests.</p>
-<div class="codewrapper sourceCode" id="cb7">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> cd spacewalks</span>
-<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch test_code.py</span></code></pre>
-</div>
+<p>In VS Code, create a new Python file <code>test_code.py</code> in the
+root of our project directory to store our tests.</p>
 <p>Like before in the Python terminal, we need to import
 <code>text_to_duration</code> into our test script. Then, we add our
 first test function:</p>
-<div class="codewrapper sourceCode" id="cb8">
+<div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a></span>
-<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a></span>
-<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a>    input_value <span class="op">=</span> <span class="st">"10:00"</span></span>
-<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a>    test_result <span class="op">=</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>    <span class="bu">print</span>(<span class="ss">f"text_to_duration('10:00') == 10? </span><span class="sc">{</span>test_result<span class="sc">}</span><span class="ss">"</span>)</span>
-<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a></span>
-<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a>test_text_to_duration()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a></span>
+<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb7-3"><a href="#cb7-3" tabindex="-1"></a></span>
+<span id="cb7-4"><a href="#cb7-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb7-5"><a href="#cb7-5" tabindex="-1"></a>    input_value <span class="op">=</span> <span class="st">"10:00"</span></span>
+<span id="cb7-6"><a href="#cb7-6" tabindex="-1"></a>    test_result <span class="op">=</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb7-7"><a href="#cb7-7" tabindex="-1"></a>    <span class="bu">print</span>(<span class="ss">f"text_to_duration('10:00') == 10? </span><span class="sc">{</span>test_result<span class="sc">}</span><span class="ss">"</span>)</span>
+<span id="cb7-8"><a href="#cb7-8" tabindex="-1"></a></span>
+<span id="cb7-9"><a href="#cb7-9" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <p>We can run this code from the command line terminal as:</p>
-<div class="codewrapper sourceCode" id="cb9">
+<div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span><span class="ex">$</span> python3 test_code.py </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span><span class="ex">$</span> python3 test_code.py </span></code></pre>
 </div>
 <p>This test checks that when we apply <code>text_to_duration</code> to
 input value <code>10:00</code>, the output matches the expected value of
@@ -5146,16 +5144,16 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <code>False</code>, <code>assert</code> raises an
 <code>AssertError</code>.</p>
 <p>Let’s rewrite our test with an <code>assert</code> statement:</p>
-<div class="codewrapper sourceCode" id="cb10">
+<div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a></span>
-<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a></span>
-<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a></span>
-<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a></span>
+<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a></span>
+<span id="cb9-4"><a href="#cb9-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb9-5"><a href="#cb9-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb9-6"><a href="#cb9-6" tabindex="-1"></a></span>
+<span id="cb9-7"><a href="#cb9-7" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <p>Notice that when we run <code>test_text_to_duration_integer()</code>,
 nothing happens - there is no output. That is because our function is
@@ -5163,75 +5161,78 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <p>Let’s add another test to check what happens when duration is not an
 integer number and if our function can handle durations with a non-zero
 minute component, and rerun our test code.</p>
-<div class="codewrapper sourceCode" id="cb11">
+<div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb11-2"><a href="#cb11-2" tabindex="-1"></a></span>
-<span id="cb11-3"><a href="#cb11-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb11-4"><a href="#cb11-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:15"</span>) <span class="op">==</span> <span class="fl">10.25</span></span>
-<span id="cb11-5"><a href="#cb11-5" tabindex="-1"></a></span>
-<span id="cb11-6"><a href="#cb11-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb11-7"><a href="#cb11-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb11-8"><a href="#cb11-8" tabindex="-1"></a></span>
-<span id="cb11-9"><a href="#cb11-9" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb11-10"><a href="#cb11-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a></span>
+<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:15"</span>) <span class="op">==</span> <span class="fl">10.25</span></span>
+<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a></span>
+<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb10-8"><a href="#cb10-8" tabindex="-1"></a></span>
+<span id="cb10-9"><a href="#cb10-9" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb10-10"><a href="#cb10-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="error" tabindex="0"><code>(venv_spacewalks) $ python3 test_code.py
 Traceback (most recent call last):
-  File "/Users/user/work/SSI/lessons/astronaut-data-analysis/test_code.py", line 12, in &lt;module&gt;
+  File "/Users/user/Desktop/spacewalks/test_code.py", line 9, in &lt;module&gt;
     test_text_to_duration_float()
-  File "/Users/user/work/SSI/lessons/astronaut-data-analysis/test_code.py", line 5, in test_text_to_duration_float
+  File "/Users/user/Desktop/spacewalks/test_code.py", line 4, in test_text_to_duration_float
     assert text_to_duration("10:15") == 10.25
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-AssertionError
-</code></pre>
+AssertionError</code></pre>
 </div>
 <p>Notice that this time, our test
 <code>test_text_to_duration_float</code> fails. Our assert statement has
 raised an <code>AssertionError</code> - a clear signal that there is a
-problem in our code that we need to fix. Python helpfully tells us which
-line of our code is problematic:</p>
-<div class="codewrapper sourceCode" id="cb13">
+problem in our code that we need to fix. We know that duration
+<code>10:15</code> should be converted to number <code>10.25</code>.
+What is wrong with our code? If we look at our
+<code>text_to_duration</code> function, we may identify the following
+line of our code as problematic:</p>
+<div class="codewrapper sourceCode" id="cb12">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a>...</span>
-<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span> </span>
-<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="kw">def</span> text_to_duration(duration):</span>
+<span id="cb12-2"><a href="#cb12-2" tabindex="-1"></a>    ...</span>
+<span id="cb12-3"><a href="#cb12-3" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span> </span>
+<span id="cb12-4"><a href="#cb12-4" tabindex="-1"></a>    ...</span></code></pre>
 </div>
 <p>You may notice that our conversion code is wrong - the minutes
 component should have been divided by 60 and not 6. We were able to spot
 this tiny bug by testing our code.</p>
 <p>Let’s fix the problematic line and rerun out tests.</p>
-<div class="codewrapper sourceCode" id="cb14">
+<div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a>...</span>
-<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">60</span> </span>
-<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a>...</span>
+<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a>duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">60</span> </span>
+<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a>...</span></code></pre>
 </div>
 <p>This time our tests run without problem.</p>
 <p>Should we add more tests or the tests we have so far are enough? What
-happens if our duration value is <code>01:20</code> (one hour and 20
-minutes) and our result is not a rational floating point number like
-<code>10.25</code> but an irrational number such as
+happens if our duration value is <code>10:20</code> (ten hours and 20
+minutes) and our result is not a rational floating point number (like
+<code>10.25</code>) but an irrational number such as
 <code>10.333333333</code>? Let’s tests for this.</p>
-<div class="codewrapper sourceCode" id="cb15">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a></span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> <span class="fl">10.333333</span></span>
-<span id="cb15-5"><a href="#cb15-5" tabindex="-1"></a></span>
-<span id="cb15-6"><a href="#cb15-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb15-7"><a href="#cb15-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
-<span id="cb15-8"><a href="#cb15-8" tabindex="-1"></a></span>
-<span id="cb15-9"><a href="#cb15-9" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb15-10"><a href="#cb15-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a></span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb14-4"><a href="#cb14-4" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> <span class="fl">10.333333</span></span>
+<span id="cb14-5"><a href="#cb14-5" tabindex="-1"></a></span>
+<span id="cb14-6"><a href="#cb14-6" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb14-7"><a href="#cb14-7" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span>
+<span id="cb14-8"><a href="#cb14-8" tabindex="-1"></a></span>
+<span id="cb14-9"><a href="#cb14-9" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb14-10"><a href="#cb14-10" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -5251,13 +5252,13 @@ <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></
 (<code>==</code>) to compare the equality of floating point numbers.
 Instead, we check that our floating point numbers are equal within a
 very small tolerance (e.g. 1e-5). Hence, our code should look like:</p>
-<div class="codewrapper sourceCode" id="cb17">
+<div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a>...</span>
-<span id="cb17-2"><a href="#cb17-2" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb17-3"><a href="#cb17-3" tabindex="-1"></a>    <span class="cf">assert</span> <span class="bu">abs</span>(text_to_duration(<span class="st">"10:20"</span>) <span class="op">-</span> <span class="fl">10.33333333</span>) <span class="op">&lt;</span> <span class="fl">1e-5</span></span>
-<span id="cb17-4"><a href="#cb17-4" tabindex="-1"></a>...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a>...</span>
+<span id="cb16-2"><a href="#cb16-2" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb16-3"><a href="#cb16-3" tabindex="-1"></a>    <span class="cf">assert</span> <span class="bu">abs</span>(text_to_duration(<span class="st">"10:20"</span>) <span class="op">-</span> <span class="fl">10.33333333</span>) <span class="op">&lt;</span> <span class="fl">1e-5</span></span>
+<span id="cb16-4"><a href="#cb16-4" tabindex="-1"></a>...</span></code></pre>
 </div>
 <p>You may have noticed that we have to repeat a lot of code to add each
 individual test for each test case. You may also have noticed that our
@@ -5278,10 +5279,10 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 code coverage extension <code>pytest-cov</code>. To install these
 libraries into our virtual environment, from the command line terminal
 do:</p>
-<div class="codewrapper sourceCode" id="cb18">
+<div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip install pytest pytest-cov</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip install pytest pytest-cov</span></code></pre>
 </div>
 <p>Let’s make sure that our tests are ready to work with
 <code>pytest</code>.</p>
@@ -5294,12 +5295,12 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 requirements, so there is nothing to do here. However, our script does
 contain lines to run each of our test functions. These are no-longer
 required as pytest will run our tests so we can remove them:</p>
-<div class="codewrapper sourceCode" id="cb19">
+<div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="co"># Delete these 2 lines</span></span>
-<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a>test_text_to_duration_float()</span>
-<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="co"># Delete these 2 lines</span></span>
+<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a>test_text_to_duration_float()</span>
+<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a>test_text_to_duration_integer()</span></code></pre>
 </div>
 </li>
 <li><p>It is also conventional when working with a testing framework to
@@ -5312,55 +5313,57 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 test suite is currently located in the root folder of our project. Let’s
 move it to a dedicated test folder and rename our
 <code>test_code.py</code> file to <code>test_eva_analysis.py</code>.</p>
-<div class="codewrapper sourceCode" id="cb20">
+<p>You can do it from VS Code or by typing the following commands in the
+command line terminal:</p>
+<div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir tests</span>
-<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mv test_code.py tests/test_eva_analysis.py</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir tests</span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mv test_code.py tests/test_eva_analysis.py</span></code></pre>
 </div>
 <p>Before we re-run our tests using <code>pytest</code>, let’s update
 our second test to use <code>pytest</code>’s function
 <code>approx()</code> which is specifically intended for comparing
 floating point numbers within a tolerance.</p>
-<div class="codewrapper sourceCode" id="cb21">
+<div class="codewrapper sourceCode" id="cb20">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a></span>
-<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> pytest.approx(<span class="fl">10.33333333</span>)</span>
-<span id="cb21-6"><a href="#cb21-6" tabindex="-1"></a></span>
-<span id="cb21-7"><a href="#cb21-7" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb21-8"><a href="#cb21-8" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb20-3"><a href="#cb20-3" tabindex="-1"></a></span>
+<span id="cb20-4"><a href="#cb20-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb20-5"><a href="#cb20-5" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:20"</span>) <span class="op">==</span> pytest.approx(<span class="fl">10.33333333</span>)</span>
+<span id="cb20-6"><a href="#cb20-6" tabindex="-1"></a></span>
+<span id="cb20-7"><a href="#cb20-7" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb20-8"><a href="#cb20-8" tabindex="-1"></a>    <span class="cf">assert</span> text_to_duration(<span class="st">"10:00"</span>) <span class="op">==</span> <span class="dv">10</span></span></code></pre>
 </div>
 <p>Let’s also add some inline comments to clarify what each test is
 doing and expand our syntax to highlight the logic behind our
 approach:</p>
-<div class="codewrapper sourceCode" id="cb22">
+<div class="codewrapper sourceCode" id="cb21">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
-<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a></span>
-<span id="cb22-4"><a href="#cb22-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
-<span id="cb22-5"><a href="#cb22-5" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb22-6"><a href="#cb22-6" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
-<span id="cb22-7"><a href="#cb22-7" tabindex="-1"></a><span class="co">    for typical durations with a non-zero minute component</span></span>
-<span id="cb22-8"><a href="#cb22-8" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb22-9"><a href="#cb22-9" tabindex="-1"></a>    actual_result <span class="op">=</span> text_to_duration(<span class="st">"10:20"</span>) </span>
-<span id="cb22-10"><a href="#cb22-10" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="fl">10.33333333</span></span>
-<span id="cb22-11"><a href="#cb22-11" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> pytest.approx(expected_result)</span>
-<span id="cb22-12"><a href="#cb22-12" tabindex="-1"></a>    </span>
-<span id="cb22-13"><a href="#cb22-13" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
-<span id="cb22-14"><a href="#cb22-14" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb22-15"><a href="#cb22-15" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
-<span id="cb22-16"><a href="#cb22-16" tabindex="-1"></a><span class="co">    for typical whole hour durations </span></span>
-<span id="cb22-17"><a href="#cb22-17" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb22-18"><a href="#cb22-18" tabindex="-1"></a>    actual_result <span class="op">=</span>  text_to_duration(<span class="st">"10:00"</span>)</span>
-<span id="cb22-19"><a href="#cb22-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">10</span></span>
-<span id="cb22-20"><a href="#cb22-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb22-21"><a href="#cb22-21" tabindex="-1"></a>    </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> text_to_duration</span>
+<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a></span>
+<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_float():</span>
+<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb21-6"><a href="#cb21-6" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
+<span id="cb21-7"><a href="#cb21-7" tabindex="-1"></a><span class="co">    for typical durations with a non-zero minute component</span></span>
+<span id="cb21-8"><a href="#cb21-8" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb21-9"><a href="#cb21-9" tabindex="-1"></a>    actual_result <span class="op">=</span> text_to_duration(<span class="st">"10:20"</span>) </span>
+<span id="cb21-10"><a href="#cb21-10" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="fl">10.33333333</span></span>
+<span id="cb21-11"><a href="#cb21-11" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> pytest.approx(expected_result)</span>
+<span id="cb21-12"><a href="#cb21-12" tabindex="-1"></a>    </span>
+<span id="cb21-13"><a href="#cb21-13" tabindex="-1"></a><span class="kw">def</span> test_text_to_duration_integer():</span>
+<span id="cb21-14"><a href="#cb21-14" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb21-15"><a href="#cb21-15" tabindex="-1"></a><span class="co">    Test that text_to_duration returns expected ground truth values</span></span>
+<span id="cb21-16"><a href="#cb21-16" tabindex="-1"></a><span class="co">    for typical whole hour durations </span></span>
+<span id="cb21-17"><a href="#cb21-17" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb21-18"><a href="#cb21-18" tabindex="-1"></a>    actual_result <span class="op">=</span>  text_to_duration(<span class="st">"10:00"</span>)</span>
+<span id="cb21-19"><a href="#cb21-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">10</span></span>
+<span id="cb21-20"><a href="#cb21-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb21-21"><a href="#cb21-21" tabindex="-1"></a>    </span></code></pre>
 </div>
 <p>Writing our tests this way highlights the key idea that each test
 should compare the actual results returned by our function with expected
@@ -5368,23 +5371,23 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <p>Similarly, writing inline comments for our tests that complete the
 sentence “Test that …” helps us to understand what each test is doing
 and why it is needed.</p>
-<p>Before running out tests with <code>putest</code>, let’s reintroduce
+<p>Before running out tests with <code>pytest</code>, let’s reintroduce
 our old bug in function <code>text_to_duration</code> that affects the
 durations with a non-zero minute component like “10:20” but not those
 that are whole hours, e.g. “10:00”:</p>
-<div class="codewrapper sourceCode" id="cb23">
+<div class="codewrapper sourceCode" id="cb22">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a>    ...</span>
-<span id="cb23-2"><a href="#cb23-2" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span>  <span class="co"># Divide by 6 instead of 60</span></span>
-<span id="cb23-3"><a href="#cb23-3" tabindex="-1"></a>    ...</span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a>    ...</span>
+<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a>    duration_hours <span class="op">=</span> <span class="bu">int</span>(hours) <span class="op">+</span> <span class="bu">int</span>(minutes)<span class="op">/</span><span class="dv">6</span>  <span class="co"># Divide by 6 instead of 60</span></span>
+<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a>    ...</span></code></pre>
 </div>
 <p>Finally, let’s run our tests with <code>pytest</code> from our
 project’s root directory (and not <code>tests</code> directory):</p>
-<div class="codewrapper sourceCode" id="cb24">
+<div class="codewrapper sourceCode" id="cb23">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest </span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">ERROR<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -5439,6 +5442,7 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 
 =========================================== 2 passed in 0.63s =============================================</code></pre>
 </div>
+<p>This time, all out tests passed.</p>
 <div id="interpreting-pytest-output" class="callout challenge">
 <div class="callout-square">
 <i class="callout-icon" data-feather="zap"></i>
@@ -5558,70 +5562,70 @@ <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 that alone is not enough to properly test code. We will now look into
 what makes a good test suite and good practices for testing code.</p>
 <p>Let’s start by considering the following scenario. A collaborator on
-our project has sent us the following code which adds a new column to
-our data containing the <code>crew_size</code> values capturing the
-number of astronauts participating in any given spacewalk. How do we
-know that it works as intended and that it will not break the rest of
-our code? For this, we need to write a test suite with a comprehensive
-coverage of the new code.</p>
-<div class="codewrapper sourceCode" id="cb28">
+our project has sent us the following code which adds a new column
+called <code>crew_size</code> to our data containing the number of
+astronauts participating in any given spacewalk. How do we know that it
+works as intended and that it will not break the rest of our code? For
+this, we need to write a test suite with a comprehensive coverage of the
+new code.</p>
+<div class="codewrapper sourceCode" id="cb27">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb28-1"><a href="#cb28-1" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
-<span id="cb28-2"><a href="#cb28-2" tabindex="-1"></a><span class="im">import</span> pandas <span class="im">as</span> pd</span>
-<span id="cb28-3"><a href="#cb28-3" tabindex="-1"></a><span class="im">import</span> sys</span>
-<span id="cb28-4"><a href="#cb28-4" tabindex="-1"></a><span class="im">import</span> re <span class="co"># added this line</span></span>
-<span id="cb28-5"><a href="#cb28-5" tabindex="-1"></a></span>
-<span id="cb28-6"><a href="#cb28-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
-<span id="cb28-7"><a href="#cb28-7" tabindex="-1"></a></span>
-<span id="cb28-8"><a href="#cb28-8" tabindex="-1"></a><span class="kw">def</span> main(input_file, output_file, graph_file):</span>
-<span id="cb28-9"><a href="#cb28-9" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--START--"</span>)</span>
-<span id="cb28-10"><a href="#cb28-10" tabindex="-1"></a></span>
-<span id="cb28-11"><a href="#cb28-11" tabindex="-1"></a>    eva_data <span class="op">=</span> read_json_to_dataframe(input_file)</span>
-<span id="cb28-12"><a href="#cb28-12" tabindex="-1"></a></span>
-<span id="cb28-13"><a href="#cb28-13" tabindex="-1"></a>    eva_data <span class="op">=</span> add_crew_size_column(eva_data) <span class="co"># added this line</span></span>
-<span id="cb28-14"><a href="#cb28-14" tabindex="-1"></a></span>
-<span id="cb28-15"><a href="#cb28-15" tabindex="-1"></a>    write_dataframe_to_csv(eva_data, output_file)</span>
-<span id="cb28-16"><a href="#cb28-16" tabindex="-1"></a></span>
-<span id="cb28-17"><a href="#cb28-17" tabindex="-1"></a>    plot_cumulative_time_in_space(eva_data, graph_file)</span>
-<span id="cb28-18"><a href="#cb28-18" tabindex="-1"></a></span>
-<span id="cb28-19"><a href="#cb28-19" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--END--"</span>)</span>
-<span id="cb28-20"><a href="#cb28-20" tabindex="-1"></a></span>
-<span id="cb28-21"><a href="#cb28-21" tabindex="-1"></a>... </span>
-<span id="cb28-22"><a href="#cb28-22" tabindex="-1"></a></span>
-<span id="cb28-23"><a href="#cb28-23" tabindex="-1"></a><span class="kw">def</span> calculate_crew_size(crew):</span>
-<span id="cb28-24"><a href="#cb28-24" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb28-25"><a href="#cb28-25" tabindex="-1"></a><span class="co">    Calculate the size of the crew for a single crew entry</span></span>
-<span id="cb28-26"><a href="#cb28-26" tabindex="-1"></a></span>
-<span id="cb28-27"><a href="#cb28-27" tabindex="-1"></a><span class="co">    Args:</span></span>
-<span id="cb28-28"><a href="#cb28-28" tabindex="-1"></a><span class="co">        crew (str): The text entry in the crew column containing a list of crew member names</span></span>
-<span id="cb28-29"><a href="#cb28-29" tabindex="-1"></a></span>
-<span id="cb28-30"><a href="#cb28-30" tabindex="-1"></a><span class="co">    Returns:</span></span>
-<span id="cb28-31"><a href="#cb28-31" tabindex="-1"></a><span class="co">        int: The crew size</span></span>
-<span id="cb28-32"><a href="#cb28-32" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb28-33"><a href="#cb28-33" tabindex="-1"></a>    <span class="cf">if</span> crew.split() <span class="op">==</span> []:</span>
-<span id="cb28-34"><a href="#cb28-34" tabindex="-1"></a>        <span class="cf">return</span> <span class="va">None</span></span>
-<span id="cb28-35"><a href="#cb28-35" tabindex="-1"></a>    <span class="cf">else</span>:</span>
-<span id="cb28-36"><a href="#cb28-36" tabindex="-1"></a>        <span class="cf">return</span> <span class="bu">len</span>(re.split(<span class="vs">r';'</span>, crew))<span class="op">-</span><span class="dv">1</span></span>
-<span id="cb28-37"><a href="#cb28-37" tabindex="-1"></a></span>
-<span id="cb28-38"><a href="#cb28-38" tabindex="-1"></a><span class="kw">def</span> add_crew_size_column(df):</span>
-<span id="cb28-39"><a href="#cb28-39" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb28-40"><a href="#cb28-40" tabindex="-1"></a><span class="co">    Add crew_size column to the dataset containing the value of the crew size</span></span>
-<span id="cb28-41"><a href="#cb28-41" tabindex="-1"></a></span>
-<span id="cb28-42"><a href="#cb28-42" tabindex="-1"></a><span class="co">    Args:</span></span>
-<span id="cb28-43"><a href="#cb28-43" tabindex="-1"></a><span class="co">        df (pd.DataFrame): The input data frame.</span></span>
-<span id="cb28-44"><a href="#cb28-44" tabindex="-1"></a></span>
-<span id="cb28-45"><a href="#cb28-45" tabindex="-1"></a><span class="co">    Returns:</span></span>
-<span id="cb28-46"><a href="#cb28-46" tabindex="-1"></a><span class="co">        df_copy (pd.DataFrame): A copy of df with the new crew_size variable added</span></span>
-<span id="cb28-47"><a href="#cb28-47" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb28-48"><a href="#cb28-48" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">'Adding crew size variable (crew_size) to dataset'</span>)</span>
-<span id="cb28-49"><a href="#cb28-49" tabindex="-1"></a>    df_copy <span class="op">=</span> df.copy()</span>
-<span id="cb28-50"><a href="#cb28-50" tabindex="-1"></a>    df_copy[<span class="st">"crew_size"</span>] <span class="op">=</span> df_copy[<span class="st">"crew"</span>].<span class="bu">apply</span>(</span>
-<span id="cb28-51"><a href="#cb28-51" tabindex="-1"></a>        calculate_crew_size</span>
-<span id="cb28-52"><a href="#cb28-52" tabindex="-1"></a>    )</span>
-<span id="cb28-53"><a href="#cb28-53" tabindex="-1"></a>    <span class="cf">return</span> df_copy</span>
-<span id="cb28-54"><a href="#cb28-54" tabindex="-1"></a>...</span>
-<span id="cb28-55"><a href="#cb28-55" tabindex="-1"></a>    </span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="im">import</span> matplotlib.pyplot <span class="im">as</span> plt</span>
+<span id="cb27-2"><a href="#cb27-2" tabindex="-1"></a><span class="im">import</span> pandas <span class="im">as</span> pd</span>
+<span id="cb27-3"><a href="#cb27-3" tabindex="-1"></a><span class="im">import</span> sys</span>
+<span id="cb27-4"><a href="#cb27-4" tabindex="-1"></a><span class="im">import</span> re <span class="co"># added this line</span></span>
+<span id="cb27-5"><a href="#cb27-5" tabindex="-1"></a></span>
+<span id="cb27-6"><a href="#cb27-6" tabindex="-1"></a><span class="co"># https://data.nasa.gov/resource/eva.json (with modifications)</span></span>
+<span id="cb27-7"><a href="#cb27-7" tabindex="-1"></a></span>
+<span id="cb27-8"><a href="#cb27-8" tabindex="-1"></a><span class="kw">def</span> main(input_file, output_file, graph_file):</span>
+<span id="cb27-9"><a href="#cb27-9" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--START--"</span>)</span>
+<span id="cb27-10"><a href="#cb27-10" tabindex="-1"></a></span>
+<span id="cb27-11"><a href="#cb27-11" tabindex="-1"></a>    eva_data <span class="op">=</span> read_json_to_dataframe(input_file)</span>
+<span id="cb27-12"><a href="#cb27-12" tabindex="-1"></a></span>
+<span id="cb27-13"><a href="#cb27-13" tabindex="-1"></a>    eva_data <span class="op">=</span> add_crew_size_column(eva_data) <span class="co"># added this line</span></span>
+<span id="cb27-14"><a href="#cb27-14" tabindex="-1"></a></span>
+<span id="cb27-15"><a href="#cb27-15" tabindex="-1"></a>    write_dataframe_to_csv(eva_data, output_file)</span>
+<span id="cb27-16"><a href="#cb27-16" tabindex="-1"></a></span>
+<span id="cb27-17"><a href="#cb27-17" tabindex="-1"></a>    plot_cumulative_time_in_space(eva_data, graph_file)</span>
+<span id="cb27-18"><a href="#cb27-18" tabindex="-1"></a></span>
+<span id="cb27-19"><a href="#cb27-19" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">"--END--"</span>)</span>
+<span id="cb27-20"><a href="#cb27-20" tabindex="-1"></a></span>
+<span id="cb27-21"><a href="#cb27-21" tabindex="-1"></a>... </span>
+<span id="cb27-22"><a href="#cb27-22" tabindex="-1"></a></span>
+<span id="cb27-23"><a href="#cb27-23" tabindex="-1"></a><span class="kw">def</span> calculate_crew_size(crew):</span>
+<span id="cb27-24"><a href="#cb27-24" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb27-25"><a href="#cb27-25" tabindex="-1"></a><span class="co">    Calculate the size of the crew for a single crew entry</span></span>
+<span id="cb27-26"><a href="#cb27-26" tabindex="-1"></a></span>
+<span id="cb27-27"><a href="#cb27-27" tabindex="-1"></a><span class="co">    Args:</span></span>
+<span id="cb27-28"><a href="#cb27-28" tabindex="-1"></a><span class="co">        crew (str): The text entry in the crew column containing a list of crew member names</span></span>
+<span id="cb27-29"><a href="#cb27-29" tabindex="-1"></a></span>
+<span id="cb27-30"><a href="#cb27-30" tabindex="-1"></a><span class="co">    Returns:</span></span>
+<span id="cb27-31"><a href="#cb27-31" tabindex="-1"></a><span class="co">        int: The crew size</span></span>
+<span id="cb27-32"><a href="#cb27-32" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb27-33"><a href="#cb27-33" tabindex="-1"></a>    <span class="cf">if</span> crew.split() <span class="op">==</span> []:</span>
+<span id="cb27-34"><a href="#cb27-34" tabindex="-1"></a>        <span class="cf">return</span> <span class="va">None</span></span>
+<span id="cb27-35"><a href="#cb27-35" tabindex="-1"></a>    <span class="cf">else</span>:</span>
+<span id="cb27-36"><a href="#cb27-36" tabindex="-1"></a>        <span class="cf">return</span> <span class="bu">len</span>(re.split(<span class="vs">r';'</span>, crew))<span class="op">-</span><span class="dv">1</span></span>
+<span id="cb27-37"><a href="#cb27-37" tabindex="-1"></a></span>
+<span id="cb27-38"><a href="#cb27-38" tabindex="-1"></a><span class="kw">def</span> add_crew_size_column(df):</span>
+<span id="cb27-39"><a href="#cb27-39" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb27-40"><a href="#cb27-40" tabindex="-1"></a><span class="co">    Add crew_size column to the dataset containing the value of the crew size</span></span>
+<span id="cb27-41"><a href="#cb27-41" tabindex="-1"></a></span>
+<span id="cb27-42"><a href="#cb27-42" tabindex="-1"></a><span class="co">    Args:</span></span>
+<span id="cb27-43"><a href="#cb27-43" tabindex="-1"></a><span class="co">        df (pd.DataFrame): The input data frame.</span></span>
+<span id="cb27-44"><a href="#cb27-44" tabindex="-1"></a></span>
+<span id="cb27-45"><a href="#cb27-45" tabindex="-1"></a><span class="co">    Returns:</span></span>
+<span id="cb27-46"><a href="#cb27-46" tabindex="-1"></a><span class="co">        df_copy (pd.DataFrame): A copy of df with the new crew_size variable added</span></span>
+<span id="cb27-47"><a href="#cb27-47" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb27-48"><a href="#cb27-48" tabindex="-1"></a>    <span class="bu">print</span>(<span class="st">'Adding crew size variable (crew_size) to dataset'</span>)</span>
+<span id="cb27-49"><a href="#cb27-49" tabindex="-1"></a>    df_copy <span class="op">=</span> df.copy()</span>
+<span id="cb27-50"><a href="#cb27-50" tabindex="-1"></a>    df_copy[<span class="st">"crew_size"</span>] <span class="op">=</span> df_copy[<span class="st">"crew"</span>].<span class="bu">apply</span>(</span>
+<span id="cb27-51"><a href="#cb27-51" tabindex="-1"></a>        calculate_crew_size</span>
+<span id="cb27-52"><a href="#cb27-52" tabindex="-1"></a>    )</span>
+<span id="cb27-53"><a href="#cb27-53" tabindex="-1"></a>    <span class="cf">return</span> df_copy</span>
+<span id="cb27-54"><a href="#cb27-54" tabindex="-1"></a>...</span>
+<span id="cb27-55"><a href="#cb27-55" tabindex="-1"></a>    </span></code></pre>
 </div>
 <div class="section level3">
 <h3 id="writing-good-tests">Writing good tests<a class="anchor" aria-label="anchor" href="#writing-good-tests"></a>
@@ -5675,38 +5679,44 @@ <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
 <div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
 <div class="accordion-body">
 <p>We can add the following test functions to out test suite.</p>
-<div class="codewrapper sourceCode" id="cb30">
+<div class="codewrapper sourceCode" id="cb29">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
-<span id="cb30-2"><a href="#cb30-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> (</span>
-<span id="cb30-3"><a href="#cb30-3" tabindex="-1"></a>    text_to_duration,</span>
-<span id="cb30-4"><a href="#cb30-4" tabindex="-1"></a>    calculate_crew_size</span>
-<span id="cb30-5"><a href="#cb30-5" tabindex="-1"></a>)</span>
-<span id="cb30-6"><a href="#cb30-6" tabindex="-1"></a></span>
-<span id="cb30-7"><a href="#cb30-7" tabindex="-1"></a>...</span>
-<span id="cb30-8"><a href="#cb30-8" tabindex="-1"></a></span>
-<span id="cb30-9"><a href="#cb30-9" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size():</span>
-<span id="cb30-10"><a href="#cb30-10" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb30-11"><a href="#cb30-11" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
-<span id="cb30-12"><a href="#cb30-12" tabindex="-1"></a><span class="co">    for typical crew values</span></span>
-<span id="cb30-13"><a href="#cb30-13" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb30-14"><a href="#cb30-14" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Valentina Tereshkova;"</span>)</span>
-<span id="cb30-15"><a href="#cb30-15" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">1</span></span>
-<span id="cb30-16"><a href="#cb30-16" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb30-17"><a href="#cb30-17" tabindex="-1"></a></span>
-<span id="cb30-18"><a href="#cb30-18" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Judith Resnik; Sally Ride;"</span>)</span>
-<span id="cb30-19"><a href="#cb30-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
-<span id="cb30-20"><a href="#cb30-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
-<span id="cb30-21"><a href="#cb30-21" tabindex="-1"></a></span>
-<span id="cb30-22"><a href="#cb30-22" tabindex="-1"></a><span class="co"># Edge cases</span></span>
-<span id="cb30-23"><a href="#cb30-23" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size_edge_cases():</span>
-<span id="cb30-24"><a href="#cb30-24" tabindex="-1"></a>    <span class="co">"""</span></span>
-<span id="cb30-25"><a href="#cb30-25" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
-<span id="cb30-26"><a href="#cb30-26" tabindex="-1"></a><span class="co">    for edge case where crew is an empty string</span></span>
-<span id="cb30-27"><a href="#cb30-27" tabindex="-1"></a><span class="co">    """</span></span>
-<span id="cb30-28"><a href="#cb30-28" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">""</span>)</span>
-<span id="cb30-29"><a href="#cb30-29" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="kw">is</span> <span class="va">None</span></span></code></pre>
+<pre class="sourceCode python" tabindex="0"><code class="sourceCode python"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="im">import</span> pytest</span>
+<span id="cb29-2"><a href="#cb29-2" tabindex="-1"></a><span class="im">from</span> eva_data_analysis <span class="im">import</span> (</span>
+<span id="cb29-3"><a href="#cb29-3" tabindex="-1"></a>    text_to_duration,</span>
+<span id="cb29-4"><a href="#cb29-4" tabindex="-1"></a>    calculate_crew_size</span>
+<span id="cb29-5"><a href="#cb29-5" tabindex="-1"></a>)</span>
+<span id="cb29-6"><a href="#cb29-6" tabindex="-1"></a></span>
+<span id="cb29-7"><a href="#cb29-7" tabindex="-1"></a>...</span>
+<span id="cb29-8"><a href="#cb29-8" tabindex="-1"></a></span>
+<span id="cb29-9"><a href="#cb29-9" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size():</span>
+<span id="cb29-10"><a href="#cb29-10" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb29-11"><a href="#cb29-11" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
+<span id="cb29-12"><a href="#cb29-12" tabindex="-1"></a><span class="co">    for typical crew values</span></span>
+<span id="cb29-13"><a href="#cb29-13" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb29-14"><a href="#cb29-14" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Valentina Tereshkova;"</span>)</span>
+<span id="cb29-15"><a href="#cb29-15" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">1</span></span>
+<span id="cb29-16"><a href="#cb29-16" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb29-17"><a href="#cb29-17" tabindex="-1"></a></span>
+<span id="cb29-18"><a href="#cb29-18" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">"Judith Resnik; Sally Ride;"</span>)</span>
+<span id="cb29-19"><a href="#cb29-19" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
+<span id="cb29-20"><a href="#cb29-20" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span>
+<span id="cb29-21"><a href="#cb29-21" tabindex="-1"></a></span>
+<span id="cb29-22"><a href="#cb29-22" tabindex="-1"></a><span class="co"># Edge cases</span></span>
+<span id="cb29-23"><a href="#cb29-23" tabindex="-1"></a><span class="kw">def</span> test_calculate_crew_size_edge_cases():</span>
+<span id="cb29-24"><a href="#cb29-24" tabindex="-1"></a>    <span class="co">"""</span></span>
+<span id="cb29-25"><a href="#cb29-25" tabindex="-1"></a><span class="co">    Test that calculate_crew_size returns expected ground truth values</span></span>
+<span id="cb29-26"><a href="#cb29-26" tabindex="-1"></a><span class="co">    for edge case where crew is an empty string</span></span>
+<span id="cb29-27"><a href="#cb29-27" tabindex="-1"></a><span class="co">    """</span></span>
+<span id="cb29-28"><a href="#cb29-28" tabindex="-1"></a>    actual_result <span class="op">=</span> calculate_crew_size(<span class="st">""</span>)</span>
+<span id="cb29-29"><a href="#cb29-29" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="kw">is</span> <span class="va">None</span></span></code></pre>
+</div>
+<p>Let’s run out tests:</p>
+<div class="codewrapper sourceCode" id="cb30">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pytest</span></code></pre>
 </div>
 </div>
 </div>
@@ -5737,9 +5747,9 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <span id="cb31-11"><a href="#cb31-11" tabindex="-1"></a>    expected_result <span class="op">=</span> <span class="dv">2</span></span>
 <span id="cb31-12"><a href="#cb31-12" tabindex="-1"></a>    <span class="cf">assert</span> actual_result <span class="op">==</span> expected_result</span></code></pre>
 </div>
-<p>To avoid such repetitions in our test code, we can <strong>test
+<p>To avoid such repetitions in our test code, we use <strong>test
 parameterisation</strong>. This allows us to apply our test function to
-a list of input / expected output pairs without the need for repetition.
+a list of input/expected output pairs without the need for repetition.
 To parameterise the <code>test_calculate_crew_size</code> function, we
 can rewrite is as follows:</p>
 <div class="codewrapper sourceCode" id="cb32">
@@ -6029,7 +6039,7 @@ <h3 class="callout-title">Key Points</h3>
  -->
 </section></section><section id="aio-09-code-documentation"><p>Content from <a href="09-code-documentation.html">Code documentation</a></p>
 <hr>
-<p>Last updated on 2024-09-26 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/09-code-documentation.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 90 minutes</p>
@@ -6093,8 +6103,8 @@ <h3 class="callout-title">Activate your virtual environment</h3>
 <div class="codewrapper sourceCode" id="cb1">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="ex">$</span> source venv_spacewalks/bin/activate <span class="co"># Mac or Linux</span></span>
-<span id="cb1-2"><a href="#cb1-2" tabindex="-1"></a><span class="ex">$</span> source venv_spacewalks/Scripts/activate <span class="co"># Windows</span></span>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb1-1"><a href="#cb1-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> source venv_spacewalks/bin/activate <span class="co"># Mac or Linux</span></span>
+<span id="cb1-2"><a href="#cb1-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> source venv_spacewalks/Scripts/activate <span class="co"># Windows</span></span>
 <span id="cb1-3"><a href="#cb1-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span></span></code></pre>
 </div>
 </div>
@@ -6146,10 +6156,9 @@ <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square">
 <hr class="half-width">
 <p>In previous episodes we encountered several different forms of
 in-code documentation aspects, including in-line comments and
-docstrings.</p>
-<p>These are an excellent way to improve the readability of our code,
-but by themselves are insufficient to ensure that our code is easy to
-use, understand and modify - this requires additional software-level
+docstrings. These are an excellent way to improve the readability of our
+code, but by themselves are insufficient to ensure that our code is easy
+to use, understand and modify - this requires additional software-level
 documentation.</p>
 <p>There are many different types of software-level documentation.</p>
 <div class="section level3">
@@ -6168,15 +6177,22 @@ <h3 id="technical-documentation">Technical documentation<a class="anchor" aria-l
 understand implementation decisions</li>
 </ul>
 </div>
+</section><section><h2 class="section-heading" id="project-level-documentation">Project-level documentation<a class="anchor" aria-label="anchor" href="#project-level-documentation"></a>
+</h2>
+<hr class="half-width">
+<p>Project-level documentation includes various information and metadata
+about software that help to discover it, explain the legal terms of
+reusing it, describe its functionality on a high level and how to
+install, run and contribute to it.</p>
 <div class="section level3">
 <h3 id="repository-metadata-files">Repository metadata files<a class="anchor" aria-label="anchor" href="#repository-metadata-files"></a>
 </h3>
-<p>In addition to software-level technical documentation, it is also
-common to see repository metadata files included in a code repository.
-Many of these files can be described as “social documentation” i.e. they
-indicate how users should “behave” in relation to our software project.
-Some common examples of repository metadata files and their role are
-tabulated below:</p>
+<p>A common way to to provide project-level documentation is to include
+various metadata files in the software repository together with code.
+Many of these files can be described as “social documentation”,
+i.e. they indicate how users should “behave” in relation to our software
+project. Some common examples of repository metadata files and their
+role are explained below:</p>
 <table class="table">
 <colgroup>
 <col width="7%">
@@ -6219,13 +6235,20 @@ <h3 id="repository-metadata-files">Repository metadata files<a class="anchor" ar
 </tr>
 </tbody>
 </table>
+<div id="just-enough-documentation" class="callout">
+<div class="callout-square">
+<i class="callout-icon" data-feather="bell"></i>
+</div>
+<div id="just-enough-documentation" class="callout-inner">
+<h3 class="callout-title">Just enough documentation</h3>
+<div class="callout-content">
+<p>For many small projects the following three pieces of project-level
+documentation may be sufficient: README, LICENSE and CITATION.</p>
+</div>
+</div>
 </div>
-</section><section><h2 class="section-heading" id="just-enough-documentation">Just enough documentation<a class="anchor" aria-label="anchor" href="#just-enough-documentation"></a>
-</h2>
-<hr class="half-width">
-<p>For many small projects the following three pieces of documentation
-may be sufficient: README, LICENSE and CITATION.</p>
 <p>Let’s look at each of these files in turn.</p>
+</div>
 <div class="section level3">
 <h3 id="readme-file">README file<a class="anchor" aria-label="anchor" href="#readme-file"></a>
 </h3>
@@ -6328,23 +6351,20 @@ <h4 id="optional">Optional<a class="anchor" aria-label="anchor" href="#optional"
 </div>
 </div>
 </div>
-<p>Let’s create a simple README for our repository.</p>
-<div class="codewrapper sourceCode" id="cb2">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb2-1"><a href="#cb2-1" tabindex="-1"></a><span class="ex">$</span> cd ~/Desktop/Spacewalks</span>
-<span id="cb2-2"><a href="#cb2-2" tabindex="-1"></a><span class="ex">$</span> touch README.md</span></code></pre>
-</div>
-<p>Let’s start by adding a one-liner that explains the purpose of our
+<p>Let’s create a simple README for our repository - from VS Code or
+command line terminal create file <code>README.md</code> (in Markdown
+format) or <code>README.txt</code> (in plain text format).</p>
+<p>We can start by adding a one-liner that explains the purpose of our
 code and who it is for.</p>
 <pre class="code"><code># Spacewalks
 
 ## Overview
-Spacewalks is a python-based analysis tool for researchers to generate visualisations
+Spacewalks is a Python analysis tool for researchers to generate visualisations
 and statistical summaries of NASA's extravehicular activity datasets.</code></pre>
 <p>Now let’s add a list of Spacewalks’ key features:</p>
 <pre class="code"><code>## Features
 Key features of Spacewalks:
+
 - Generates a CSV table of summary statistics of extravehicular activity crew sizes
 - Generates a line plot to show the cumulative duration of space walks over time</code></pre>
 <p>Now let’s tell users about any pre-requisites required to run the
@@ -6367,8 +6387,11 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div id="spacewalks-readme" class="callout-inner">
 <h3 class="callout-title">Spacewalks README</h3>
 <div class="callout-content">
-<p>Extend the README for Spacewalks by adding a. Installation
-instructions b. A simple usage example</p>
+<p>Extend the README for Spacewalks by adding:</p>
+<ol style="list-style-type: decimal">
+<li>Installation instructions</li>
+<li>A simple usage example</li>
+</ol>
 </div>
 </div>
 </div>
@@ -6381,39 +6404,40 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 <div class="accordion-body">
 <p>Installation instructions:</p>
 <p>NB: In the solution below the back ticks of each code block have been
-escaped to avoid rendering issues.</p>
-<pre class="text"><code># Installation instructions
+escaped to avoid rendering issues (if you are copying and pasting the
+text, make sure you unescape them).</p>
+<pre class="text"><code>## Installation instructions
 
 + Clone the Spacewalks repository to your local machine using Git.
 If you don't have Git installed, you can download it from the official Git website.
 
-\`\`\`bash
+\`\`\`
 git clone https://github.com/your-repository-url/spacewalks.git
 cd spacewalks
 \`\`\`
 
 + Install the necessary dependencies:
-\`\`\`bash
-pip install pandas==2.2.2 matplotlib==3.8.4 numpy==2.0.0 pytest==7.4.2
+\`\`\`
+python3 -m pip install pandas==2.2.2 matplotlib==3.8.4 numpy==2.0.0 pytest==7.4.2
 \`\`\`
 
 + To ensure everything is working correctly, run the tests using pytest.
 
-\`\`\`bash
-python -m pytest
+\`\`\`
+python3 -m pytest
 \`\`\`</code></pre>
 <p>Usage instructions:</p>
-<pre class="text"><code># Usage Example
+<pre class="text"><code>## Usage Example
 
 To run an analysis using the eva_data_analysis.py script from the command line terminal,
 launch the script using Python as follows:
 
-\`\`\`python
+\`\`\`
 # Usage Examples
-python eva_data_analysis.py eva-data.json eva-data.csv
+python3 eva_data_analysis.py eva-data.json eva-data.csv
 \`\`\`
 
-The first argument is path to the Json data file.
+The first argument is path to the JSON data file.
 The second argument is the path the CSV output file.</code></pre>
 </div>
 </div>
@@ -6540,155 +6564,130 @@ <h3 id="citation-file">CITATION file<a class="anchor" aria-label="anchor" href="
 </h3>
 <p>We can add a citation file to our repository to provide instructions
 on how and when to cite our code. A citation file can be a plain text
-(CITATION.txt) or a Markdown file (CITATION.md), but there are certain
-benefits to use a special file format called the Citation File Format
-(CFF) which provides a way to include richer metadata about software or
-datasets we want to cite, making it easy for both humans and machines to
-use this information.</p>
+(<code>CITATION.txt</code>) or a Markdown file
+(<code>CITATION.md</code>), but there are certain benefits to use a
+special file format called the Citation File Format (CFF) which provides
+a way to include richer metadata about software or datasets we want to
+cite, making it easy for both humans and machines to use this
+information.</p>
 <div class="section level4">
 <h4 id="why-use-cff">Why use CFF?<a class="anchor" aria-label="anchor" href="#why-use-cff"></a>
 </h4>
 <p>For developers, using a CFF file can help to automate the process of
-publishing new releases on Zenodo via GitHub. GitHub also “understands”
-CFF, and will display citation information prominently on the landing
-page of a repository that contains citation info in CFF.</p>
+publishing new releases on <a href="https://zenodo.org/" class="external-link">Zenodo</a> via
+GitHub. GitHub also “understands” CFF, and will display citation
+information prominently on the landing page of a repository that
+contains citation info in CFF.</p>
 <p>For users, having a CFF file makes it easy to cite the software or
 dataset with formatted citation information available for copy-paste and
 direct import from GitHub into reference managers like Zotero.</p>
 </div>
 <div class="section level4">
-<h4 id="creating-a-cff-file">Creating a CFF file<a class="anchor" aria-label="anchor" href="#creating-a-cff-file"></a>
+<h4 id="cff-file-format">CFF file format<a class="anchor" aria-label="anchor" href="#cff-file-format"></a>
 </h4>
 <p>A CFF file is using the <a href="https://yaml.org/" class="external-link">YAML</a>
 key-value pair format. At a minimum a CFF file must contain the title of
 the software/data, the type of asset (software or data) and at least one
 author:</p>
-<div class="codewrapper sourceCode" id="cb8">
+<div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
-<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb8-10"><a href="#cb8-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
-<span id="cb8-11"><a href="#cb8-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
+<span id="cb7-2"><a href="#cb7-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
+<span id="cb7-3"><a href="#cb7-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb7-4"><a href="#cb7-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
+<span id="cb7-5"><a href="#cb7-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb7-6"><a href="#cb7-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb7-7"><a href="#cb7-7" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb7-8"><a href="#cb7-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb7-9"><a href="#cb7-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb7-10"><a href="#cb7-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
+<span id="cb7-11"><a href="#cb7-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span></code></pre>
 </div>
 <p>Additional and optional metadata includes an abstract, repository URL
 and more.</p>
 </div>
 <div class="section level4">
-<h4 id="steps-to-make-your-software-citable">Steps to make your software citable<a class="anchor" aria-label="anchor" href="#steps-to-make-your-software-citable"></a>
+<h4 id="creating-cff-file-and-making-your-software-citable">Creating CFF file and making your software citable<a class="anchor" aria-label="anchor" href="#creating-cff-file-and-making-your-software-citable"></a>
 </h4>
-<p>We can create (and update) a CFF file for our software using an
-online application called <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a>.</p>
-<p>Let’s create a dummy citation file for a project called “Spacetravel”
-with Author “Max Hypothesis” by following these steps:</p>
+<p>We can create (and later update) a CFF file for our software using an
+online application called <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a> by following
+these steps:</p>
 <ol style="list-style-type: decimal">
-<li>First, head to <code>cffinit</code> online at <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code></a>.</li>
-<li>Then, let’s work through the metadata input form to complete the
-minimum information needed to generate a CFF. We’ll also add the
-following abstract:
-<code>"Spacetravel - a simple python script to calculate time spent in Space by individual NASA astronauts"</code>
+<li><p>Head to <a href="https://bit.ly/cffinit" class="external-link"><code>cffinit</code>
+online tool</a>.</p></li>
+<li>
+<p>Then, work through the metadata input form to complete the
+minimum information needed to generate a CFF.</p>
+<p>We can use the following description as an “Abstract”: “A Python
+script to analyse NASA extravehicular activity data”</p>
+<p>Add the URL of the code repository as a “Related Resources”.</p>
+<p>Add at least two key words under the “Keywords” section.</p>
 </li>
-<li>At the end of the process, download the CFF file and inspect it. It
-should look like this:</li>
+<li><p>At the end of the process, download the CFF file and inspect it.
+It should look like this:</p></li>
 </ol>
-<div class="codewrapper sourceCode" id="cb9">
+<div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a></span>
-<span id="cb9-4"><a href="#cb9-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb9-5"><a href="#cb9-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacetravel</span></span>
-<span id="cb9-6"><a href="#cb9-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb9-7"><a href="#cb9-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb9-8"><a href="#cb9-8" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb9-9"><a href="#cb9-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb9-10"><a href="#cb9-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb9-11"><a href="#cb9-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Hypothesis</span></span>
-<span id="cb9-12"><a href="#cb9-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Max</span></span>
-<span id="cb9-13"><a href="#cb9-13" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb9-14"><a href="#cb9-14" tabindex="-1"></a>    A simple python script to calculate time spent in Space by individual NASA astronauts</span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
+<span id="cb8-2"><a href="#cb8-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
+<span id="cb8-3"><a href="#cb8-3" tabindex="-1"></a></span>
+<span id="cb8-4"><a href="#cb8-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb8-5"><a href="#cb8-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
+<span id="cb8-6"><a href="#cb8-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-7"><a href="#cb8-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb8-8"><a href="#cb8-8" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb8-9"><a href="#cb8-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb8-10"><a href="#cb8-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb8-11"><a href="#cb8-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
+<span id="cb8-12"><a href="#cb8-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
+<span id="cb8-13"><a href="#cb8-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
+<span id="cb8-14"><a href="#cb8-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
+<span id="cb8-15"><a href="#cb8-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
+<span id="cb8-16"><a href="#cb8-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
+<span id="cb8-17"><a href="#cb8-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-18"><a href="#cb8-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
+<span id="cb8-19"><a href="#cb8-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb8-20"><a href="#cb8-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
+<span id="cb8-21"><a href="#cb8-21" tabindex="-1"></a>  data</span>
+<span id="cb8-22"><a href="#cb8-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
+<span id="cb8-23"><a href="#cb8-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
+<span id="cb8-24"><a href="#cb8-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span></code></pre>
 </div>
+<p>CFF files can also be updated using the <code>cffinit</code> online
+tool by pasting the previous version of CFF file and working through the
+form to update various fields.</p>
 </div>
 <div class="section level4">
-<h4 id="updating-and-citing">Updating and citing<a class="anchor" aria-label="anchor" href="#updating-and-citing"></a>
+<h4 id="citing">Citing<a class="anchor" aria-label="anchor" href="#citing"></a>
 </h4>
-<p>CFF files can also be updated using the <code>cffinit</code> online
-tool.</p>
 <p>To cite our software (or dataset), once a CFF file has been pushed to
 our remote repository, GitHub’s “Cite this repository” button can be
 used to generate a citation in various formats (APA, BibTeX).</p>
-</div>
-<div class="section level4">
-<h4 id="tools">Tools<a class="anchor" aria-label="anchor" href="#tools"></a>
-</h4>
-<p>Command line tools are also available for creating, validating, and
-converting CFF files. Further information is available from the <a href="https://book.the-turing-way.org/communication/citable/citable-cff.html" class="external-link">Turing
-Way’s guide to software citation</a>.</p>
-<div id="spacewalks-software-citation" class="callout challenge">
+<div id="section" class="callout">
 <div class="callout-square">
-<i class="callout-icon" data-feather="zap"></i>
+<i class="callout-icon" data-feather="bell"></i>
 </div>
-<div id="spacewalks-software-citation" class="callout-inner">
-<h3 class="callout-title">Spacewalks software citation</h3>
+<div id="section" class="callout-inner">
+<h3 class="callout-title"></h3>
 <div class="callout-content">
-<p>Write a software citation file for our Spacewalks software and add it
-to the root folder of our project.</p>
-<ul>
-<li>Add the URL of the code repository as a “Related Resources”</li>
-<li>Add a one-line description of the code under the “Abstract”
-section</li>
-<li>Add at least two key words under the “Keywords” section</li>
-</ul>
+<p>Further information is available from the <a href="https://book.the-turing-way.org/communication/citable/citable-cff.html" class="external-link">Turing
+Way’s guide to software citation</a>.</p>
 </div>
 </div>
 </div>
-<div id="accordionSolution4" class="accordion challenge-accordion accordion-flush">
-<div class="accordion-item">
-<button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution4" aria-expanded="false" aria-controls="collapseSolution4">
-  <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
-</button>
-<div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
-<div class="accordion-body">
-<p>Use <a href="https://citation-file-format.github.io/cff-initializer-javascript/#/version-specific" class="external-link">cffinit</a>,
-a web application to create your citation file using a series of online
-forms.</p>
-<div class="codewrapper sourceCode" id="cb10">
-<h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
-<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb10-3"><a href="#cb10-3" tabindex="-1"></a></span>
-<span id="cb10-4"><a href="#cb10-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb10-5"><a href="#cb10-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
-<span id="cb10-6"><a href="#cb10-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-7"><a href="#cb10-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb10-8"><a href="#cb10-8" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb10-9"><a href="#cb10-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb10-10"><a href="#cb10-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb10-11"><a href="#cb10-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
-<span id="cb10-12"><a href="#cb10-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
-<span id="cb10-13"><a href="#cb10-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
-<span id="cb10-14"><a href="#cb10-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
-<span id="cb10-15"><a href="#cb10-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
-<span id="cb10-16"><a href="#cb10-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
-<span id="cb10-17"><a href="#cb10-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-18"><a href="#cb10-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
-<span id="cb10-19"><a href="#cb10-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb10-20"><a href="#cb10-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
-<span id="cb10-21"><a href="#cb10-21" tabindex="-1"></a>  data</span>
-<span id="cb10-22"><a href="#cb10-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
-<span id="cb10-23"><a href="#cb10-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
-<span id="cb10-24"><a href="#cb10-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span></code></pre>
-</div>
+<div id="spacewalks-software-citation" class="callout discussion">
+<div class="callout-square">
+<i class="callout-icon" data-feather="message-circle"></i>
 </div>
+<div id="spacewalks-software-citation" class="callout-inner">
+<h3 class="callout-title">Spacewalks software citation</h3>
+<div class="callout-content">
+<p>Add the citation file for our Spacewalks software to the root folder
+of our repository on GitHub. You can either do it directly on GitHub or
+creating the file locally and the committing and pushing to GitHub from
+the command line.</p>
 </div>
 </div>
 </div>
@@ -6699,16 +6698,15 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 <hr class="half-width">
 <p>Once our project reaches a certain size or level of complexity we may
 want to add additional documentation such as a standalone tutorial or
-“Background” explaining our methodological choices.</p>
+“background” explaining our methodological choices.</p>
 <p>Once we move beyond using a README as our primary source of
 documentation, we need to consider how we will distribute our
-documentation to our users.</p>
-<p>Options include:</p>
+documentation to our users. Options include:</p>
 <ul>
-<li>A <code>docs/</code> folder of Markdown files.</li>
-<li>Adding a Wiki to our repository.</li>
+<li>A <code>docs/</code> folder of Markdown files</li>
+<li>Adding a Wiki to our repository</li>
 <li>Creating a set of web pages for our documentation using a static
-site generator for our documentation such as Sphinx or MkDocs</li>
+site generator for our documentation such as Sphinx or MkDocs.</li>
 </ul>
 <p>Creating a static site is a popular solution as it has the key
 benefit being able to automatically generate a reference manual from any
@@ -6717,25 +6715,19 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 id="mkdocs">MkDocs<a class="anchor" aria-label="anchor" href="#mkdocs"></a>
 </h3>
 <p>Let’s setup the static documentation site generator tool MkDocs.</p>
-<div class="codewrapper sourceCode" id="cb11">
-<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
-</h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install mkdocs</span>
-<span id="cb11-2"><a href="#cb11-2" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install <span class="st">"mkdocstrings[python]"</span></span>
-<span id="cb11-3"><a href="#cb11-3" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip install mkdocs-material</span></code></pre>
-</div>
-<p>Let’s check that MkDocs has been setup correctly:</p>
-<div class="codewrapper sourceCode" id="cb12">
+<div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="ex">python</span> <span class="at">-m</span> pip list</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb9-1"><a href="#cb9-1" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install mkdocs</span>
+<span id="cb9-2"><a href="#cb9-2" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install <span class="st">"mkdocstrings[python]"</span></span>
+<span id="cb9-3"><a href="#cb9-3" tabindex="-1"></a><span class="ex">python3</span> <span class="at">-m</span> pip install mkdocs-material</span></code></pre>
 </div>
-<p>Let’s creates a new MkDocs project in the current directory</p>
-<div class="codewrapper sourceCode" id="cb13">
+<p>Let’s creates a new MkDocs project in the current directory:</p>
+<div class="codewrapper sourceCode" id="cb10">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="co"># In ~/Desktop/spacewalks</span></span>
-<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a><span class="ex">mkdocs</span> new .    </span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb10-1"><a href="#cb10-1" tabindex="-1"></a><span class="co"># In ~/Desktop/spacewalks</span></span>
+<span id="cb10-2"><a href="#cb10-2" tabindex="-1"></a><span class="ex">mkdocs</span> new .    </span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6745,72 +6737,76 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 </div>
 <p>This command creates a new MkDocs project in the current directory
 with a <code>docs</code> folder containing an <code>index.md</code> file
-and a <code>mkdocs.yml</code> configuration file.</p>
-<p>Now, let’s fill in the configuration file for our project.</p>
-<div class="codewrapper sourceCode" id="cb15">
+and a <code>mkdocs.yml</code> configuration file in the root of our
+project.</p>
+<p>Now, let’s fill in the <code>mkdocs.yml</code> configuration file for
+our project.</p>
+<div class="codewrapper sourceCode" id="cb12">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
-<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a></span>
-<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
-<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
-<span id="cb15-5"><a href="#cb15-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
-<span id="cb15-6"><a href="#cb15-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
-<span id="cb15-7"><a href="#cb15-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
-<span id="cb15-8"><a href="#cb15-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
-<span id="cb15-9"><a href="#cb15-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
-<span id="cb15-10"><a href="#cb15-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
-<span id="cb15-11"><a href="#cb15-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span></code></pre>
-</div>
-<p>Note font-false is for GDPR compliance.</p>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb12-1"><a href="#cb12-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
+<span id="cb12-2"><a href="#cb12-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb12-3"><a href="#cb12-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
+<span id="cb12-4"><a href="#cb12-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
+<span id="cb12-5"><a href="#cb12-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb12-6"><a href="#cb12-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
+<span id="cb12-7"><a href="#cb12-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
+<span id="cb12-8"><a href="#cb12-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
+<span id="cb12-9"><a href="#cb12-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
+<span id="cb12-10"><a href="#cb12-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
+<span id="cb12-11"><a href="#cb12-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span></code></pre>
+</div>
+<p>Note <code>font: false</code> variable is for GDPR compliance;
+<code>use_directory_url: false</code> variable tells MKDocs tools how to
+handle URLs for documentation that is served as a website (we will cover
+this in a moment).</p>
 <p>Let’s add support for <code>mkdocstrings</code> - this will allow us
 to automatically our docstrings into our documentation using a simple
 tag.</p>
-<div class="codewrapper sourceCode" id="cb16">
+<div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
-<span id="cb16-2"><a href="#cb16-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
-<span id="cb16-3"><a href="#cb16-3" tabindex="-1"></a></span>
-<span id="cb16-4"><a href="#cb16-4" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
-<span id="cb16-5"><a href="#cb16-5" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
-<span id="cb16-6"><a href="#cb16-6" tabindex="-1"></a></span>
-<span id="cb16-7"><a href="#cb16-7" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
-<span id="cb16-8"><a href="#cb16-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
-<span id="cb16-9"><a href="#cb16-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
-<span id="cb16-10"><a href="#cb16-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
-<span id="cb16-11"><a href="#cb16-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
-<span id="cb16-12"><a href="#cb16-12" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span>
-<span id="cb16-13"><a href="#cb16-13" tabindex="-1"></a></span>
-<span id="cb16-14"><a href="#cb16-14" tabindex="-1"></a><span class="fu">plugins</span><span class="kw">:</span></span>
-<span id="cb16-15"><a href="#cb16-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> mkdocstrings</span></span></code></pre>
+<pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">site_name</span><span class="kw">:</span><span class="at"> Spacewalks Documentation</span></span>
+<span id="cb13-2"><a href="#cb13-2" tabindex="-1"></a><span class="fu">use_directory_urls</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb13-3"><a href="#cb13-3" tabindex="-1"></a><span class="fu">theme</span><span class="kw">:</span></span>
+<span id="cb13-4"><a href="#cb13-4" tabindex="-1"></a><span class="at">  </span><span class="fu">name</span><span class="kw">:</span><span class="at"> </span><span class="st">"material"</span></span>
+<span id="cb13-5"><a href="#cb13-5" tabindex="-1"></a><span class="fu">font</span><span class="kw">:</span><span class="at"> </span><span class="ch">false</span></span>
+<span id="cb13-6"><a href="#cb13-6" tabindex="-1"></a><span class="fu">nav</span><span class="kw">:</span></span>
+<span id="cb13-7"><a href="#cb13-7" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Spacewalks Documentation</span><span class="kw">:</span><span class="at"> index.md</span></span>
+<span id="cb13-8"><a href="#cb13-8" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Tutorials</span><span class="kw">:</span><span class="at"> tutorials.md</span></span>
+<span id="cb13-9"><a href="#cb13-9" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">How-To Guides</span><span class="kw">:</span><span class="at"> how-to-guides.md</span></span>
+<span id="cb13-10"><a href="#cb13-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Reference</span><span class="kw">:</span><span class="at"> reference.md</span></span>
+<span id="cb13-11"><a href="#cb13-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">Background</span><span class="kw">:</span><span class="at"> explanation.md</span></span>
+<span id="cb13-12"><a href="#cb13-12" tabindex="-1"></a></span>
+<span id="cb13-13"><a href="#cb13-13" tabindex="-1"></a><span class="fu">plugins</span><span class="kw">:</span></span>
+<span id="cb13-14"><a href="#cb13-14" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> mkdocstrings</span></span></code></pre>
 </div>
 <p>Let’s populate our <code>docs/</code> folder to match our
 configuration file.</p>
-<div class="codewrapper sourceCode" id="cb17">
+<div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="fu">touch</span> docs/tutorials.md</span>
-<span id="cb17-2"><a href="#cb17-2" tabindex="-1"></a><span class="fu">touch</span> docs/how-to-guides.md</span>
-<span id="cb17-3"><a href="#cb17-3" tabindex="-1"></a><span class="fu">touch</span> docs/reference.md</span>
-<span id="cb17-4"><a href="#cb17-4" tabindex="-1"></a><span class="fu">touch</span> docs/explanation.md</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/tutorials.md</span>
+<span id="cb14-2"><a href="#cb14-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/how-to-guides.md</span>
+<span id="cb14-3"><a href="#cb14-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/reference.md</span>
+<span id="cb14-4"><a href="#cb14-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> touch docs/explanation.md</span></code></pre>
 </div>
-<p>Let’s populate our reference file with some preamble to include
-before the reference manual that will be generated from the docstrings
-we created.</p>
-<div class="codewrapper sourceCode" id="cb18">
+<p>Let’s populate our reference file <code>reference.md</code> with some
+preamble to include before the reference manual that will be generated
+from the docstrings we created.</p>
+<div class="codewrapper sourceCode" id="cb15">
 <h3 class="code-label">MARKDOWN<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode markdown" tabindex="0"><code class="sourceCode markdown"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a>This file documents the key functions in the Spacewalks tool.</span>
-<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a>It is provided as a reference manual.</span>
-<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a></span>
-<span id="cb18-4"><a href="#cb18-4" tabindex="-1"></a>::: eva_data_analysis</span></code></pre>
+<pre class="sourceCode markdown" tabindex="0"><code class="sourceCode markdown"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a>This file documents the key functions in the Spacewalks tool.</span>
+<span id="cb15-2"><a href="#cb15-2" tabindex="-1"></a>It is provided as a reference manual.</span>
+<span id="cb15-3"><a href="#cb15-3" tabindex="-1"></a></span>
+<span id="cb15-4"><a href="#cb15-4" tabindex="-1"></a>::: eva_data_analysis</span></code></pre>
 </div>
 <p>Finally, let’s build our documentation.</p>
-<div class="codewrapper sourceCode" id="cb19">
+<div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="ex">mkdocs</span> build</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs build</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6823,25 +6819,43 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 INFO    -  Documentation built in 0.31 seconds</code></pre>
 </div>
 <p>Once the build step is completed, our documentation site is saved to
-a <code>site</code> folder in the root of our project folder.</p>
-<p>These files will be distributed with our code. We can either direct
-users to read these files locally on their own device using their
-browser, or we can choose to host our documentation as a website that
-our uses can navigate to.</p>
+a <code>site</code> folder in the root of our project folder. These
+files will be distributed with our code. We can either direct users to
+read these files locally on their own device using their browser, or we
+can choose to host our documentation as a website that our uses can
+navigate to.</p>
 <p>Note that we used the setting <code>use_directory_urls: false</code>
 in the <code>mkdocs.yml</code> file. This setting ensures that the
 documentation site is generated with URLs that are easy to navigate
 locally on a user’s device.</p>
-<p>Finally let us commit our documentation to the main branch of our git
-repository and push the changes to GitHub</p>
-<div class="codewrapper sourceCode" id="cb21">
+<div id="explore-your-documentation" class="callout discussion">
+<div class="callout-square">
+<i class="callout-icon" data-feather="message-circle"></i>
+</div>
+<div id="explore-your-documentation" class="callout-inner">
+<h3 class="callout-title">Explore your documentation</h3>
+<div class="callout-content">
+<p>Explore documentation in <code>site/</code> folder built with MkDocs
+for your project, starting from <code>index.html</code> file.</p>
+<p>For example, check <code>site/reference.html</code> to see how
+docstrings from your functions are provided here as a reference
+manual.</p>
+</div>
+</div>
+</div>
+<p>Finally, let us commit our documentation to the main branch of our
+git repository and push the changes to GitHub.</p>
+<div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb21-1"><a href="#cb21-1" tabindex="-1"></a><span class="fu">git</span> add mkdocs.yml </span>
-<span id="cb21-2"><a href="#cb21-2" tabindex="-1"></a><span class="fu">git</span> add docs/</span>
-<span id="cb21-3"><a href="#cb21-3" tabindex="-1"></a><span class="fu">git</span> add site/</span>
-<span id="cb21-4"><a href="#cb21-4" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
-<span id="cb21-5"><a href="#cb21-5" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add mkdocs.yml </span>
+<span id="cb18-2"><a href="#cb18-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add docs/</span>
+<span id="cb18-3"><a href="#cb18-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add site/</span>
+<span id="cb18-4"><a href="#cb18-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
+<span id="cb18-5"><a href="#cb18-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 <span class="at">-m</span> pip freeze <span class="op">&gt;</span> requirements.txt</span>
+<span id="cb18-6"><a href="#cb18-6" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add requirements.txt </span>
+<span id="cb18-7"><a href="#cb18-7" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Added mkdocs plugin"</span></span>
+<span id="cb18-8"><a href="#cb18-8" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 <div id="hosting-documentation" class="callout">
 <div class="callout-square">
@@ -6850,9 +6864,8 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div id="hosting-documentation" class="callout-inner">
 <h3 class="callout-title">Hosting documentation</h3>
 <div class="callout-content">
-<p>In the previous section, we saw how Mkdocs documentation can be
-distributed with our repository and viewed “offline” using a
-browser.</p>
+<p>We saw how MkDocs documentation can be distributed with our
+repository and viewed “offline” using a browser.</p>
 <p>We can also make our documentation available as a live website by
 deploying our documentation to a hosting service.</p>
 <div id="accordionSpoiler1" class="accordion spoiler-accordion accordion-flush">
@@ -6871,10 +6884,11 @@ <h3 id="github-pages">GitHub Pages<a class="anchor" aria-label="anchor" href="#g
 <p>There are two types of GitHub Pages: project pages and
 user/organization Pages. While similar, they have different deployment
 workflows, and we will only discuss project pages here. For information
-about deploying to user/organisational pages, see [MkDocs Deployment
-pages][mkdocs-deploy].</p>
-<p>Project Pages deploy site files to a branch within the project
-repository (default is gh-pages). To deploy our documentation:</p>
+about deploying to user/organisational pages, see <a href="https://www.mkdocs.org/user-guide/deploying-your-docs/" class="external-link">MkDocs
+Deployment pages</a>.</p>
+<p>Project Pages deploy site files to a branch (by default the
+<code>gh-pages</code> branch, but it can be any other branch) within the
+project repository. To deploy our documentation:</p>
 <blockquote>
 <p><strong>Warning!</strong> Before we proceed to the next step, we MUST
 ensure that there are no uncommitted changes or untracked files in our
@@ -6884,28 +6898,29 @@ <h3 id="github-pages">GitHub Pages<a class="anchor" aria-label="anchor" href="#g
 </blockquote>
 <ol style="list-style-type: decimal">
 <li>(If not done already), let us commit our documentation to the main
-branch of our git repository and push the changes to GitHub</li>
+branch of our git repository and push the changes to GitHub.</li>
 </ol>
-<div class="codewrapper sourceCode" id="cb22">
+<div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="fu">git</span> add mkdocs.yml </span>
-<span id="cb22-2"><a href="#cb22-2" tabindex="-1"></a><span class="fu">git</span> add docs/</span>
-<span id="cb22-3"><a href="#cb22-3" tabindex="-1"></a><span class="fu">git</span> add site/</span>
-<span id="cb22-4"><a href="#cb22-4" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
-<span id="cb22-5"><a href="#cb22-5" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add mkdocs.yml </span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add docs/</span>
+<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add site/</span>
+<span id="cb19-4"><a href="#cb19-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Add project-level documentation"</span></span>
+<span id="cb19-5"><a href="#cb19-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 <ol start="2" style="list-style-type: decimal">
 <li>Once we are on the main branch and all our changes are up to date,
-run the following command to deploy our documentation to GitHub.</li>
+run the following command from the command line termindal to deploy our
+documentation to GitHub.</li>
 </ol>
-<div class="codewrapper sourceCode" id="cb23">
+<div class="codewrapper sourceCode" id="cb20">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb23-1"><a href="#cb23-1" tabindex="-1"></a><span class="co"># Important: </span></span>
-<span id="cb23-2"><a href="#cb23-2" tabindex="-1"></a><span class="co"># - This command will push the documentation to the gh-pages branch of your repository</span></span>
-<span id="cb23-3"><a href="#cb23-3" tabindex="-1"></a><span class="co"># - It will ALSO include uncommitted changes and untracked files (read the warning above!!) &lt;- VERY IMPORTANT!!</span></span>
-<span id="cb23-4"><a href="#cb23-4" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb20-1"><a href="#cb20-1" tabindex="-1"></a><span class="co"># Important: </span></span>
+<span id="cb20-2"><a href="#cb20-2" tabindex="-1"></a><span class="co"># - This command will push the documentation to the gh-pages branch of your repository</span></span>
+<span id="cb20-3"><a href="#cb20-3" tabindex="-1"></a><span class="co"># - It will ALSO include uncommitted changes and untracked files (read the warning above!!) &lt;- VERY IMPORTANT!!</span></span>
+<span id="cb20-4"><a href="#cb20-4" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs gh-deploy</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -6935,13 +6950,14 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 INFO    -  Your documentation should shortly be available at: https://kkh451.github.io/spacewalks/</code></pre>
 </div>
 <p>This command will build our documentation with MkDocs, then commit
-and push the files to the gh-pages branch using the GitHub ghp-import
-tool which is installed as a dependency of MkDocs.</p>
+and push the files to the <code>gh-pages</code> branch using the GitHub
+<code>ghp-import</code> tool which is installed as a dependency of
+MkDocs.</p>
 <p>For more options, use:</p>
-<div class="codewrapper sourceCode" id="cb25">
+<div class="codewrapper sourceCode" id="cb22">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy <span class="at">--help</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb22-1"><a href="#cb22-1" tabindex="-1"></a><span class="ex">mkdocs</span> gh-deploy <span class="at">--help</span></span></code></pre>
 </div>
 <p>Notice that the deploy command did not allow us to preview the site
 before it was pushed to GitHub; so, it is a good idea to check changes
@@ -6951,8 +6967,8 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 id="other-options">Other options<a class="anchor" aria-label="anchor" href="#other-options"></a>
 </h3>
 <p>You can find out about other deployment options including free
-documentation hosting service ReadTheDocs on the [MkDocs deployment
-pages][mkdocs-deploy].</p>
+documentation hosting service ReadTheDocs on the <a href="https://www.mkdocs.org/user-guide/deploying-your-docs/" class="external-link">MkDocs
+deployment pages</a>.</p>
 </div>
 </div>
 </div>
@@ -6966,8 +6982,8 @@ <h3 id="other-options">Other options<a class="anchor" aria-label="anchor" href="
 </h2>
 <hr class="half-width">
 <p>Once we start to consider other forms of documentation beyond the
-README, we can also increase the re-usability of our code by ensuring
-that the content and style of our documentation matches its purpose.</p>
+README, we can also increase reusability of our code by ensuring that
+the content and style of our documentation matches its purpose.</p>
 <p>Documentation guides such as <a href="https://www.writethedocs.org/" class="external-link">Write the Docs</a>, <a href="https://www.thegooddocsproject.dev/" class="external-link">The Good Docs Project</a> and
 the <a href="https://diataxis.fr/" class="external-link">Diataxis framework</a> provide a
 range of resources including documentation templates to help to help us
@@ -6983,8 +6999,9 @@ <h3 class="callout-title">Spacewalks how-to guide</h3>
 <li><p>Review the Diataxis guidance page on writing a How-to guide.
 Identify three features of an effective how-to guide.</p></li>
 <li><p>Following the Diataxis guidelines, add a how-to guide to the
-<code>docs</code> folder that show users how to change the destination
-filename for the output dataset generated by Spacewalks.</p></li>
+<code>docs/how-to-guides.md</code> file in your documentation folder to
+show users how to change the destination filename for the output CSV
+dataset generated by the Spacewalks software.</p></li>
 </ol>
 <div id="accordionSpoiler2" class="accordion spoiler-accordion accordion-flush">
 <div class="accordion-item">
@@ -7000,21 +7017,30 @@ <h3 class="accordion-header" id="headingSpoiler2">  <div class="note-square"><i
 <li>use appropriate language e.g. conditional imperatives</li>
 <li>have an informative title</li>
 </ul>
-<p>An example how-to guide:</p>
+<p>An example how-to guide for our project to the file
+<code>docs/how-to-guides.md</code>:</p>
 <pre><code># How to change the file path of Spacewalk's output dataset
 
 This guide shows you how to set the file path for Spacewalk's output
 data set to a location of your choice.
 
-By default, the cleaned data set generated by Spacewalk is saved to the current
-working directory with file name `eva-data.csv`.
+By default, the cleaned data set in CSV format, generated by the Spacewalk software, is saved to the `results/`
+folder within the working directory with file name `eva-data.csv`.
 
 If you would like to modify the name or location of the output dataset, set the
 second command line argument to your chosen file path.
+For example, if you want to save the output data set to the subfolder `data/clean/` you can
+invoke the script as:
 
-`python eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv`
+`(venv_spacewalks) $ python3 eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv`
 
-The specified destination folder must exist before running spacewalks analysis script.</code></pre>
+The specified destination folder `data/clean/` must exist before running spacewalks analysis script.</code></pre>
+<p>Remember to rebuild your documentation:</p>
+<div class="codewrapper sourceCode" id="cb24">
+<h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
+</h3>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb24-1"><a href="#cb24-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdocs build</span></code></pre>
+</div>
 </div>
 </div>
 </div>
@@ -7048,8 +7074,9 @@ <h3 class="accordion-header" id="headingSpoiler3">  <div class="note-square"><i
 <h4 id="introduction">Introduction<a class="anchor" aria-label="anchor" href="#introduction"></a>
 </h4>
 <p>In this tutorial, we will learn how to change the file path for the
-output dataset generated by Spacewalk. By the end of this tutorial, you
-will be able to specify a custom file path for the cleaned dataset.</p>
+output dataset generated by the Spacewalk software. By the end of this
+tutorial, you will be able to specify a custom file path for the cleaned
+dataset.</p>
 </div>
 <div class="section level4">
 <h4 id="prerequisites">Prerequisites<a class="anchor" aria-label="anchor" href="#prerequisites"></a>
@@ -7064,35 +7091,36 @@ <h4 id="prerequisites">Prerequisites<a class="anchor" aria-label="anchor" href="
 <div class="section level4">
 <h4 id="prepare-the-destination-directory">Prepare the destination directory<a class="anchor" aria-label="anchor" href="#prepare-the-destination-directory"></a>
 </h4>
-<p>First, let us decide where we want to save the cleaned dataset. and
+<p>First, let us decide where we want to save the cleaned dataset and
 make sure the directory exists.</p>
-<p>For this tutorial, we will use data/clean as the destination
-folder.</p>
-<p>Let’s create the directory if it does not exist:</p>
-<div class="codewrapper sourceCode" id="cb27">
+<p>For this tutorial, we will use <code>data/clean/</code> as the
+destination folder.</p>
+<p>Let’s create the directory if it does not exist - e.g. from the
+command line do:</p>
+<div class="codewrapper sourceCode" id="cb25">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="fu">mkdir</span> <span class="at">-p</span> data/clean</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb25-1"><a href="#cb25-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir <span class="at">-p</span> data/clean</span></code></pre>
 </div>
 </div>
 <div class="section level4">
-<h4 id="run-the-analysis-script-with-custom-path">Run the analysis script with custom path<a class="anchor" aria-label="anchor" href="#run-the-analysis-script-with-custom-path"></a>
+<h4 id="run-the-analysis-script-with-a-custom-path">Run the analysis script with a custom path<a class="anchor" aria-label="anchor" href="#run-the-analysis-script-with-a-custom-path"></a>
 </h4>
 <p>Next, execute the Spacewalk script and specify the custom file path
 for the output dataset:</p>
-<div class="codewrapper sourceCode" id="cb28">
+<div class="codewrapper sourceCode" id="cb26">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb28-1"><a href="#cb28-1" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py <span class="op">&lt;</span>input-file<span class="op">&gt;</span> <span class="op">&lt;</span>output-file<span class="op">&gt;</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb26-1"><a href="#cb26-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py <span class="op">&lt;</span>input-file<span class="op">&gt;</span> <span class="op">&lt;</span>output-file<span class="op">&gt;</span></span></code></pre>
 </div>
-<p>Replace <input-file> with your input dataset (eva-data.json) and
-<output-file> with your desired output path
-(data/clean/eva-data-clean.csv).</output-file></input-file></p>
+<p>Replace <input-file> with your input dataset
+(<code>data/eva-data.json</code>) and <output-file> with your desired
+output path (<code>data/clean/eva-data-clean.csv</code>).</output-file></input-file></p>
 <p>Here is the complete command:</p>
-<div class="codewrapper sourceCode" id="cb29">
+<div class="codewrapper sourceCode" id="cb27">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py eva-data.json data/clean/eva-data-clean.csv</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb27-1"><a href="#cb27-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py data/eva-data.json data/clean/eva-data-clean.csv</span></code></pre>
 </div>
 <p>Notice how the output to the command line clearly indicates that we
 are using a custom output file path.</p>
@@ -7100,48 +7128,49 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="output" tabindex="0"><code>Using custom input and output filenames
-Reading JSON file eva-data.json
+Reading JSON file data/eva-data.json
 Saving to CSV file data/clean/eva-data-clean.csv
 Adding crew size variable (crew_size) to dataset
 Saving to CSV file data/clean/eva-data-clean.csv
-Plotting cumulative spacewalk duration and saving to ./cumulative_eva_graph.png</code></pre>
+Plotting cumulative spacewalk duration and saving to results/cumulative_eva_graph.png</code></pre>
 </div>
-<p>After running the script, let us check the data/clean directory to
-ensure the cleaned dataset has been saved correctly.</p>
-<div class="codewrapper sourceCode" id="cb31">
+<p>After running the script, let us check the <code>data/clean</code>
+directory to ensure the cleaned dataset has been saved correctly.</p>
+<div class="codewrapper sourceCode" id="cb29">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" tabindex="-1"></a><span class="fu">ls</span> data/clean</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb29-1"><a href="#cb29-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> ls data/clean</span></code></pre>
 </div>
-<p>You should see eva-data-clean.csv listed in the data/clean folder</p>
+<p>You should see <code>eva-data-clean.csv</code> file listed in the
+<code>data/clean</code> folder.</p>
 </div>
 <div class="section level4">
 <h4 id="exercise-custom-output-path">Exercise: custom output path<a class="anchor" aria-label="anchor" href="#exercise-custom-output-path"></a>
 </h4>
 <ul>
-<li>Create a new directory named output/data in your working
-directory.</li>
+<li>Create a new directory named <code>output/data</code> in your
+working directory.</li>
 <li>Run the Spacewalk script to save the cleaned dataset in the newly
-created output/data directory with the filename
-cleaned-eva-data.csv.</li>
+created <code>output/data</code> directory with the filename
+<code>cleaned-eva-data.csv</code>.</li>
 <li>Verify that the dataset has been saved correctly.</li>
 </ul>
 <div class="section level5">
 <h5 id="solution-1">Solution<a class="anchor" aria-label="anchor" href="#solution-1"></a>
 </h5>
-<div class="codewrapper sourceCode" id="cb32">
+<div class="codewrapper sourceCode" id="cb30">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb32-1"><a href="#cb32-1" tabindex="-1"></a><span class="co"># Create the directory:</span></span>
-<span id="cb32-2"><a href="#cb32-2" tabindex="-1"></a><span class="fu">mkdir</span> <span class="at">-p</span> output/data</span>
-<span id="cb32-3"><a href="#cb32-3" tabindex="-1"></a></span>
-<span id="cb32-4"><a href="#cb32-4" tabindex="-1"></a><span class="co"># Run the script:</span></span>
-<span id="cb32-5"><a href="#cb32-5" tabindex="-1"></a><span class="ex">python</span> eva_data_analysis.py eva-data.json output/data/cleaned-eva-data.csv</span>
-<span id="cb32-6"><a href="#cb32-6" tabindex="-1"></a></span>
-<span id="cb32-7"><a href="#cb32-7" tabindex="-1"></a><span class="co"># Verify the output:</span></span>
-<span id="cb32-8"><a href="#cb32-8" tabindex="-1"></a><span class="fu">ls</span> output/data</span>
-<span id="cb32-9"><a href="#cb32-9" tabindex="-1"></a></span>
-<span id="cb32-10"><a href="#cb32-10" tabindex="-1"></a><span class="co"># You should see cleaned-eva-data.csv listed</span></span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb30-1"><a href="#cb30-1" tabindex="-1"></a><span class="co"># Create the directory:</span></span>
+<span id="cb30-2"><a href="#cb30-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> mkdir <span class="at">-p</span> output/data</span>
+<span id="cb30-3"><a href="#cb30-3" tabindex="-1"></a></span>
+<span id="cb30-4"><a href="#cb30-4" tabindex="-1"></a><span class="co"># Run the script:</span></span>
+<span id="cb30-5"><a href="#cb30-5" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> python3 eva_data_analysis.py data/eva-data.json output/data/cleaned-eva-data.csv</span>
+<span id="cb30-6"><a href="#cb30-6" tabindex="-1"></a></span>
+<span id="cb30-7"><a href="#cb30-7" tabindex="-1"></a><span class="co"># Verify the output:</span></span>
+<span id="cb30-8"><a href="#cb30-8" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> ls output/data</span>
+<span id="cb30-9"><a href="#cb30-9" tabindex="-1"></a></span>
+<span id="cb30-10"><a href="#cb30-10" tabindex="-1"></a><span class="co"># You should see cleaned-eva-data.csv listed</span></span></code></pre>
 </div>
 <p>Congratulations! You have successfully changed the file path for
 Spacewalks output dataset and completed an exercise to practice the
@@ -7202,24 +7231,14 @@ <h4 id="language">Language<a class="anchor" aria-label="anchor" href="#language"
 </div>
 </div>
 </div>
-<div id="commit-and-push-your-changes" class="callout">
-<div class="callout-square">
-<i class="callout-icon" data-feather="bell"></i>
-</div>
-<div id="commit-and-push-your-changes" class="callout-inner">
-<h3 class="callout-title">Commit and push your changes</h3>
-<div class="callout-content">
-<p>Do not forget to commit any uncommited changes you may have and then
+<p>Do not forget to commit any uncommitted changes you may have and then
 push your work to GitHub.</p>
-<div class="codewrapper sourceCode" id="cb33">
+<div class="codewrapper sourceCode" id="cb31">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb33-1"><a href="#cb33-1" tabindex="-1"></a><span class="fu">git</span> add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
-<span id="cb33-2"><a href="#cb33-2" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
-<span id="cb33-3"><a href="#cb33-3" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
-</div>
-</div>
-</div>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb31-1"><a href="#cb31-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
+<span id="cb31-2"><a href="#cb31-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
+<span id="cb31-3"><a href="#cb31-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 </section><section><h2 class="section-heading" id="further-reading">Further reading<a class="anchor" aria-label="anchor" href="#further-reading"></a>
 </h2>
@@ -7277,9 +7296,9 @@ <h3 class="callout-title">Key Points</h3>
 Place links that you need to refer to multiple times across pages here. Delete
 any links that you are not going to use.
  -->
-</section></section><section id="aio-10-open-collaboration"><p>Content from <a href="10-open-collaboration.html">Open collaboration on code</a></p>
+</section></section><section id="aio-10-open-collaboration"><p>Content from <a href="10-open-collaboration.html">Open code &amp; collaboration</a></p>
 <hr>
-<p>Last updated on 2024-09-24 |
+<p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/10-open-collaboration.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time: <i aria-hidden="true" data-feather="clock"></i> 90 minutes</p>
@@ -7322,9 +7341,16 @@ <h3 class="card-title">Objectives</h3>
 </div>
 </div>
 </div>
-<p>In addition to adding a license and other metadata to our code
-(covered in previous episode) there are several other important steps to
-consider before sharing the code publicly.</p>
+<p>Sharing code openly promotes collaboration, transparency, and
+innovation by allowing others to review, use, and improve the code. It
+fosters knowledge exchange, accelerates scientific progress, and
+enhances the reproducibility of research. Additionally, open sharing
+encourages community contributions and can lead to better-maintained,
+more reliable software.</p>
+<p>Adding a <a href="licensing.html">license</a> and other metadata to
+our code (covered in the previous episode) are the first steps towards
+sharing the code publicly. There are several other important steps to
+consider which we will cover here.</p>
 <div id="activate-your-virtual-environment" class="callout">
 <div class="callout-square">
 <i class="callout-icon" data-feather="bell"></i>
@@ -7344,92 +7370,106 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 </div>
 </div>
 </div>
+<div id="accordionInstructor1" class="accordion instructor-note accordion-flush">
+<div class="accordion-item">
+<button class="accordion-button instructor-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseInstructor1" aria-expanded="false" aria-controls="collapseInstructor1">
+  <h3 class="accordion-header" id="headingInstructor1">  <div class="note-square"><i aria-hidden="true" class="callout-icon" data-feather="edit-2"></i></div> Instructor Note </h3>
+</button>
+<div id="collapseInstructor1" class="accordion-collapse collapse" aria-labelledby="headingInstructor1" data-bs-parent="#accordionInstructor1">
+<div class="accordion-body">
+<p>At this point, the code in your local software project’s directory
+should be as in: <a href="https://github.com/carpentries-incubator/astronaut-data-analysis-not-so-fair/tree/10-open-collaboration" class="external-link uri">https://github.com/carpentries-incubator/astronaut-data-analysis-not-so-fair/tree/10-open-collaboration</a></p>
+</div>
+</div>
+</div>
+</div>
 <section><h2 class="section-heading" id="sharing-code-to-encourage-collaboration">Sharing code to encourage collaboration<a class="anchor" aria-label="anchor" href="#sharing-code-to-encourage-collaboration"></a>
 </h2>
 <hr class="half-width">
 <div class="section level3">
 <h3 id="making-the-code-public">Making the code public<a class="anchor" aria-label="anchor" href="#making-the-code-public"></a>
 </h3>
-<p>By default repositories created on Github are private and only their
-creator can see them. If we’re going to be adding an open source license
-to our repository we probably want to make sure people can actually
-access it too!</p>
-<p>Go to the Github webpage of your repository
-(<code>https://github.com/&lt;yourusername&gt;/&lt;yourrepsoitoryname&gt;</code>)
-and click on the Settings link near the top right corner. Then scroll
-down to the bottom of the page and the “Danger Zone” settings. Click on
-“Change Visibility” and you should see a message saying “Change to
-public”, if it says “Change to private” then the repository is already
-public. You’ll then be asked to confirm that you want to make the
-repository public and agree to the warning that the code will now be
-publicly visible. As a security measure you’ll then have to put in your
-Github password.</p>
+<p>By default repositories created on GitHub are private and only their
+creator can see them. Since we added an open source license to our
+repository we probably want to make sure people can actually access
+it.</p>
+<p>To make your repository public, if it is not already, go to your
+repository on GitHub and click on the <code>Settings</code> link near
+the top right corner. Then scroll down to the bottom of the page and the
+“Danger Zone” settings. Click on “Change Visibility” and you should see
+a message saying “Change to public”. If it says “Change to private” then
+the repository is already public. You will then be asked to confirm that
+you indeed want to make the repository public and agree to the warning
+that the code will now be publicly visible. As a security measure, you
+will then have to put in your GitHub password.</p>
 </div>
 <div class="section level3">
 <h3 id="transferring-to-an-organisation">Transferring to an organisation<a class="anchor" aria-label="anchor" href="#transferring-to-an-organisation"></a>
 </h3>
-<p>Currently our repository is under the Github “namespace” of our
-individual user. This is ok for individual projects where we are the
-sole or at least main author, but for bigger and more complex projects
-it is common to use a Github organisation named after our project. If we
-are a member of an organisation and have the appropriate permissions
-then we can transfer a repository from our personal namespace to the
-organisation’s. This can be done with another option in the “Danger
-Zone” settings, the “Transfer ownership” button. Pressing this will then
-prompt us as to which organisation we want to transfer the repository
-to.</p>
+<p>Currently our repository is under the GitHub “namespace” of our
+individual user. This is OK for individual projects where we are the
+sole or at least the main code author, but for bigger and more complex
+projects it is common to use a GitHub organisation named after our
+project. If we are a member of an organisation and have the appropriate
+permissions then we can transfer a repository from our personal
+namespace to the organisation’s. This can be done with another option in
+the “Danger Zone” settings, the “Transfer ownership” button. Pressing
+this will then prompt us as to which organisation we want to transfer
+the repository to.</p>
 </div>
 <div class="section level3">
-<h3 id="archiving-to-zenodo-and-obtaining-a-doi">Archiving to Zenodo and obtaining a DOI<a class="anchor" aria-label="anchor" href="#archiving-to-zenodo-and-obtaining-a-doi"></a>
+<h3 id="archiving-code-to-zenodo-and-obtaining-a-doi">Archiving code to Zenodo and obtaining a DOI<a class="anchor" aria-label="anchor" href="#archiving-code-to-zenodo-and-obtaining-a-doi"></a>
 </h3>
-<p>Zenodo is a data archive run by CERN. Anybody can upload datasets up
-to 50GB to it and receive a Digital Object Identifier (DOI). Zenodo’s
-definition of a dataset is quite broad and can include code. This gives
-us a way to obtain a DOI for our code. We can archive our Github
-repository to Zenodo by doing the following:</p>
+<p><a href="https://zenodo.org/" class="external-link">Zenodo</a> is a data archive run by
+CERN. Anybody can upload datasets up to 50GB to it and receive a Digital
+Object Identifier (DOI). Zenodo’s definition of a dataset is quite broad
+and can include code - which gives us a way to obtain a DOI for our
+software. We can archive our GitHub repository to Zenodo by doing the
+following:</p>
 <ol style="list-style-type: decimal">
 <li>Go to the <a href="https://zenodo.org/login" class="external-link">Zenodo Login page</a>
-and choose to login with Github.</li>
-<li>Authorise Zenodo to connect to Github.</li>
-<li>Go to the <a href="https://zenodo.org/account/settings/github/" class="external-link">Github page</a> in
+and choose to login with GitHub.</li>
+<li>Authorise Zenodo to connect to GitHub.</li>
+<li>Go to the <a href="https://zenodo.org/account/settings/github/" class="external-link">GitHub page</a> in
 your Zenodo account. This can be found in the pull down menu with your
 user name in the top right corner of the screen.</li>
-<li>You’ll now have a list of all of your Github repositories. Next to
+<li>You’ll now have a list of all of your GitHub repositories. Next to
 each will be an “On” button. If you have created a new repository you
 might need to press the “Sync” button to update the list of repositories
 Zenodo knows about.</li>
 <li>Press the “On” button for the repository you want to archive. If
-this was successful you’ll be told to refresh the page.</li>
-<li>The repository should now appear in the list of Enabled repositories
-at the top of the screen. But it doesn’t yet have a DOI. To get one we
-have to make a release on Github. Click on the repository and then press
-the green button to create a release. This will take you to Github’s
-release page where you’ll be asked to give a title and description of
-the release. You will also have to create a tag, this is a way of having
-a friendly name for the version of some code in Git instead of using a
-long hash code. Often we’ll create a sequential version number for each
-release of the software and have the tag name match this, for example
-v1.0 or just 1.0.</li>
+this was successful you will be told to refresh the page.</li>
+<li>The repository should now appear in the list of “Enabled”
+repositories at the top of the screen, but it does not yet have a DOI.
+To get one we have to make a “release” on GitHub. Click on the
+repository and then press the green button to create a release. This
+will take you to GitHub’s release page where you will be asked to give a
+title and description of the release. You will also have to create a
+“tag” for your release - a way of having a friendly name for the version
+of some code in Git instead of using a long hash code. Often we will
+create a sequential version number for each release of the software and
+have the tag name match this, for example v1.0 or just 1.0.</li>
 <li>If we now refresh the Zenodo page for this repository we will see
 that it has been assigned a DOI.</li>
 </ol>
-<p>The DOI doesn’t just link to Github, Zenodo will have taken a copy of
-our repository at the point where we tagged the release. This means that
-even if we delete it from Github or even if Github were ever to go away
-or remove it, they’ll still be a copy on Zenodo. Zenodo will allow
-people to download the entire repository as a single Zip file.</p>
+<p>The DOI does not just link to GitHub, Zenodo will have taken a copy
+(a snapshot) of our repository at the point where we tagged the release.
+This means that even if we delete it from GitHub or even if GitHub were
+ever to go away or remove it, there will still be a copy on Zenodo.
+Zenodo will allow people to download the entire repository as a single
+<code>zip</code> file.</p>
 <p>Zenodo will have actually created two DOIs for you. One represents
 the latest version of the software and will always represent the latest
-if you make more releases. The other is specfic to the release you made
+if you make more releases. The other is specific to the release you made
 and will always point to that version. We can see both of these by
-clicking on the DOI link in the Zenodo page for the repository. One of
-the things which is displayed on this page is a badge image that you can
-copy the link for and add to the README file in your Git repository so
-that people can find the Zenodo version of the repository. If you click
-on the DOI image in the Details section of the Zenodo page then you will
-be shown instructions for obtaining a link to the DOI badge in various
-formats including Markdown. Here is the badge for this repository and
-the corresponding Markdown:</p>
+clicking on the DOI link in the Zenodo page for the repository.</p>
+<p>One of the things which is displayed on this page is a badge image
+that you can copy the link for and add to the README file in your GitHub
+repository so that people can find the Zenodo version of the repository.
+If you click on the DOI image in the Details section of the Zenodo page
+then you will be shown instructions for obtaining a link to the DOI
+badge in various formats including Markdown. Here is the badge for this
+repository and the corresponding Markdown:</p>
 <p><a href="https://doi.org/10.5281/zenodo.11869450" class="external-link"><img src="https://zenodo.org/badge/DOI/10.5281/zenodo.11869450.svg" alt="DOI" class="figure"></a></p>
 <pre class="text"><code>[![DOI](https://zenodo.org/badge/DOI/10.5281/zenodo.11869450.svg)](https://doi.org/10.5281/zenodo.11869450)</code></pre>
 <div id="archive-your-repository-to-zenodo" class="callout discussion">
@@ -7439,8 +7479,12 @@ <h3 id="archiving-to-zenodo-and-obtaining-a-doi">Archiving to Zenodo and obtaini
 <div id="archive-your-repository-to-zenodo" class="callout-inner">
 <h3 class="callout-title">Archive your repository to Zenodo</h3>
 <div class="callout-content">
+<p>Note: for this exercise, you should use the <a href="https://sandbox.zenodo.org/" class="external-link">Sandbox Zenodo</a> (which is a
+version of Zenodo for testing and playing with before minting a real
+DOI) to avoid polluting the DOI space with test repositories we use for
+this course.</p>
 <ul>
-<li>Create an account on Zenodo that is linked to your Github
+<li>Create an account on Zenodo that is linked to your GitHub
 account.</li>
 <li>Use Zenodo to create a release for your repository and obtain a DOI
 for it.</li>
@@ -7457,12 +7501,12 @@ <h3 class="callout-title">Archive your repository to Zenodo</h3>
 <i class="callout-icon" data-feather="bell"></i>
 </div>
 <div id="problems-with-github-and-zenodo-integration" class="callout-inner">
-<h3 class="callout-title">Problems with Github and Zenodo integration</h3>
+<h3 class="callout-title">Problems with GitHub and Zenodo integration</h3>
 <div class="callout-content">
-<p>The integration between Github and Zenodo does not interact well with
+<p>The integration between GitHub and Zenodo does not interact well with
 some browser privacy features and extensions. Firefox can be
 particularly problematic with this and might open new tabs to login to
-Github and then give an error saying:
+GitHub and then give an error saying:
 <code>Your browser did something unexpected.  Please try again. If the error continues, try disabling all browser extensions.</code>
 If this happens try disabling the extra privacy features/extensions or
 using another browser such as Chrome.</p>
@@ -7474,35 +7518,49 @@ <h3 class="callout-title">Problems with Github and Zenodo integration</h3>
 <h3 id="adding-a-doi-and-orcid-to-the-citation-file">Adding a DOI and ORCID to the citation file<a class="anchor" aria-label="anchor" href="#adding-a-doi-and-orcid-to-the-citation-file"></a>
 </h3>
 <p>Now that we have our DOI it is good practice to include this
-information in our citation file. In the previous part of this lesson we
-created a <code>CITATION.cff</code> file with information about how to
-cite our code. There are a few fields we can add which are related to
-the DOI, one of these is the <code>version</code> file which covers the
+information in our citation file. Earlier we created a
+<code>CITATION.cff</code> file with information about how to cite our
+code. There are a few fields we can add now which are related to the
+DOI; one of these is the <code>version</code> file which covers the
 version number of the software. We can add a DOI to the file in the
 <code>identifiers</code> section with a type of <code>doi</code> and
-<code>value</code> with the URL. Optionally we can also add a
+<code>value</code> of the Zenodo URL. Optionally we can also add a
 <code>date-released</code> field indicating the date we released this
-software. Here is an updated version of our CITATION.cff from the
-previous episode with a version number, DOI and release date added.</p>
+software. Here is an updated version of our <code>CITATION.cff</code>
+from the previous episode with a version number, DOI and release date
+added.</p>
 <div class="codewrapper sourceCode" id="cb3">
 <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
 <pre class="sourceCode yaml" tabindex="0"><code class="sourceCode yaml"><span id="cb3-1"><a href="#cb3-1" tabindex="-1"></a><span class="co"># This CITATION.cff file was generated with cffinit.</span></span>
 <span id="cb3-2"><a href="#cb3-2" tabindex="-1"></a><span class="co"># Visit https://bit.ly/cffinit to generate yours today!</span></span>
-<span id="cb3-3"><a href="#cb3-3" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
-<span id="cb3-4"><a href="#cb3-4" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> My Software</span></span>
-<span id="cb3-5"><a href="#cb3-5" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
-<span id="cb3-6"><a href="#cb3-6" tabindex="-1"></a>  If you use this software, please cite it using the</span>
-<span id="cb3-7"><a href="#cb3-7" tabindex="-1"></a>  metadata from this file.</span>
-<span id="cb3-8"><a href="#cb3-8" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
-<span id="cb3-9"><a href="#cb3-9" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
-<span id="cb3-10"><a href="#cb3-10" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Anne</span></span>
-<span id="cb3-11"><a href="#cb3-11" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Researcher</span></span>
-<span id="cb3-12"><a href="#cb3-12" tabindex="-1"></a><span class="fu">version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.0.1</span></span>
-<span id="cb3-13"><a href="#cb3-13" tabindex="-1"></a><span class="fu">identifiers</span><span class="kw">:</span></span>
-<span id="cb3-14"><a href="#cb3-14" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> doi</span></span>
-<span id="cb3-15"><a href="#cb3-15" tabindex="-1"></a><span class="at">    </span><span class="fu">value</span><span class="kw">:</span><span class="at"> 10.5281/zenodo.1234</span></span>
-<span id="cb3-16"><a href="#cb3-16" tabindex="-1"></a><span class="fu">date-released</span><span class="kw">:</span><span class="at"> 2024-06-01</span></span></code></pre>
+<span id="cb3-3"><a href="#cb3-3" tabindex="-1"></a></span>
+<span id="cb3-4"><a href="#cb3-4" tabindex="-1"></a><span class="fu">cff-version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.2.0</span></span>
+<span id="cb3-5"><a href="#cb3-5" tabindex="-1"></a><span class="fu">title</span><span class="kw">:</span><span class="at"> Spacewalks</span></span>
+<span id="cb3-6"><a href="#cb3-6" tabindex="-1"></a><span class="fu">message</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-7"><a href="#cb3-7" tabindex="-1"></a>  If you use this software, please cite it using the</span>
+<span id="cb3-8"><a href="#cb3-8" tabindex="-1"></a>  metadata from this file.</span>
+<span id="cb3-9"><a href="#cb3-9" tabindex="-1"></a><span class="fu">type</span><span class="kw">:</span><span class="at"> software</span></span>
+<span id="cb3-10"><a href="#cb3-10" tabindex="-1"></a><span class="fu">authors</span><span class="kw">:</span></span>
+<span id="cb3-11"><a href="#cb3-11" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Jaffa</span></span>
+<span id="cb3-12"><a href="#cb3-12" tabindex="-1"></a><span class="at">    </span><span class="fu">name-particle</span><span class="kw">:</span><span class="at"> Sarah</span></span>
+<span id="cb3-13"><a href="#cb3-13" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Aleksandra</span></span>
+<span id="cb3-14"><a href="#cb3-14" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Nenadic</span></span>
+<span id="cb3-15"><a href="#cb3-15" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">given-names</span><span class="kw">:</span><span class="at"> Kamilla</span></span>
+<span id="cb3-16"><a href="#cb3-16" tabindex="-1"></a><span class="at">    </span><span class="fu">family-names</span><span class="kw">:</span><span class="at"> Kopec-Harding</span></span>
+<span id="cb3-17"><a href="#cb3-17" tabindex="-1"></a><span class="fu">repository-code</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-18"><a href="#cb3-18" tabindex="-1"></a>  https://github.com/YOUR-REPOSITORY-URL/spacewalks.git</span>
+<span id="cb3-19"><a href="#cb3-19" tabindex="-1"></a><span class="fu">abstract</span><span class="kw">: </span><span class="ch">&gt;-</span></span>
+<span id="cb3-20"><a href="#cb3-20" tabindex="-1"></a>  A Python script to analyse NASA extravehicular activity</span>
+<span id="cb3-21"><a href="#cb3-21" tabindex="-1"></a>  data</span>
+<span id="cb3-22"><a href="#cb3-22" tabindex="-1"></a><span class="fu">keywords</span><span class="kw">:</span></span>
+<span id="cb3-23"><a href="#cb3-23" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> NASA</span></span>
+<span id="cb3-24"><a href="#cb3-24" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> Extravehicular activity</span></span>
+<span id="cb3-25"><a href="#cb3-25" tabindex="-1"></a><span class="fu">version</span><span class="kw">:</span><span class="at"> </span><span class="fl">1.0.1</span></span>
+<span id="cb3-26"><a href="#cb3-26" tabindex="-1"></a><span class="fu">identifiers</span><span class="kw">:</span></span>
+<span id="cb3-27"><a href="#cb3-27" tabindex="-1"></a><span class="at">  </span><span class="kw">-</span><span class="at"> </span><span class="fu">type</span><span class="kw">:</span><span class="at"> doi</span></span>
+<span id="cb3-28"><a href="#cb3-28" tabindex="-1"></a><span class="at">    </span><span class="fu">value</span><span class="kw">:</span><span class="at"> 10.5281/zenodo.1234</span></span>
+<span id="cb3-29"><a href="#cb3-29" tabindex="-1"></a><span class="fu">date-released</span><span class="kw">:</span><span class="at"> 2024-06-01</span></span></code></pre>
 </div>
 <div id="add-a-doi-to-your-citation-file" class="callout discussion">
 <div class="callout-square">
@@ -7512,10 +7570,11 @@ <h3 class="code-label">YAML<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="callout-title">Add a DOI to your citation file</h3>
 <div class="callout-content">
 <p>Add the DOI you were allocated in the previous exercise to your
-CITATION.cff file and commit/push the updated version to your Github
-repository. You can remove the <code>commit</code> field from the
-CITATION.cff file as the DOI is a better way to point to given version
-of the code.</p>
+<code>CITATION.cff</code> file and then commit and push the updated
+version to your GitHub repository. If you used the <code>commit</code>
+field in your <code>CITATION.cff</code> file before to point to a given
+version of the code - you can now remove it as using the DOI field is
+better for this job.</p>
 </div>
 </div>
 </div>
@@ -7546,25 +7605,25 @@ <h3 class="callout-title">Going further with publishing code</h3>
 </section><section><h2 class="section-heading" id="working-with-collaborators">Working with collaborators<a class="anchor" aria-label="anchor" href="#working-with-collaborators"></a>
 </h2>
 <hr class="half-width">
-<p>The strength of online collaboration tools such as Github doesn’t
-just lie in the ability to share code. They also allow us to track
+<p>The strength of online collaboration platforms such as GitHub does
+not just lie in the ability to share code. They also allow us to track
 problems with that code, for multiple developers to work on it
 independently and bring their changes together and to review those
 changes before they are accepted.</p>
 <div class="section level3">
 <h3 id="tracking-issues-with-code">Tracking issues with code<a class="anchor" aria-label="anchor" href="#tracking-issues-with-code"></a>
 </h3>
-<p>A key feature of Github (as opposed to Git itself) is the issue
+<p>A key feature of GitHub (as opposed to Git itself) is the issue
 tracker. This provides us with a place to keep track of any problems or
 bugs in the code and to discuss them with other developers. Sometimes
 advanced users will also use issue trackers of public projects to report
 problems they are having (and sometimes this is misused by users seeking
 help using documented features of the program).</p>
 <p>The code from the testing chapter earlier has a bug with an extra
-bracket in eva_data_analysis.py (and if you’ve fixed that a missing
+bracket in eva_data_analysis.py (and if you have fixed that a missing
 import of summarise_categorical in the test). Let’s go ahead and create
-a new issue in our Github repository to describe this problem. We can
-find the issue tracker on the “Issues” tab in the top left of the Github
+a new issue in our GitHub repository to describe this problem. We can
+find the issue tracker on the “Issues” tab in the top left of the GitHub
 page for the repository. Click on this and then click on the green “New
 Issue” button on the right hand side of the screen. We can then enter a
 title and description of our issue.</p>
@@ -7590,7 +7649,7 @@ <h3 class="callout-title">Write an issue to describe our bug</h3>
 <p>Create a new issue in your repository’s issue tracker by doing the
 following:</p>
 <ul>
-<li>Go to the Github webpage for your code</li>
+<li>Go to the GitHub webpage for your code</li>
 <li>Click on the Issues tab</li>
 <li>Click on the “New issue” button</li>
 <li>Enter a title and description for the issue</li>
@@ -7614,7 +7673,7 @@ <h3 id="discussing-an-issue">Discussing an issue<a class="anchor" aria-label="an
 <h3 id="closing-an-issue">Closing an issue<a class="anchor" aria-label="anchor" href="#closing-an-issue"></a>
 </h3>
 <p>Once an issue is solved then it can be closed. This can be done
-either by pressing the “Close” button in the Github web interface or by
+either by pressing the “Close” button in the GitHub web interface or by
 making a commit which includes the word “fixes”, “fixed”, “close”,
 “closed” or “closes” followed by a # symbol and the issue number.</p>
 </div>
@@ -7626,37 +7685,38 @@ <h3 id="working-in-parallel-with-git-branches">Working in parallel with Git bran
 with another. Branches are commonly used as a way for one developer to
 work on a new feature or a bug fix while other developers work on other
 features. When those new features or bug fixes are complete, the branch
-will be merged back with the main (sometimes called master) branch.</p>
+will be merged back with the <code>main</code> (sometimes called the
+<code>master</code>) branch.</p>
 <div class="section level4">
 <h4 id="creating-a-new-branch">Creating a new branch<a class="anchor" aria-label="anchor" href="#creating-a-new-branch"></a>
 </h4>
-<p>New git branches are created with the <code>git branch</code>
+<p>New Git branches are created with the <code>git branch</code>
 command. This should be followed by the name of the branch to create. It
 is common practice when the bug we are fixing has a corresponding issue
 to name the branch after the issue number and name. For example, we
-might call the branch <code>01-extra-brakcet-bug</code> instead of
+might call the branch <code>01-extra-bracket-bug</code> instead of
 something less descriptive like <code>bugfix</code>.</p>
 <p>For example, the command:</p>
 <div class="codewrapper sourceCode" id="cb4">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="fu">git</span> branch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb4-1"><a href="#cb4-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git branch 01-extra-bracket-bug</span></code></pre>
 </div>
-<p>will create a new branch called <code>01-extra-brakcet-bug</code>. We
-can view the names of all the branches, by default there should be one
-branch called <code>main</code> or perhaps <code>master</code> and our
-new <code>01-extra-brakcet-bug</code> branch. by running
-<code>git branch</code> with no parameters. This will put <code>*</code>
-next to the currently active branch.</p>
+<p>will create a new branch called <code>01-extra-bracket-bug</code>. We
+can view the names of all the branches by running
+<code>git branch</code> with no parameters. By default there should be
+one branch called <code>main</code> (formerly <code>master</code>) and
+our new <code>01-extra-bracket-bug</code> branch. The command will put
+<code>*</code> next to the currently active branch.</p>
 <div class="codewrapper sourceCode" id="cb5">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" tabindex="-1"></a><span class="fu">git</span> branch</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git branch</span></code></pre>
 </div>
 <div class="codewrapper">
 <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="output" tabindex="0"><code>  01-extra-brakcet-bug
+<pre class="output" tabindex="0"><code>  01-extra-bracket-bug
 * main</code></pre>
 </div>
 <p>We can see that creating a new branch has not activated that branch.
@@ -7666,28 +7726,28 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="fu">git</span> switch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch 01-extra-bracket-bug</span></code></pre>
 </div>
 <p>To create a branch and change to it in a single command we can use
 <code>git switch</code> with the <code>-c</code> option (or
-<code>git checkout</code> with the <code>-b</code> option,
-<code>git switch</code> is only found in more recent versions of
-Git).</p>
+<code>git checkout</code> with the <code>-b</code> option). Note that
+<code>git switch</code> command is only available in more recent
+versions of Git.</p>
 <div class="codewrapper sourceCode" id="cb8">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="fu">git</span> switch <span class="at">-c</span> 02-another-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch <span class="at">-c</span> 02-another-bug</span></code></pre>
 </div>
 </div>
 <div class="section level4">
 <h4 id="committing-to-a-branch">Committing to a branch<a class="anchor" aria-label="anchor" href="#committing-to-a-branch"></a>
 </h4>
 <p>Once we have switched to a branch any further commits that are made
-will go to that branch. When we run a <code>git commit</code> command
-we’ll see the name of the branch we’re committing to in the output of
+will go to that branch. When we run a <code>git commit</code> command we
+will see the name of the branch we are committing to in the output of
 <code>git commit</code>. Let’s edit our code and fix the lack of default
 values bug that we entered into the issue tracker earlier on.</p>
-<p>Change your code from</p>
+<p>Change your code from:</p>
 <div class="codewrapper sourceCode" id="cb9">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
@@ -7703,7 +7763,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb11">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"fixed bug"</span> eva_data_analysis.py</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb11-1"><a href="#cb11-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"fixed bug"</span> eva_data_analysis.py</span></code></pre>
 </div>
 <p>In the output of <code>git commit -m</code> the first part of the
 output line will show the name of the branch we just made the commit
@@ -7719,14 +7779,14 @@ <h3 class="code-label">OUTPUT<i aria-hidden="true" data-feather="chevron-left"><
 <div class="codewrapper sourceCode" id="cb13">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="fu">git</span> switch main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb13-1"><a href="#cb13-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch main</span></code></pre>
 </div>
-<p>And if we go back to the <code>01-extra-brakcet-bug</code> branch it
+<p>And if we go back to the <code>01-extra-bracket-bug</code> branch it
 will re-appear.</p>
 <div class="codewrapper sourceCode" id="cb14">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="fu">git</span> switch 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb14-1"><a href="#cb14-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch 01-extra-bracket-bug</span></code></pre>
 </div>
 <p>If we want to push our changes to a remote such as GitHub we have to
 tell the <code>git push</code> command which branch to push to. If the
@@ -7735,18 +7795,18 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <div class="codewrapper sourceCode" id="cb15">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="fu">git</span> push origin 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb15-1"><a href="#cb15-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin 01-extra-bracket-bug</span></code></pre>
 </div>
-<p>If we now refresh the Github webpage for this repository we should
+<p>If we now refresh the GitHub webpage for this repository we should
 see the bugfix branch has appeared in the list of branches.</p>
 <p>If we needed to pull changes from a branch on a remote (for example
-if we’ve made changes on another computer or via Github’s web based
+if we have made changes on another computer or via GitHub’s web based
 editor), then we can specify a branch on a <code>git pull</code>
 command.</p>
 <div class="codewrapper sourceCode" id="cb16">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">git</span> pull origin 01-extra-brakcet-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb16-1"><a href="#cb16-1" tabindex="-1"></a><span class="fu">git</span> pull origin 01-extra-bracket-bug</span></code></pre>
 </div>
 </div>
 </div>
@@ -7756,19 +7816,19 @@ <h3 id="merging-branches">Merging branches<a class="anchor" aria-label="anchor"
 <p>When we have completed working on a branch (for example fixing a bug)
 then we can merge our branch back into the main one (or any other
 branch). This is done with the <code>git merge</code> command.</p>
-<p>This must be run on the <em>TARGET</em> branch of the merge, so we’ll
-have to use a <code>git switch</code> command to set this.</p>
+<p>This must be run on the <em>TARGET</em> branch of the merge, so we
+will have to use a <code>git switch</code> command to set this.</p>
 <div class="codewrapper sourceCode" id="cb17">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="fu">git</span> switch main</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb17-1"><a href="#cb17-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git switch main</span></code></pre>
 </div>
-<p>Now we’re back on the main branch we can go ahead and merge the
+<p>Now we are back on the main branch we can go ahead and merge the
 changes from the bugfix branch:</p>
 <div class="codewrapper sourceCode" id="cb18">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="fu">git</span> merge 01-extra-bracket-bug</span></code></pre>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb18-1"><a href="#cb18-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git merge 01-extra-bracket-bug</span></code></pre>
 </div>
 </div>
 <div class="section level3">
@@ -7777,25 +7837,26 @@ <h3 id="pull-requests">Pull requests<a class="anchor" aria-label="anchor" href="
 <p>On larger projects we might need to have a code review process before
 changes are merged, especially before they are merged onto the main
 branch that might be what is being released as the public version of the
-software. Github has a process for this that it calls a “Pull Request”,
-other Git services such as GitLab have different names for this, GitLab
-calls them “Merge Requests”. Pull requests are where one developer
-requests that another merge code from a branch (or “pull” it from
-another copy of the repository). The person receiving the request then
-has the chance to review the code, write comments suggesting changes or
-even change the code themselves before merging it. It is also very
-common for automated checks of code to be run on a pull request to
-ensure the code is of good quality and is passing automated tests.</p>
+software. GitHub has a process for this that is called a <strong>pull
+request</strong>. Other Git services such as GitLab have different names
+for this; GitLab calls them <strong>merge requests</strong>. Pull
+requests are situations where one developer requests that another merges
+code from a branch (or “pull” it from another copy of the repository).
+The person receiving the request then has the chance to review the code,
+write comments suggesting changes or even change the code themselves
+before merging it. It is also very common for automated checks of code
+to be run on a pull request to ensure the code is of good quality and is
+passing automated tests.</p>
 <p>As a simple example of a pull request, we can now create a pull
 request for the changes we made on our <code>01-extra-bracket-bug</code>
-branch and pushed to Github earlier on. The Github webpage for our
-repository will now be saying something like “bugfix had recent pushes n
-minutes ago - Compare &amp; Pull request”. Click on this button and
-create a new pull request.</p>
+branch and pushed to GitHub earlier on. The GitHub webpage for our
+repository will now be saying something like “bugfix had recent pushes
+<code>n</code> minutes ago - Compare &amp; Pull request”. Click on this
+button and create a new pull request.</p>
 <p>Give the pull request a title and write a brief description of it,
-then click the green “Create pull request” button. Github will then
-check if we can merge this pull request without any problems. We’ll look
-at what to do when this isn’t possible later on.</p>
+then click the green “Create pull request” button. GitHub will then
+check if we can merge this pull request without any problems. We will
+look at what to do when this is not possible later on.</p>
 <p>There should be a green “Merge pull request” button, but if we click
 on the down arrow inside this button there are three options on how to
 handle this request:</p>
@@ -7819,44 +7880,45 @@ <h3 id="pull-requests">Pull requests<a class="anchor" aria-label="anchor" href="
 kind of merge they will prefer. For the purposes of this exercise we’ll
 stick with the default merge commit.</p>
 <p>Go ahead and click on “Merge pull request”, then “Confirm merge”. The
-changes will now be merged together. Github gives us the option to
-delete the branch we were working on, since it’s history is preserved in
-the main branch there isn’t any reason to keep it.</p>
+changes will now be merged together. GitHub gives us the option to
+delete the branch we were working on, since its history is preserved in
+the main branch there is no reason to keep it.</p>
 <div class="section level4">
 <h4 id="using-forks-instead-of-branches">Using forks instead of branches<a class="anchor" aria-label="anchor" href="#using-forks-instead-of-branches"></a>
 </h4>
 <p>A fork is similar to a branch, but instead of it being part of the
 same repository it is a entirely new copy of the repository. Forks are
-commonly used by Github users who wish to work on a project that they’re
-not a member of. Typically forking will copy the repository to our own
-namespace (e.g. github.com/username/reponame instead of
+commonly used by Github users who wish to work on a project that they
+are not a member of. Typically forking will copy the repository to our
+own namespace (e.g. github.com/username/reponame instead of
 github.com/projectname/reponame)</p>
 <p>To create a fork on github use the “Fork” button to the right of the
 repository name. After we create our fork we can make some changes and
 these could even be on the main branch inside our forked repository.
-Github will track that a fork has been made displays a “Contribute”
+GitHub will track that a fork has been made displays a “Contribute”
 button to create a pull request back to the original repository. Using
 this we can request that the changes on our fork are incorporated by the
 upstream project.</p>
-<div id="pull-request-exercise" class="callout discussion">
+<div id="practice-pull-requests" class="callout discussion">
 <div class="callout-square">
 <i class="callout-icon" data-feather="message-circle"></i>
 </div>
-<div id="pull-request-exercise" class="callout-inner">
-<h3 class="callout-title">Pull request exercise</h3>
+<div id="practice-pull-requests" class="callout-inner">
+<h3 class="callout-title">Practice pull requests</h3>
 <div class="callout-content">
-<p>Q: Work in pairs for this exercise. Share the Github link of your
+<p>Q: Work in pairs for this exercise. Share the GitHub link of your
 repository with your partner. If you have set your repository to
-private, you’ll need to add them as a collaborator. Go to the settings
-page on your Github repository’s webpage, click on Collaborators from
+private, you will need to add them as a collaborator. Go to the settings
+page on your GitHub repository’s webpage, click on Collaborators from
 the left hand menu and then click the green “Add People” button and
-enter the Github username or email address of your partner. They will
-get an email and an alert within Github to accept your invitation to
+enter the GitHub username or email address of your partner. They will
+get an email and an alert within GitHub to accept your invitation to
 work on this repository, without doing this they won’t be able to access
 it.</p>
 <ul>
 <li>Now make a fork of your partners repository.</li>
-<li>Edit the CITATION.cff file and add your name to it.</li>
+<li>Edit the <code>CITATION.cff</code> file and add your name to
+it.</li>
 <li>Commit these changes to your fork</li>
 <li>Create a pull request back to the original repository</li>
 <li>Your partner will now receive your pull request and can review</li>
@@ -7864,24 +7926,14 @@ <h3 class="callout-title">Pull request exercise</h3>
 </div>
 </div>
 </div>
-<div id="commit-and-push-your-changes" class="callout">
-<div class="callout-square">
-<i class="callout-icon" data-feather="bell"></i>
-</div>
-<div id="commit-and-push-your-changes" class="callout-inner">
-<h3 class="callout-title">Commit and push your changes</h3>
-<div class="callout-content">
-<p>Do not forget to commit any uncommited changes you may have and then
+<p>Do not forget to commit any uncommitted changes you may have and then
 push your work to GitHub.</p>
 <div class="codewrapper sourceCode" id="cb19">
 <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
 </h3>
-<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="fu">git</span> add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
-<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="fu">git</span> commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
-<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="fu">git</span> push origin main</span></code></pre>
-</div>
-</div>
-</div>
+<pre class="sourceCode bash" tabindex="0"><code class="sourceCode bash"><span id="cb19-1"><a href="#cb19-1" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git add <span class="op">&lt;</span>your_changed_files<span class="op">&gt;</span></span>
+<span id="cb19-2"><a href="#cb19-2" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git commit <span class="at">-m</span> <span class="st">"Your commit message"</span></span>
+<span id="cb19-3"><a href="#cb19-3" tabindex="-1"></a><span class="kw">(</span><span class="ex">venv_spacewalks</span><span class="kw">)</span> <span class="ex">$</span> git push origin main</span></code></pre>
 </div>
 </div>
 </div>
@@ -7894,7 +7946,7 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <li>Licencing and citation episodes from the <a href="https://swcarpentry.github.io/git-novice" class="external-link">Software Carpentry’s Git
 Novice lesson</a>
 </li>
-<li>Carpentries Github Skill ups for <a href="https://carpentries-incubator.github.io/github-skill-up-instructors/" class="external-link">instructors</a>
+<li>Carpentries GitHub Skill ups for <a href="https://carpentries-incubator.github.io/github-skill-up-instructors/" class="external-link">instructors</a>
 and <a href="https://carpentries.github.io/github-skill-up-maintainers/" class="external-link">maintainers</a>
 </li>
 <li>
@@ -7919,26 +7971,13 @@ <h3 class="code-label">BASH<i aria-hidden="true" data-feather="chevron-left"></i
 <h3 class="callout-title">Key Points</h3>
 <div class="callout-content">
 <ul>
-<li>Open source applies Copyright licenses permitting others to reuse
-and adapt your code or data.</li>
-<li>Permissive licenses allow code to be used in other products
-providing the copyright statement is displayed.</li>
-<li>Copyleft licenses require the source code of any modifications to be
-released under a copyleft license.</li>
-<li>Creative commons licenses are suitable for non-code files such as
-documentation and images.</li>
-<li>Open source software can be sold, but you must supply the source
-code and the people you sell it to can give it away to somebody
-else.</li>
-<li>Add license file to your repository and add a license to each file
-in case it gets detached.</li>
-<li>Zenodo can be used to archive a Github repository and obtain a DOI
+<li>Zenodo can be used to archive a GitHub repository and obtain a DOI
 for it.</li>
-<li>We can include a CITATION file to tell people how to cite our
-code.</li>
-<li>Github can track bugs or issues with a program.</li>
+<li>We include a CITATION file with our code to tell people how to cite
+it.</li>
+<li>GitHub can help us track bugs or issues with software.</li>
 <li>Git branches can be used to allow multiple developers to work on the
-same part of a program in parallel.</li>
+same part of code in parallel.</li>
 <li>The <code>git branch</code> command shows the list of branches and
 can create new branches.</li>
 <li>The <code>git switch</code> command changes which branch we are
@@ -8085,7 +8124,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer>
 </div> <!-- / div.container -->
@@ -8108,8 +8147,8 @@ <h3 class="callout-title">Key Points</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/aio.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/aio.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/ci-for-testing.html b/instructor/ci-for-testing.html
index 129f602f..3336c204 100644
--- a/instructor/ci-for-testing.html
+++ b/instructor/ci-for-testing.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -584,7 +584,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -607,7 +607,7 @@ <h3 class="callout-title">Key Points</h3>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/ci-for-testing.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/ethical-environmental-considerations.html b/instructor/ethical-environmental-considerations.html
index 43a1e1f6..2768a9bf 100644
--- a/instructor/ethical-environmental-considerations.html
+++ b/instructor/ethical-environmental-considerations.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -448,7 +448,7 @@ <h3 class="callout-title">Scraping publicly available data responsibly</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
 <div class="accordion-body">
 <ol style="list-style-type: decimal"><li>Compliance with Terms of Service (ToS) - most websites, including
 forums, have ToS that explicitly prohibit or restrict web scraping.
@@ -524,7 +524,7 @@ <h3 class="callout-title">Ethical software reuse</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
 <div class="accordion-body">
 <p>When incorporating other researchers’ software into our research
 workflows we should not do it blindly but should inspect it critically
@@ -605,7 +605,7 @@ <h3 class="callout-title">Intellectual property and licensing of AI-generated co
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution3" aria-expanded="false" aria-controls="collapseSolution3">
   <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 </button>
-<div id="collapseSolution3" class="accordion-collapse collapse" aria-labelledby="headingSolution3" data-bs-parent="#accordionSolution3">
+<div id="collapseSolution3" class="accordion-collapse collapse" data-bs-parent="#accordionSolution3" aria-labelledby="headingSolution3">
 <div class="accordion-body">
 <p>Here are some considerations:</p>
 <ul><li>Intellectual Property (IP) ownership of the AI-generated code -
@@ -687,7 +687,7 @@ <h3 class="callout-title">Using HPC systems in a more environmentally responsibl
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution4" aria-expanded="false" aria-controls="collapseSolution4">
   <h4 class="accordion-header" id="headingSolution4"> Show me the solution </h4>
 </button>
-<div id="collapseSolution4" class="accordion-collapse collapse" aria-labelledby="headingSolution4" data-bs-parent="#accordionSolution4">
+<div id="collapseSolution4" class="accordion-collapse collapse" data-bs-parent="#accordionSolution4" aria-labelledby="headingSolution4">
 <div class="accordion-body">
 <p>Here are some thing to consider:</p>
 <ul><li>Code efficiency: writing efficient code and choosing more efficient
@@ -785,7 +785,7 @@ <h3 class="callout-title">Key Points</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -808,7 +808,7 @@ <h3 class="callout-title">Key Points</h3>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/ethical-environmental-considerations.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-09-17",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/images.html b/instructor/images.html
index 6ba5d91b..897423bd 100644
--- a/instructor/images.html
+++ b/instructor/images.html
@@ -355,7 +355,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -511,7 +511,7 @@ <h3 id="04-version-control-figure-8">Figure 8</h3>
 <hr class="half-width"></section><section id="07-code-structure"><h2 class="section-heading"><a href="07-code-structure.html">Code structure</a></h2>
 <hr class="half-width"></section><section id="08-code-correctness"><h2 class="section-heading"><a href="08-code-correctness.html">Code correctness</a></h2>
 <hr class="half-width"></section><section id="09-code-documentation"><h2 class="section-heading"><a href="09-code-documentation.html">Code documentation</a></h2>
-<hr class="half-width"></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open collaboration on code</a></h2>
+<hr class="half-width"></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open code &amp; collaboration</a></h2>
 <hr class="half-width">
 <h3 id="10-open-collaboration-figure-1">Figure 1</h3>
 <p aria-hidden="true">Image 1 of 1: ‘DOI’</p>
@@ -562,7 +562,7 @@ <h3 id="11-wrap-up-figure-4">Figure 4</h3>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer>
 </div> <!-- / div.container -->
@@ -585,8 +585,8 @@ <h3 id="11-wrap-up-figure-4">Figure 4</h3>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/images.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/images.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/index.html b/instructor/index.html
index 4b213a60..b4e28232 100644
--- a/instructor/index.html
+++ b/instructor/index.html
@@ -300,7 +300,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -510,7 +510,7 @@ <h3 class="callout-title">Prerequisites</h3>
  7. <a href="07-code-structure.html">Code structure</a>
 </td>
 <td>
-How can we bests structure code?<br>What is a common code structure
+How can we best structure code?<br>What is a common code structure
 (pattern) for creating software that can read input from command
 line?<br>What are conventional places to store data, code, results,
 tests, auxiliary information and metadata<br>within our software or
@@ -543,7 +543,8 @@ <h3 class="callout-title">Prerequisites</h3>
 <span class="visually-hidden">Duration: </span>11h 00m
 </td>
 <td>
-10. <a href="10-open-collaboration.html">Open collaboration on code</a>
+10. <a href="10-open-collaboration.html">Open code &amp;
+collaboration</a>
 </td>
 <td>
 How do I ensure my code is citable?<br>How do we track issues with code
@@ -1042,7 +1043,7 @@ <h3 id="astronaut-data-and-analysis-code">Astronaut data and analysis code<a cla
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -1064,8 +1065,8 @@ <h3 id="astronaut-data-and-analysis-code">Astronaut data and analysis code<a cla
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/index.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/index.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/instructor-notes.html b/instructor/instructor-notes.html
index 0801d380..0f41f3d2 100644
--- a/instructor/instructor-notes.html
+++ b/instructor/instructor-notes.html
@@ -355,7 +355,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -445,14 +445,7 @@ <h1>Instructor Notes</h1>
       <section id="aggregate-instructor-notes"><section id="01-introduction"><h2 class="section-heading"><a href="01-introduction.html">Course introduction</a></h2>
 <hr class="half-width"></section><section id="02-fair-research-software"><h2 class="section-heading"><a href="02-fair-research-software.html">FAIR research software</a></h2>
 <hr class="half-width"></section><section id="03-tools"><h2 class="section-heading"><a href="03-tools.html">Tools and practices for FAIR research software development</a></h2>
-<hr class="half-width">
-<h3 id="03-tools-headingInstructor1">
-<a href="03-tools.html#headingInstructor1">Instructor Note</a><a class="anchor" aria-label="anchor" href="#03-tools-headingInstructor1"></a>
-</h3>
-<p>At this point you could open the Python file or another file in VS
-Code to show all the squiggly lines suggesting improvements.</p>
-<hr>
-<br></section><section id="04-version-control"><h2 class="section-heading"><a href="04-version-control.html">Version control</a></h2>
+<hr class="half-width"></section><section id="04-version-control"><h2 class="section-heading"><a href="04-version-control.html">Version control</a></h2>
 <hr class="half-width">
 <h3 id="04-version-control-headingInstructor1">
 <a href="04-version-control.html#headingInstructor1">Instructor Note</a><a class="anchor" aria-label="anchor" href="#04-version-control-headingInstructor1"></a>
@@ -509,8 +502,15 @@ <h3 id="09-code-documentation-headingInstructor1">
 code repository (as there is likely not going to be enough time to spend
 on different license types).</p>
 <hr>
-<br></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open collaboration on code</a></h2>
-<hr class="half-width"></section><section id="11-wrap-up"><h2 class="section-heading"><a href="11-wrap-up.html">Wrap-up</a></h2>
+<br></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open code &amp; collaboration</a></h2>
+<hr class="half-width">
+<h3 id="10-open-collaboration-headingInstructor1">
+<a href="10-open-collaboration.html#headingInstructor1">Instructor Note</a><a class="anchor" aria-label="anchor" href="#10-open-collaboration-headingInstructor1"></a>
+</h3>
+<p>At this point, the code in your local software project’s directory
+should be as in: <a href="https://github.com/carpentries-incubator/astronaut-data-analysis-not-so-fair/tree/10-open-collaboration" class="external-link uri">https://github.com/carpentries-incubator/astronaut-data-analysis-not-so-fair/tree/10-open-collaboration</a></p>
+<hr>
+<br></section><section id="11-wrap-up"><h2 class="section-heading"><a href="11-wrap-up.html">Wrap-up</a></h2>
 <hr class="half-width"></section></section>
 </div>
     </main>
@@ -536,7 +536,7 @@ <h3 id="09-code-documentation-headingInstructor1">
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer>
 </div> <!-- / div.container -->
@@ -559,8 +559,8 @@ <h3 id="09-code-documentation-headingInstructor1">
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/instructor-notes.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/instructor-notes.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/key-points.html b/instructor/key-points.html
index eb8e39ee..4073435f 100644
--- a/instructor/key-points.html
+++ b/instructor/key-points.html
@@ -355,7 +355,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -538,29 +538,16 @@ <h2 class="accordion-header" id="flush-headingTwelve">
 MkDocs.</li>
 <li>Documentation frameworks such as Diataxis provide content and style
 guidelines that can helps us write high quality documentation.</li>
-</ul></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open collaboration on code</a></h2>
+</ul></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open code &amp; collaboration</a></h2>
 <hr class="half-width">
 <ul>
-<li>Open source applies Copyright licenses permitting others to reuse
-and adapt your code or data.</li>
-<li>Permissive licenses allow code to be used in other products
-providing the copyright statement is displayed.</li>
-<li>Copyleft licenses require the source code of any modifications to be
-released under a copyleft license.</li>
-<li>Creative commons licenses are suitable for non-code files such as
-documentation and images.</li>
-<li>Open source software can be sold, but you must supply the source
-code and the people you sell it to can give it away to somebody
-else.</li>
-<li>Add license file to your repository and add a license to each file
-in case it gets detached.</li>
-<li>Zenodo can be used to archive a Github repository and obtain a DOI
+<li>Zenodo can be used to archive a GitHub repository and obtain a DOI
 for it.</li>
-<li>We can include a CITATION file to tell people how to cite our
-code.</li>
-<li>Github can track bugs or issues with a program.</li>
+<li>We include a CITATION file with our code to tell people how to cite
+it.</li>
+<li>GitHub can help us track bugs or issues with software.</li>
 <li>Git branches can be used to allow multiple developers to work on the
-same part of a program in parallel.</li>
+same part of code in parallel.</li>
 <li>The <code>git branch</code> command shows the list of branches and
 can create new branches.</li>
 <li>The <code>git switch</code> command changes which branch we are
@@ -601,7 +588,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer>
 </div> <!-- / div.container -->
@@ -624,8 +611,8 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/key-points.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/key-points.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/licensing.html b/instructor/licensing.html
index 0c68ccbc..bc043592 100644
--- a/instructor/licensing.html
+++ b/instructor/licensing.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -360,7 +360,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Software licensing</h1>
-        <p>Last updated on 2024-08-12 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/learners/licensing.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -759,7 +759,7 @@ <h3 class="callout-title">Select a license</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
 <div class="accordion-body">
 <p>The LGPL license could be a good choice for library code. It can be
 linked to software that is not GPL licensed but any modifications to the
@@ -840,7 +840,7 @@ <h3 class="callout-title">Relicensing code</h3>
 <button class="accordion-button hint-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseHint1" aria-expanded="false" aria-controls="collapseHint1">
   <h4 class="accordion-header" id="headingHint1"> Give me a hint </h4>
 </button>
-<div id="collapseHint1" class="accordion-collapse collapse" data-bs-parent="#accordionHint1" aria-labelledby="headingHint1">
+<div id="collapseHint1" class="accordion-collapse collapse" aria-labelledby="headingHint1" data-bs-parent="#accordionHint1">
 <div class="accordion-body">
 <p>Hint: try looking at Matplotlib - <a href="https://matplotlib.org" class="external-link uri">https://matplotlib.org</a> which Spacewalks uses for
 plotting.</p>
@@ -853,7 +853,7 @@ <h4 class="accordion-header" id="headingHint1"> Give me a hint </h4>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
 <div class="accordion-body">
 <p>Here are a few examples:</p>
 <ul><li>Python - <a href="https://www.python.org/psf/contrib/" class="external-link uri">https://www.python.org/psf/contrib/</a>
@@ -866,6 +866,29 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </div>
 </div>
 </div>
+<div id="keypoints1" class="callout keypoints">
+<div class="callout-square">
+<i class="callout-icon" data-feather="key"></i>
+</div>
+<div class="callout-inner">
+<h3 class="callout-title">Key Points</h3>
+<div class="callout-content">
+<ul><li>Open source applies Copyright licenses permitting others to reuse
+and adapt your code or data.</li>
+<li>Permissive licenses allow code to be used in other products
+providing the copyright statement is displayed.</li>
+<li>Copyleft licenses require the source code of any modifications to be
+released under a copyleft license.</li>
+<li>Creative commons licenses are suitable for non-code files such as
+documentation and images.</li>
+<li>Open source software can be sold, but you must supply the source
+code and the people you sell it to can give it away to somebody
+else.</li>
+<li>Add license file to your repository and add a license to each file
+in case it gets detached.</li>
+</ul></div>
+</div>
+</div>
 <!--
 Place links that you need to refer to multiple times across pages here. Delete
 any links that you are not going to use.
@@ -907,7 +930,7 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -929,8 +952,8 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/licensing.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/licensing.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-08-12",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/profiles.html b/instructor/profiles.html
index b9525deb..1cd2c75f 100644
--- a/instructor/profiles.html
+++ b/instructor/profiles.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -447,7 +447,7 @@ <h1>Learner Profiles</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -469,8 +469,8 @@ <h1>Learner Profiles</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/profiles.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/profiles.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/instructor/test-suite-exercise.html b/instructor/test-suite-exercise.html
index 640c955c..1ea80c71 100644
--- a/instructor/test-suite-exercise.html
+++ b/instructor/test-suite-exercise.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -519,7 +519,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb4">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -593,7 +593,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb6">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -643,7 +643,7 @@ <h3 class="callout-title">Exercise 3 - invalid inputs</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution3" aria-expanded="false" aria-controls="collapseSolution3">
   <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 </button>
-<div id="collapseSolution3" class="accordion-collapse collapse" data-bs-parent="#accordionSolution3" aria-labelledby="headingSolution3">
+<div id="collapseSolution3" class="accordion-collapse collapse" aria-labelledby="headingSolution3" data-bs-parent="#accordionSolution3">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -708,7 +708,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -731,7 +731,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/test-suite-exercise.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/key-points.html b/key-points.html
index 4b426e2a..d7154c68 100644
--- a/key-points.html
+++ b/key-points.html
@@ -354,7 +354,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div>
 <!--/div.accordion-header-->
 
@@ -536,29 +536,16 @@ <h2 class="accordion-header" id="flush-headingTwelve">
 MkDocs.</li>
 <li>Documentation frameworks such as Diataxis provide content and style
 guidelines that can helps us write high quality documentation.</li>
-</ul></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open collaboration on code</a></h2>
+</ul></section><section id="10-open-collaboration"><h2 class="section-heading"><a href="10-open-collaboration.html">Open code &amp; collaboration</a></h2>
 <hr class="half-width">
 <ul>
-<li>Open source applies Copyright licenses permitting others to reuse
-and adapt your code or data.</li>
-<li>Permissive licenses allow code to be used in other products
-providing the copyright statement is displayed.</li>
-<li>Copyleft licenses require the source code of any modifications to be
-released under a copyleft license.</li>
-<li>Creative commons licenses are suitable for non-code files such as
-documentation and images.</li>
-<li>Open source software can be sold, but you must supply the source
-code and the people you sell it to can give it away to somebody
-else.</li>
-<li>Add license file to your repository and add a license to each file
-in case it gets detached.</li>
-<li>Zenodo can be used to archive a Github repository and obtain a DOI
+<li>Zenodo can be used to archive a GitHub repository and obtain a DOI
 for it.</li>
-<li>We can include a CITATION file to tell people how to cite our
-code.</li>
-<li>Github can track bugs or issues with a program.</li>
+<li>We include a CITATION file with our code to tell people how to cite
+it.</li>
+<li>GitHub can help us track bugs or issues with software.</li>
 <li>Git branches can be used to allow multiple developers to work on the
-same part of a program in parallel.</li>
+same part of code in parallel.</li>
 <li>The <code>git branch</code> command shows the list of branches and
 can create new branches.</li>
 <li>The <code>git switch</code> command changes which branch we are
@@ -599,7 +586,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer>
 </div> <!-- / div.container -->
@@ -622,8 +609,8 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "url": "https://softwaresaved.github.io/fair-research-software/key-points.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/key-points.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/licensing.html b/licensing.html
index 033d9fa4..f2e81cea 100644
--- a/licensing.html
+++ b/licensing.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -360,7 +360,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Software licensing</h1>
-        <p>Last updated on 2024-08-12 |
+        <p>Last updated on 2024-10-14 |
 
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/learners/licensing.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 
@@ -757,7 +757,7 @@ <h3 class="callout-title">Select a license</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
 <div class="accordion-body">
 <p>The LGPL license could be a good choice for library code. It can be
 linked to software that is not GPL licensed but any modifications to the
@@ -838,7 +838,7 @@ <h3 class="callout-title">Relicensing code</h3>
 <button class="accordion-button hint-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseHint1" aria-expanded="false" aria-controls="collapseHint1">
   <h4 class="accordion-header" id="headingHint1"> Give me a hint </h4>
 </button>
-<div id="collapseHint1" class="accordion-collapse collapse" data-bs-parent="#accordionHint1" aria-labelledby="headingHint1">
+<div id="collapseHint1" class="accordion-collapse collapse" aria-labelledby="headingHint1" data-bs-parent="#accordionHint1">
 <div class="accordion-body">
 <p>Hint: try looking at Matplotlib - <a href="https://matplotlib.org" class="external-link uri">https://matplotlib.org</a> which Spacewalks uses for
 plotting.</p>
@@ -851,7 +851,7 @@ <h4 class="accordion-header" id="headingHint1"> Give me a hint </h4>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
 <div class="accordion-body">
 <p>Here are a few examples:</p>
 <ul><li>Python - <a href="https://www.python.org/psf/contrib/" class="external-link uri">https://www.python.org/psf/contrib/</a>
@@ -864,6 +864,29 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </div>
 </div>
 </div>
+<div id="keypoints1" class="callout keypoints">
+<div class="callout-square">
+<i class="callout-icon" data-feather="key"></i>
+</div>
+<div class="callout-inner">
+<h3 class="callout-title">Key Points</h3>
+<div class="callout-content">
+<ul><li>Open source applies Copyright licenses permitting others to reuse
+and adapt your code or data.</li>
+<li>Permissive licenses allow code to be used in other products
+providing the copyright statement is displayed.</li>
+<li>Copyleft licenses require the source code of any modifications to be
+released under a copyleft license.</li>
+<li>Creative commons licenses are suitable for non-code files such as
+documentation and images.</li>
+<li>Open source software can be sold, but you must supply the source
+code and the people you sell it to can give it away to somebody
+else.</li>
+<li>Add license file to your repository and add a license to each file
+in case it gets detached.</li>
+</ul></div>
+</div>
+</div>
 <!--
 Place links that you need to refer to multiple times across pages here. Delete
 any links that you are not going to use.
@@ -905,7 +928,7 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -927,8 +950,8 @@ <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
   "url": "https://softwaresaved.github.io/fair-research-software/licensing.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/licensing.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-08-12",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/md5sum.txt b/md5sum.txt
index 442d544f..29ccb2a3 100644
--- a/md5sum.txt
+++ b/md5sum.txt
@@ -4,22 +4,22 @@
 "LICENSE.md" "b24ebbb41b14ca25cf6b8216dda83e5f" "site/built/LICENSE.md" "2023-10-03"
 "config.yaml" "233c98f6f1660c443ddd943465e06f80" "site/built/config.yaml" "2024-09-26"
 "index.md" "02ad77bddfc822162873c1f532255eeb" "site/built/index.md" "2024-09-13"
-"links.md" "1aba2c6f07134e834635a3381b5328b4" "site/built/links.md" "2024-09-24"
+"links.md" "95769884fcb051d978f4508fa523e499" "site/built/links.md" "2024-10-14"
 "episodes/01-introduction.md" "5ad6ec9b0ec53ca6e861ee719782bca4" "site/built/01-introduction.md" "2024-07-04"
-"episodes/02-fair-research-software.md" "b6e60011c17543d5d6e71b2fa3807fe6" "site/built/02-fair-research-software.md" "2024-07-04"
-"episodes/03-tools.md" "c290bc227d08f68f63acc30a3d2c307a" "site/built/03-tools.md" "2024-09-24"
-"episodes/04-version-control.md" "c1d090055a68e7bc566249646ce21c7a" "site/built/04-version-control.md" "2024-09-24"
-"episodes/05-code-environment.md" "3658165241a6e8ac2cc551a6ede4d289" "site/built/05-code-environment.md" "2024-09-24"
-"episodes/06-code-readability.md" "d17db5fc63187d2ea8a82fd4ac97b81a" "site/built/06-code-readability.md" "2024-09-26"
-"episodes/07-code-structure.md" "c184c0921657b211a4d00590dc566065" "site/built/07-code-structure.md" "2024-09-26"
-"episodes/08-code-correctness.md" "0c114e0600a149e0f2070b17fc40a239" "site/built/08-code-correctness.md" "2024-09-26"
-"episodes/09-code-documentation.md" "1bae1e17a141bf162218feee8e11819e" "site/built/09-code-documentation.md" "2024-09-26"
-"episodes/10-open-collaboration.md" "2426770a01755e5b512b02bbd9365087" "site/built/10-open-collaboration.md" "2024-09-24"
+"episodes/02-fair-research-software.md" "18f32628b3978cc5d6cf4bd05f9a2166" "site/built/02-fair-research-software.md" "2024-10-14"
+"episodes/03-tools.md" "90c36d859bdd60723c86d5daef3684c8" "site/built/03-tools.md" "2024-10-14"
+"episodes/04-version-control.md" "fcb7634fb3431936793161a3e63580c8" "site/built/04-version-control.md" "2024-10-14"
+"episodes/05-code-environment.md" "fd7e401e69605b3fbe41322c1d2e8e85" "site/built/05-code-environment.md" "2024-10-14"
+"episodes/06-code-readability.md" "a829d661277e6b2c0ca5e7b09b3255ac" "site/built/06-code-readability.md" "2024-10-14"
+"episodes/07-code-structure.md" "bd697cd5719ac841285f333077ec0c93" "site/built/07-code-structure.md" "2024-10-14"
+"episodes/08-code-correctness.md" "ac5057bb8cdd310a3379038394c621f3" "site/built/08-code-correctness.md" "2024-10-14"
+"episodes/09-code-documentation.md" "94318f688d932a80e3e77267fa065699" "site/built/09-code-documentation.md" "2024-10-14"
+"episodes/10-open-collaboration.md" "a42d52ef478b5127568ca5344a6f39e1" "site/built/10-open-collaboration.md" "2024-10-14"
 "episodes/11-wrap-up.md" "e0334370460adfbb7be9b5d3bf4d319f" "site/built/11-wrap-up.md" "2024-09-17"
 "instructors/instructor-notes.md" "cae72b6712578d74a49fea7513099f8c" "site/built/instructor-notes.md" "2023-10-03"
 "learners/test-suite-exercise.md" "db3dd1f950978ef7369b338c64aeb46e" "site/built/test-suite-exercise.md" "2024-09-26"
 "learners/ci-for-testing.md" "54f72155a009c524c4bc93fda946313b" "site/built/ci-for-testing.md" "2024-09-26"
-"learners/licensing.md" "65a402fbb9f714b47e557daedab59800" "site/built/licensing.md" "2024-08-12"
+"learners/licensing.md" "a1929a660164e48b952774d23292788b" "site/built/licensing.md" "2024-10-14"
 "learners/ethical-environmental-considerations.md" "41640e0e7f180a42994da3c78e8539cb" "site/built/ethical-environmental-considerations.md" "2024-09-17"
 "learners/setup.md" "2b9e2ab566548aa6bf6e38559fd0d24b" "site/built/setup.md" "2024-06-29"
 "profiles/learner-profiles.md" "8fb91d65843f75b9b4aa60783eb65389" "site/built/learner-profiles.md" "2024-07-05"
diff --git a/pkgdown.yml b/pkgdown.yml
index de2825ae..58dade89 100644
--- a/pkgdown.yml
+++ b/pkgdown.yml
@@ -2,4 +2,4 @@ pandoc: 3.1.11
 pkgdown: 2.1.1
 pkgdown_sha: ~
 articles: {}
-last_built: 2024-10-08T00:41Z
+last_built: 2024-10-14T09:34Z
diff --git a/profiles.html b/profiles.html
index 479cb973..c1294461 100644
--- a/profiles.html
+++ b/profiles.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -447,7 +447,7 @@ <h1>Learner Profiles</h1>
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -469,8 +469,8 @@ <h1>Learner Profiles</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/profiles.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/profiles.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2024-10-08",
-  "datePublished": "2024-10-08"
+  "dateModified": "2024-10-14",
+  "datePublished": "2024-10-14"
 }
 
   </script><script>
diff --git a/test-suite-exercise.html b/test-suite-exercise.html
index cbd795ca..31cff5be 100644
--- a/test-suite-exercise.html
+++ b/test-suite-exercise.html
@@ -287,7 +287,7 @@ <h2 class="accordion-header chapters" id="flush-headingEleven">
 <div class="accordion accordion-flush" id="accordionFlush11">
   <div class="accordion-item">
     <div class="accordion-header" id="flush-heading11">
-        <a href="10-open-collaboration.html">10. Open collaboration on code</a>
+        <a href="10-open-collaboration.html">10. Open code &amp; collaboration</a>
     </div><!--/div.accordion-header-->
 
   </div><!--/div.accordion-item-->
@@ -517,7 +517,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution1" aria-expanded="false" aria-controls="collapseSolution1">
   <h4 class="accordion-header" id="headingSolution1"> Show me the solution </h4>
 </button>
-<div id="collapseSolution1" class="accordion-collapse collapse" data-bs-parent="#accordionSolution1" aria-labelledby="headingSolution1">
+<div id="collapseSolution1" class="accordion-collapse collapse" aria-labelledby="headingSolution1" data-bs-parent="#accordionSolution1">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb4">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -591,7 +591,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution2" aria-expanded="false" aria-controls="collapseSolution2">
   <h4 class="accordion-header" id="headingSolution2"> Show me the solution </h4>
 </button>
-<div id="collapseSolution2" class="accordion-collapse collapse" data-bs-parent="#accordionSolution2" aria-labelledby="headingSolution2">
+<div id="collapseSolution2" class="accordion-collapse collapse" aria-labelledby="headingSolution2" data-bs-parent="#accordionSolution2">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb6">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -641,7 +641,7 @@ <h3 class="callout-title">Exercise 3 - invalid inputs</h3>
 <button class="accordion-button solution-button collapsed" type="button" data-bs-toggle="collapse" data-bs-target="#collapseSolution3" aria-expanded="false" aria-controls="collapseSolution3">
   <h4 class="accordion-header" id="headingSolution3"> Show me the solution </h4>
 </button>
-<div id="collapseSolution3" class="accordion-collapse collapse" data-bs-parent="#accordionSolution3" aria-labelledby="headingSolution3">
+<div id="collapseSolution3" class="accordion-collapse collapse" aria-labelledby="headingSolution3" data-bs-parent="#accordionSolution3">
 <div class="accordion-body">
 <div class="codewrapper sourceCode" id="cb7">
 <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"></i><i aria-hidden="true" data-feather="chevron-right"></i>
@@ -706,7 +706,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
         <p>Materials licensed under <a href="LICENSE.html">CC-BY 4.0</a> by the authors</p>
 
         <p>Template licensed under <a href="https://creativecommons.org/licenses/by-sa/4.0/" class="external-link">CC-BY 4.0</a> by <a href="https://carpentries.org/" class="external-link">The Carpentries</a></p>
-        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.7" class="external-link">sandpaper (0.16.7)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
+        <p>Built with <a href="https://github.com/carpentries/sandpaper/tree/0.16.8" class="external-link">sandpaper (0.16.8)</a>, <a href="https://github.com/carpentries/pegboard/tree/0.7.6" class="external-link">pegboard (0.7.6)</a>, and <a href="https://github.com/carpentries/varnish/tree/1.0.4" class="external-link">varnish (1.0.4)</a></p>
 			</div>
 		</footer></div> <!-- / div.container -->
 	<div id="to-top">
@@ -729,7 +729,7 @@ <h3 class="code-label">PYTHON<i aria-hidden="true" data-feather="chevron-left"><
   "identifier": "https://softwaresaved.github.io/fair-research-software/test-suite-exercise.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2024-09-26",
-  "datePublished": "2024-10-08"
+  "datePublished": "2024-10-14"
 }
 
   </script><script>