NodeJS: Add descriptive link text

[guskirb]

Made changes to the links in the Express 102, 103, 104 and 105 lessons.

Because

Provide descriptive link text.

This PR

• Add descriptive link text to Express 102 lesson.
• Add descriptive link text to Express 103 lesson.
• Add descriptive link text to Express 104 lesson.
• Add descriptive link text to Express 105 lesson.

Issue

Related to #27819

Additional Information

Pull Request Requirements

• I have thoroughly read and understand The Odin Project curriculum contributing guide
• The title of this PR follows the location of change: brief description of change format, e.g. Intro to HTML and CSS lesson: Fix link text
• The Because section summarizes the reason for this PR
• The This PR section has a bullet point list describing the changes in this PR
• If this PR addresses an open issue, it is linked in the Issue section
• If any lesson files are included in this PR, they have been previewed with the Markdown preview tool to ensure it is formatted correctly
• If any lesson files are included in this PR, they follow the Layout Style Guide

[MaoShizhong]

Thanks for sorting out these links, @guskirb!

Would you be good to fix up the remaining lint errors? If you follow the curriculum repo contributing guide, it'll show you how to run lint checks and fixes locally.

Most of the lint errors should be fixable by running the correct script on a file (project_express_105 will need the project scripts, not the lesson scripts). There will be a couple that can't be auto-fixed so will need manually fixing (the error message should be somewhat self explanatory).

For the "Required heading structure" error in express_103_crud_and_mvc.md line 62, that should be fixed by removing the s from Knowledge checks to make Knowledge check.

You can ignore the "Required heading structure" error for express_104_view_templates.md.

Let me know if you run into any issues with this.

[MaoShizhong]

Small side note - I suspect you may have a formatter like Prettier that runs on save, as the project 105 file had its * * emphasis (which is what we want) switched to _ _ (which is not what we want). I'd recommend finding the keybinding for Save without formatting and getting used to using that when working on any external projects, as you can't guarantee they will use the same style guide as the formatter you have running automatically. Alternatively, you can have it so your formatter does not run on save but instead is bound to a separate keybinding. Then you just only use that when working on projects you know are fine to use your formatter with.

[guskirb]

Small side note - I suspect you may have a formatter like Prettier that runs on save, as the project 105 file had its * * emphasis (which is what we want) switched to _ _ (which is not what we want). I'd recommend finding the keybinding for Save without formatting and getting used to using that when working on any external projects, as you can't guarantee they will use the same style guide as the formatter you have running automatically. Alternatively, you can have it so your formatter does not run on save but instead is bound to a separate keybinding. Then you just only use that when working on projects you know are fine to use your formatter with.

I've fixed the lint errors.

I did have prettier set to reformat on save, which I've changed, thanks for letting me know.

[MaoShizhong]

Suggested change

	CRUD stands for: <span id="crud">*Create, Read, Update* and *Delete*</span>. These are the four basic functions that you will be building into your database driven apps. If you are designing a CRUD interface that means that users can expect to be able to do these 4 things to items in the database (providing they have the appropriate permissions of course).
	CRUD stands for: *Create, Read, Update* and *Delete*. These are the four basic functions that you will be building into your database driven apps. If you are designing a CRUD interface that means that users can expect to be able to do these 4 things to items in the database (providing they have the appropriate permissions of course).

Not something you've made but I just noticed that we have a redundant span here, as the ### CRUD heading itself directly above already generates an h3#crud, so the span isn't actually needed for scroll either (since it's not like it's a long way away from the heading). Mind removing it while we're at it?

Everything else looks 👨‍🍳 🤌

[guskirb]

Done!

[MaoShizhong]

🚀