Update reporting abuse or spam

[avalonv]

Why:

Closes #20202

What's being changed (if available, include any code snippets, screenshots, or gifs):

Provide a tip clarifying users can report comments that violate community guidelines without being a contributor.

Check off the following:

• I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
• For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

• This pull request impacts the contribution experience
  • I have added the 'writer impact' label
  • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md	fpt ghec	fpt ghec

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server
ghae: GitHub AE

[cmwilson21]

@avalonv Thanks for opening an issue and PR! I've slightly edited your post to link the PR to your issue.

I'll get this triaged for review! ⚡

[jules-p]

Hi @avalonv 👋 thank you for raising this PR. The information that's been added already exists elsewhere within the article, so I'm going to close this for now. I've added some guidance in the linked issue for how to address the issue in alignment with our content model.

Thank you so much for your interest and dedication in improving the docs. ✨