Expand on editing index.md in Episode 2

[alex-ball]

Given we have recommended Nano as core editor, it would be good to practise using it to edit index.md. I suspect most Instructors would do this anyway.

Breaking this step down into several paragraphs should make it less overwhelming.

To make the step portable to Nano, I think we should include an instruction to close the file. It will also help declutter when using other editors, since we don't edit the file again for a while.

Closes #124.

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/LibraryCarpentry/lc-git/compare/md-outputs..md-outputs-PR-194

The following changes were observed in the rendered markdown documents:

 02-getting-started.md | 33 +++++++++++++++++++++++++++------
 md5sum.txt            |  2 +-
 2 files changed, 28 insertions(+), 7 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-11-27 17:11:56 +0000

[srerickson]

looks good!