From 45eb70cd34b86457804bd48d612463fc57b26c45 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Wed, 13 Mar 2024 11:21:33 -0400 Subject: [PATCH] Fix typos Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> --- content/proposals.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/proposals.md b/content/proposals.md index 374a0010..b58a98be 100644 --- a/content/proposals.md +++ b/content/proposals.md @@ -381,7 +381,7 @@ of the MSC working in order for it to move into FCP. This can usually be a branch/pull request to whichever implementation of choice that proves the MSC works in practice, though in some cases the MSC itself will be small enough to be considered proven. Implementations do not need to be -merged no released, but must be of sufficient quality to show that the +merged or released, but must be of sufficient quality to show that the MSC works. Where it's unclear if an MSC will require an implementation proof, ask in [\#matrix-spec:matrix.org](https://matrix.to/#/#matrix-spec:matrix.org). Proposals may require both server-side and client-side implementations. @@ -390,7 +390,7 @@ Proposals that have not yet been implemented will have the `needs-implementation` label. After an implementation has been made, add a comment in the GitHub issue indicating so. After an implementation has been made, we will check it to verify that it implements the MSC. Proposals that -have implementations that we have not yet been checked will have the +have implementations that have not yet been checked will have the `implementation-needs-checking` label. ### Early release of an MSC/idea