Separate `nano` and `cat`, showing `nano`'s edits first

[martinosorb]

How could the content be improved?

It should first tell us what to edit with nano, and then suggest to use cat only after.

[CedricLeon]

I think the lesson must have evolved since 2024, but I agree that there is something to be improved on the first mention/interaction with nano and cat in episode 4. So, I preferred bumping the issue rather than opening a new one.

The "problem"

I feel like nano and cat are mentionned a little bit out of nowhere and they deserve to be introduced more properly because the learners will use these tools throughout the lesson. Currently, on the first nano mention there is already a link to the "Which Editor?" Unix Shell episode, but that's not explaining nano. cat is not introduced.

Proposed updates

So, I would propose to add a small sentence about both commands, and maybe a link back to the second "Setup" episode of the Git lesson, where it's explained why and how we can change the default text editor that Git uses (There is also a callout about exiting vim that can help learners figure out that exiting nano is also not straightforward).

About the added explanations, something along the lines:

nano opens a specified file in your current shell and allows you to edit it; the file is created if it does not exist. nano offers many shortcut available via the ^ (symbolizing Ctrl) key, for example to save and exit the editor you should use the sequence: Ctrl+X to exit, Y to save, and finally Enter to validate.

As for cat, maybe something simple like:

The cat commands print in the shell the content of a file. We can use it to visualize the 3 lines we added to guacamole.md.

[erinmgraham]

Hi @CedricLeon, thank you for the suggestions! This issue is a work in progress as you can see and your contribution is much appreciated. Can I ask you to create a pull request (PR) with your proposed changes?