needless repetition

Author: tshepang

src/implementing_new_features.md

@@ -40,10 +40,10 @@ without an FCP for compiler development or standard library use,
 as long as you don't expect them to be in wide use in the nightly ecosystem.
 Some teams have lighter weight processes that they use in scenarios like this;
 for example,
-the compiler team recommends filing a Major Change Proposal ([MCP][mcp])
+the compiler team recommends filing a Major Change Proposal ([MCP])
 as a lightweight way to garner support and feedback without requiring full consensus.
 
-[mcp]: https://forge.rust-lang.org/compiler/proposals-and-stabilization.html#how-do-i-submit-an-mcp
+[MCP]: https://forge.rust-lang.org/compiler/proposals-and-stabilization.html#how-do-i-submit-an-mcp
 
 You don't need to have the implementation fully ready for r+ to propose an FCP,
 but it is generally a good idea to have at least a proof of concept