Rails basics : Change link texts

[forge34]

Because

Change link text in some lessons in rails basics

This PR

• Routing lesson : change link text in line 212
• Blog app project : change link text in line 25
• Deployment lesson : change link text in lines 107 ,108 ,127 ,128 , 147 , 148 ,168 and 169

Issue

Related to #28290

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 getting these links sorted, @forge34.

Would you also be happy to fix the lint errors in routing and project_blog_app?
You should be able to sort most if not all of the errors in those files by following our local linting and fixing instructions, using the appropriate lesson/project scripts.

If you run into any issues with this, or there are any unfixable lint errors that need context-based manual fixing, let me know.

[forge34]

Thanks for getting these links sorted, @forge34.

Would you also be happy to fix the lint errors in routing and project_blog_app? You should be able to sort most if not all of the errors in those files by following our local linting and fixing instructions, using the appropriate lesson/project scripts.

If you run into any issues with this, or there are any unfixable lint errors that need context-based manual fixing, let me know.

sure : )
just to make sure i can either use option 1 or 2 , or just option 2? from the link

edit : i used option 2 , seems to be done : ) i think

[MaoShizhong]

🚀

Like with eslint/prettier, the VSCode extension just makes things more convenient by showing live error highlighting etc.
The best thing for actually seeing lint error details and fixing is to use the npm package and our scripts. So I handle large quantities of lint issues via the the npm scripts, but also have the extension because it makes things convenient when you're making changes, as you see squigglies in real-time.

[forge34]

🚀

Like with eslint/prettier, the VSCode extension just makes things more convenient by showing live error highlighting etc. The best thing for actually seeing lint error details and fixing is to use the npm package and our scripts. So I handle large quantities of lint issues via the the npm scripts, but also have the extension because it makes things convenient when you're making changes, as you see squigglies in real-time.

i see , from now on i have the extension and will continue using the npm scripts to fix and check if there is any errors