refer to PMC - not PPMC (#132)

content/how-to-contribute.html

@@ -209,8 +209,8 @@ <h2><a href="#code-of-conduct" name="code-of-conduct" class="anchor"><span class
 <p>Please see the Apache wide <a href="https://www.apache.org/foundation/policies/conduct">Code of Conduct</a>.</p>
 <h2><a href="#committers" name="committers" class="anchor"><span class="anchor-link"></span></a>Committers</h2>
 <p>The current list of Apache Pekko committers can be found in the Apache <a href="https://people.apache.org/phonebook.html?pmc=pekko">Phonebook</a>.</p>
-<p>All code merges require approval from at least 1 Pekko committer. Most Pekko committers are also members of the PPMC. Releases require that at least 3 Pekko PPMC members approve the release.</p>
-<p>We are looking to build up the number of committers and PPMC members. We will invite people to join the team. This is based on meritocracy. Contributors who have become involved in the Pekko community and who have shown a good level of understanding of the Pekko code base will be considered. We have an outline of the process for becoming a committer on the Apache Pekko project on our <a href="https://cwiki.apache.org/confluence/display/PEKKO/Becoming+a+Committer">wiki</a>.</p>
+<p>All code merges require approval from at least 1 Pekko committer. Most Pekko committers are also members of the PMC. Releases require that at least 3 Pekko PMC members approve the release.</p>
+<p>We are looking to build up the number of committers and PMC members. We will invite people to join the team. This is based on meritocracy. Contributors who have become involved in the Pekko community and who have shown a good level of understanding of the Pekko code base will be considered. We have an outline of the process for becoming a committer on the Apache Pekko project on our <a href="https://cwiki.apache.org/confluence/display/PEKKO/Becoming+a+Committer">wiki</a>.</p>
 <p>Code reviews and votes on releases can be made by anyone.</p>
 </div>
 </article>