Update docs/community/sep-guidelines.mdx

Co-authored-by: Paul Carleton <[email protected]>

Author: dsp-ant

docs/community/sep-guidelines.mdx

@@ -42,7 +42,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
-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
+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
 5. The SEP may be accepted, rejected, or returned for revision.