correct Oxford comma on Projects page

[anthonylo87]

Fixes #8510

What changes did you make?

• Update main paragraph text on Projects page to use Oxford comma

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

• This change was made to maintain consistency with the rest of the H4LA website, which uses Oxford commas.

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

Mobile:

Desktop:

Visuals after changes are applied

Mobile:

Desktop:

[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 anthonylo87-fix-oxford-comma-8510 gh-pages
git pull https://github.com/anthonylo87/website.git fix-oxford-comma-8510

[egcuriel]

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

[egcuriel]

Hi @anthonylo87!

I have reviewed this pull request and verified the following:

PR Verification:

✓ Pull Request uses the correct branch

✓ Original issue is linked

✓ Screenshots included (before and after)

Technical Verification:

✓ Issue requirements are addressed correctly

✓ Changes are accurately represented locally across both viewports (desktop and mobile)

✓ No new console errors or warnings present

✓ No unresolved CodeQL alerts

Notes:

Thank you for attaching both mobile and desktop screenshots!

I recently learned that Chrome Dev Tools has this function that lets you capture a screenshot as if you're taking it on your mobile device (I've attached a screenshot of the menu item below in case it helps)

Chrome Dev Tools capture mobile screenshot function

Status: PR Approved!

[anthonylo87]

Thank you @egcuriel! That's a neat trick to take screenshots of the mobile view - will definitely use that going forward!