docs(readme): Improvements to Vercel deployment instructions

[DmGsOuNaK]

Description

Fixes #

Type of change

• Bug fix (added a non-breaking change which fixes an issue)
• New feature (added a non-breaking change which adds functionality)
• Updated documentation (updated the readme, templates, or other repo files)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

• Tested locally with a valid username
• Tested locally with an invalid username
• Ran tests with composer test
• Added or updated test cases to test new features

Checklist:

• I have checked to make sure no other pull requests are open for this issue
• The code is properly formatted and is consistent with the existing code style
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

Screenshots

[tranthaituananh]

@DenverCoder1 reviews it and I am having some difficulty, can you provide a quick way to contact you?

[DenverCoder1]

Thanks for contributing! 👍

Sorry for the delay in getting this review in. In the future, I recommend adding a detailed PR title and description that makes it clear what the purpose of the PR is. In general, it's best to avoid changing things that are not necessary to be changed but some of the changes you made I agree with. I hope it is fine that I made some adjustments and fixed the spacing.