docs: fix Title Case heading and blockquote spacing in CONTRIBUTING.md (#7104)

[amir-rezaei]

Description

This PR fixes section heading Title Case capitalization and blockquote syntax spacing in CONTRIBUTING.md.

Details

1. Capitalized section header (### What is a verified connector? -> ### What Is a Verified Connector?).
2. Added space after blockquote marker (>To be eligible -> > To be eligible).

Issues

close #7104

[filigran-cla-bot]

Contributor License Agreement

✅ CLA signed 💚

Thank you @amir-rezaei for signing the Contributor License Agreement! Your pull request can now be reviewed and merged.

We appreciate your contribution to Filigran's open source projects! ❤️

_{This is an automated message from the Filigran CLA Bot.}

[Copilot]

Pull request overview

This PR makes small Markdown formatting fixes in CONTRIBUTING.md to improve readability and consistency in rendered documentation.

Changes:

• Updated a section heading to Title Case (“What Is a Verified Connector?”).
• Fixed blockquote syntax by adding a space after the > marker.

[Filigran-Automation]

🤖 [AI-generated]

Hey @amir-rezaei! 👋 Thanks a lot for opening PR #7099 — really appreciate you cleaning up the CONTRIBUTING.md formatting! 🙏

I just had a quick look and I think the description could be enhanced a little to help reviewers get through it faster. I haven't changed anything in your description — just a gentle suggestion:

Area	What could help	Suggestion
Related issues	No linked issue is referenced anywhere in the PR body or title	This repo's CONTRIBUTING.md asks that every PR be submitted together with an associated GitHub issue describing the problem/improvement, referenced with the "Close #123" keyword. Could you open (or link) the corresponding issue and add a "Related issues" section referencing it?

💡 If helpful, the contribution guidelines and the PR template walk through what to include.

No rush at all — thanks again for contributing to the project! 🚀

[Powlinett]

Hi @amir-rezaei 👋 thanks for your first contribution 🎉

I linked your PR to the corresponding issue ✅️

Please sign all your commits so we can merge your PR 😇

If you don't know how to sign them, may I suggest the following steps:

1. Pull the latest version of master
2. Rebase your branch on the updated master
3. Sign all your commits to enable merging (see links below)
4. git push --force to rewrite your PR's commits history

(It might be easier to do with a Git GUI client)

How to sign old commits:
• https://superuser.com/questions/397149/can-you-gpg-sign-old-commits
• https://stackoverflow.com/questions/41882919/is-there-a-way-to-gpg-sign-all-previous-commits
• https://medium.com/@aamir.shehzad3346875/how-to-sign-previous-commit-that-have-already-been-pushed-4683a7060e19