Update docs/community/governance.mdx

Co-authored-by: Tadas Antanavicius <[email protected]>

Author: dsp-ant

docs/community/governance.mdx

@@ -12,7 +12,7 @@ The MCP project adopts a hierarchical structure, similar to Python, PyTorch and
 - A community of **contributors** who file issues, make pull requests, and contribute to the project.
 - A small set of **maintainers** drive components within the MCP project, such as SDKs, documentation and others.
 - They are overseen by **core maintainers**, who drive the overall project direction.
-- The core maintainers have two **lead core maintainers** who are the catch-all decision maker.
+- The core maintainers have two **lead core maintainers** who are the catch-all decision makers.
 - Maintainers, core maintainers and lead core maintainers form the **MCP steering group**.
 
 All maintainers are expected to have a strong bias towards MCP's design philosophy. Membership in the technical governance process is for individuals, not companies. That is, there are no seats reserved for specific companies, and membership is associated with the person rather than the company employing that person. This ensures that maintainers act in the best interests of the protocol itself and the open source community.