docs: clarify README feedback prompt

[k11kirky]

Problem

The README feedback prompt can read more naturally. This is a test PR for validating the contribution workflow.

Changes

• Clarify the wording of the README feedback prompt.

How did you test this?

• git diff --check

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

[k11kirky]

This is a documentation-only test PR. It updates one sentence in the root README from ‘Found a bug or have feedback?’ to ‘Found a bug or want to share feedback?’ so the invitation reads more naturally. There are no functional changes; the diff was checked with git diff --check.

[github-actions]

This PR has had no activity for 7 days and has been marked stale. We are moving to the monorepo and tightening PR staleness in preparation, so it will be closed in 7 days if no further activity occurs.

[charlesvien]

Hey @k11kirky, we've migrated this repo into the PostHog/posthog monorepo, so this PR needs to be recreated there.

Easiest path: check out the monorepo and run the /porting-code-prs skill with your agent pointed at this PR. It has the migration guide and path remappings baked in so the agent doesn't have to figure them out. You don't strictly need it though, just asking your agent to port the PR works fine too.

Shout if you get stuck.

[charlesvien]

Ported to the monorepo as PostHog/posthog#76806