Fix Oxford comma in join us page description

[joshjyu]

Fixes #8512

What changes did you make?

• Added an Oxford comma to the description in the join us page.

Why did you make the changes (we will use this info to test)?

• To ensure the website is uniform and uses the Oxford comma consistently.

CodeQL Alerts

After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.

Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown

Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.

• I have checked this PR for CodeQL alerts and none were found.
• I found CodeQL alert(s), and (select one):
  • I have resolved the CodeQL alert(s) as noted
  • I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
  • I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)

Instructions for resolving CodeQL alerts

If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.

In general, CodeQL alerts should be resolved prior to PR reviews and merging

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

Visuals before changes are applied

Visuals after changes are applied

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

---

From your project repository, check out a new branch and test the changes.

git checkout -b joshjyu-join-us-page-oxford-comma-8512 gh-pages
git pull https://github.com/joshjyu/website.git join-us-page-oxford-comma-8512

[egcuriel]

Review ETA: 05/27/2026 EOD
Availability: M-Sun (5 pm - 11 pm)

[egcuriel]

Hi @joshjyu!

It was good seeing you in the meeting earlier tonight!

Thank you for the added context regarding the Oxford comma consistency. I appreciate that you explained the intent behind the structural changes, as it provides a clear picture of the overall goal. I find understanding the motivation behind these updates incredibly useful.

I also appreciate you highlighting the changes in the text, as they can sometimes be tricky to spot in a large block. I’ve verified the updates across both desktop and mobile viewports.

As a next step, could you please add screenshots of the updated sections to the PR? It helps ensure the changes are documented in the PR record and makes it easier for the rest of the team to visualize the final result.

If you have any questions or need a hand with the markdown for the images, just let me know. I'm happy to help so we can keep moving forward with our skills issue!

[joshjyu]

As a next step, could you please add screenshots of the updated sections to the PR? It helps ensure the changes are documented in the PR record and makes it easier for the rest of the team to visualize the final result.

@egcuriel

thanks for the review.

There are already screenshots in my PR at the bottom. Please check those out.

[egcuriel]

Hi @joshjyu!

The images currently attached are cropped tightly to the text snippets. The PR template's visual documentation requirement helps show how the changes render within the overall website UI. Could you update these attachments with wider screenshots that show the full page layout?

[joshjyu]

Could you update these attachments with wider screenshots that show the full page layout?

The screenshots are updated as requested!

[egcuriel]

Hi @joshjyu

Thank you for showing the visual changes on the PR request. Everything looks good on my end!

Status: PR Approved

[ldaws003]

Review ETA: 5/30/2026
Availability: Saturday 2:00pm to 5:00pm

[ldaws003]

Good work. You forked the repo and made changes to your own branch. The branch name follows the required format, and your pull request message was well made. Approved