replaces 2 instances of Github with GitHub on line 24

[coding-yost]

Fixes #7438

What changes did you make?

• replaced 2 instances of Github with GitHub on line 24

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

• To ensure company name is presented properly

• For Reviewers: Do not review changes locally, rather, review changes at https://github.com/coding-yost/website/blob/Replace-Github-with-GitHub-in-CONTRIBUTING.md-Table-of-Contents-1.4.c/CONTRIBUTING.md

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

![image]

Visuals after changes are applied

![image]

[github-actions]

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

---

Note that CONTRIBUTING.md cannot previewed locally; rather it should be previewed at this URL:

https://github.com/coding-yost/website/blob/Replace-Github-with-GitHub-in-CONTRIBUTING.md-Table-of-Contents-1.4.c/CONTRIBUTING.md  

[Cloid]

Review ETA: EOD 2/22/25
Availability: 5-8 PM Weekdays

[gmgonzal]

Review ETA: 4p 2/17/25
Availability: 9a-4p 2/17/25

[gmgonzal]

Hi @coding-yost, thank you for working on this issue. Your changes look good!

Things You Did Well:

• Step 0: PR is done with the correct branch.
  • Issue title looks good.
  • PR description looks good.
• Step 1: PR links to the correct issue #7438.
• Step 2: Changes appear to address the issue action items.
• Step 3: Website page looks good on the browser.
• Step 4: Source code changes look good.
• Step 5: No other issues seen.

PR is approved, well done :)

[iancooperman]

ETA: Fri, 2/21
Availability: 5-9pm Weekdays

[iancooperman]

Hi @coding-yost,

Great job on this!

• All requested changes have been made without anything out of scope.
• Action items on the original issue are properly checked off.

Just a quick note for the future:

• The branch title was appropriately named, but remember to include the issue number at the end next time (e.g., coding-yost:Replace-Github-with-GitHub-in-CONTRIBUTING.md-Table-of-Contents-1.4.c-7438).

Overall, everything looks solid. Nice work! Approved.

[t-will-gillis]

Hey @coding-yost Just a minor note: you don't need to assign yourself to the PR. Also, for the next one, please be sure to remove excess lines for example in "What changes did you make?" Otherwise, looks good, thanks!