Make blocked user info more consice

[SollyBunny]

The issue for this would be the same as the PR and take longer

Combined you no longer x's on users and users on longer x's on a into one phrase using eachother. This happens to contribution counting and colaborator status. I then put these next to eachother.

I'm not sure if I can use collaborator status since it's not used elsewhere, it would make it easier to read in my opion rather than You are removed as collaborators from

I am also not sure if I can change counted as contributions to just counted, I initally wanted to change it to counted on eachothers' profiles since I wasn't aware of anywhere else contributions were counted

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
  - [ ] All CI checks are passing and the changes look good in the review environment. Wording change

[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]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md	fpt ghec	fpt ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@SollyBunny Thanks for opening a PR! I'm afraid, though, that you're sacrificing clarity for being concise, and that is absolutely not what we want to do in any documentation about safety. Clarity is the top priority. We're not going to accept this PR, but we do have a help wanted tag in the issues if you're looking to make a contribution. A lot of articles beginning with "about" (About projects, for example) could also be much more concise, if that's the kind of editing you're specifically looking to do. ✨