docs: update wording for code freeze

[aljo242]

The worked example carried "a vulnerability" through every verb, so it read as the vulnerability being frozen and coming down. The dates belong to the repositories.

[greptile-apps]

Confidence Score: 4/5

[Low risk] Clarifies vulnerability disclosure timeline in security policy.

The PR should not merge until the example distinguishes public patches from the private repositories that remain available temporarily.

Findings

1.  Private repositories do not go public ▶

Summary

The PR rewords the August vulnerability example so repositories, rather than the vulnerability, are described as freezing and coming down. The revised sentence also incorrectly says the private repositories go public.

_{Reviews (1) · Last reviewed commit: "docs: let the repositories freeze, not t..."}

[greptile-apps]

Private repositories do not go public The new sentence says the private repositories go public on September 1. The policy instead says their patches are merged into public repositories on that date, while the private repositories remain available to invited teams until September 15. Readers could mistake this for a change to who can access the private repositories.

Suggested change

	August 25, go public on September 1, and come down on September 15.
	August 25; their patches go public on September 1, and the private repositories come down on September 15.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!