fixups

Author: dsp-ant

docs/community/governance.mdx

@@ -56,7 +56,7 @@ MCP has two lead maintainers: Justin Spahr-Summers and David Soria Parra. Lead M
 
 The Lead Maintainers are responsible for confirming or removing core maintainers.
 
-Lead Maintainers are administrators on all infrastructure for the MCP project where possible. This includes but is not restricted to all communication channels, Github organizations and repositories.
+Lead Maintainers are administrators on all infrastructure for the MCP project where possible. This includes but is not restricted to all communication channels, GitHub organizations and repositories.
 
 ### Decision Process
 
@@ -104,7 +104,7 @@ Core maintainers and maintainers are encouraged to improve any part of the MCP p
 
 #### Specification Enhancement Proposal (SEP)
 
-Proposed changes to the specification must come in the form of a written version, starting with a summary of the proposal, outlining the **problem** it tries to solve, propose **solution**, **alternatives**, **considerations, outcomes** and **risks**. The [SEP Guidelines](/community/sep-guidelines) outline information on the expected structure of SEPs. SEP's are should be created as issues in the [specification repository](https://github.com/modelcontextprotocol/specification) and tagged with the labels `proposal, sep`.
+Proposed changes to the specification must come in the form of a written version, starting with a summary of the proposal, outlining the **problem** it tries to solve, propose **solution**, **alternatives**, **considerations, outcomes** and **risks**. The [SEP Guidelines](/community/sep-guidelines) outline information on the expected structure of SEPs. SEP's should be created as issues in the [specification repository](https://github.com/modelcontextprotocol/specification) and tagged with the labels `proposal, sep`.
 
 All proposals must have a **sponsor** from the MCP steering group (maintainer, core maintainer or lead core maintainer). The sponsor is responsible for ensuring that the proposal is actively developed, meets the quality standard for proposals and is responsible for presenting and discussing it in meetings of core maintainers. Maintainer and Core Maintainer groups should review open proposals without sponsors in regular intervals. Proposals that do not find a sponsor within six months are automatically rejected.
 

docs/community/sep-guidelines.mdx

@@ -41,7 +41,7 @@ SEPs should be submitted as a GitHub Issue in the [specification repository](htt
 
 The standard SEP workflow is:
 
-1. You, the SEP author, fork the MCP repository and create a well-formatted GitHub Issue with the proposal and SEP tags
+1. You, the SEP author, create a well-formatted GitHub Issue with the proposal and SEP tags
 2. Find a Core Maintainer or Maintainer to sponsor your proposal. Core Maintainers and Maintainers will regularly go over the list of open proposals to determine which proposals to sponsor. Once a sponsor is found, the sponsor is "assigned" to the issue and a milestone is assigned. The tag `draft` is added. At this point a unique SEP number is assigned.
 3. The sponsor will review and may request changes before formal review, based on community feedback. Once ready for review, the tag `in-review` is added.
 4. Once sponsored, the SEP enters formal review by the core team