python/psrt repository isn't automatically synced

Author: sethmlarson

peps/pep-0811.rst

@@ -40,7 +40,7 @@ involved in the remediation of the vulnerability at hand.
 
 The historical approach to collaboration on patch development was to manually
 add GitHub users to a private ``python/psrt`` repository
-which was an automatically synced mirror of the ``python/cpython`` repository.
+which is a mirror of the ``python/cpython`` repository.
 This approach didn't allow filtering particular collaborators for specific
 vulnerabilities, meaning all collaborators had access to all reports and patches.
 
@@ -304,7 +304,7 @@ For this reason, the mailing list and PSRT GPG key will continue to function
 and be monitored, but reporters will be directed to individual project GitHub
 Security Advisory forms for submitting vulnerability reports.
 
-Rejected ideas
+Rejected Ideas
 ==============
 
 Should inactive members be more aggressively pruned?