From 07f80cab3b4b5c80491f62e4b9c8b5d5b1058bad Mon Sep 17 00:00:00 2001
From: Jamie <2119834+jamieQ@users.noreply.github.com>
Date: Mon, 27 Oct 2025 12:24:11 -0500
Subject: [PATCH] [chore]: make full-qualification suppression text better
 match implementation

clarify that the full qualification method of suppression does not require _all_ types to be fully qualified, just the protocol types to which the nominal type is conforming via the extension.
---
 proposals/0364-retroactive-conformance-warning.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/proposals/0364-retroactive-conformance-warning.md b/proposals/0364-retroactive-conformance-warning.md
index 6300d01b9e..1ee0161dde 100644
--- a/proposals/0364-retroactive-conformance-warning.md
+++ b/proposals/0364-retroactive-conformance-warning.md
@@ -113,11 +113,11 @@ use `@retroactive` outside of the declaration of a retroactive conformance.
 `@retroactive` is a new attribute, but it is purely additive; it can be accepted
 by all language versions. It does mean projects building with an older Swift
 will not have access to this syntax, so as a source compatible fallback,
-a client can silence this warning by fully-qualifying all types in the extension.
+a client can silence this warning by fully-qualifying all protocol types in the extension.
 As an example, the above conformance can also be written as
 
 ```swift
-extension Foundation.Date: Swift.Identifiable {
+extension Date: Swift.Identifiable {
     // ...
 }
 ```