From e568dbe9d4576f3bb12ec38c9d2afe04e605ed06 Mon Sep 17 00:00:00 2001
From: Kim Brose <2803622+HarHarLinks@users.noreply.github.com>
Date: Wed, 15 Jan 2025 23:39:41 +0100
Subject: [PATCH 1/2] Clarify concerns will cancel FCP

---
 content/proposals.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/proposals.md b/content/proposals.md
index b58a98bee..0784da358 100644
--- a/content/proposals.md
+++ b/content/proposals.md
@@ -243,7 +243,8 @@ is as follows:
 -   A concern can be raised by a Spec Core Team member at any time,
     which will block an FCP from beginning. An FCP will only begin when
     75% of the members of the Spec Core Team agree on its outcome, and
-    all existing concerns have been resolved.
+    all existing concerns have been resolved. A concern raised during FCP will
+    cancel the FCP. The FCP will restart upon resolving the concern.
 -   The FCP will then begin and last for 5 days, giving anyone else some
     time to speak up before it concludes. If sufficient reasoning
     against the disposition is provided, a member of the Spec Core Team can

From 955355f42260b657af1b56d46b4d5e85caedbd27 Mon Sep 17 00:00:00 2001
From: Kim Brose <2803622+HarHarLinks@users.noreply.github.com>
Date: Wed, 15 Jan 2025 23:43:27 +0100
Subject: [PATCH 2/2] Create 2057.clarification

---
 changelogs/internal/newsfragments/2057.clarification | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 changelogs/internal/newsfragments/2057.clarification

diff --git a/changelogs/internal/newsfragments/2057.clarification b/changelogs/internal/newsfragments/2057.clarification
new file mode 100644
index 000000000..4c8eaee50
--- /dev/null
+++ b/changelogs/internal/newsfragments/2057.clarification
@@ -0,0 +1 @@
+Clarify that new concerns will cancel FCP. Contributed by @HarHarLinks.