Building your resume updates

[BryanF1nes]

Because

This PR addresses an issue request that was created to enhance the resume project within the getting hired section. It's purpose is to give additional information on how the hiring managers and recruiters review resumes and how we can leverage that information to create a better resume.

This PR

• Updated layout to better align with the lesson project template.
• Included an additional resource walks individuals through creating a resume (directly from an active recruiter in tech).
• Included additional paragraphs to define how hiring managers and recruiters review resumes and how we can leverage that.
• Fixed miscellaneous grammatical errors and spelling errors.

Issue

Closes #30259

Additional Information

N/A

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

[mao-sz]

I wouldn't be the most appropriate to review the contents of this PR/lesson but a couple of comments.

@BryanF1nes:

• Our headings need to be in sentence case instead of title case.
• I'd want to look at the "optional reading" section and consider if that's something that's worth integrating into the main lesson content/assignment itself, or if it can be dropped given the scope of the lesson and the existing content. It's basically and "Additional resource" but not by that name (heading structure not carried over).

For whoever reviews this in more depth, I wonder if this is actually appropriate as a project. I'm not seeing anything particularly project-y about this contents, and so it may be best converted to a lesson, which would mean adding "Lesson overview" and "Knowledge check" sections as appropriate, changing the name of this file, then going to the website repo to change the appropriate details in the db fixtures.