diff --git a/peps/pep-0750.rst b/peps/pep-0750.rst
index a5ae87b3104..03dfc932c3d 100644
--- a/peps/pep-0750.rst
+++ b/peps/pep-0750.rst
@@ -736,12 +736,12 @@ Consumers can look at tag strings as starting from f-strings:
 
 - They look familiar
 - Scoping and syntax rules are the same
-- You just need to import the tag function
 
 They first thing they need to absorb: unlike f-strings, the string isn't
 immediately evaluated "in-place". Something else (the tag function) happens.
 That's the second thing to teach: the tag functions do something particular.
-Thus the concept of "domain specific languages" (DSLs).
+Thus the concept of "domain specific languages" (DSLs). What's extra to
+teach: you need to import the tag function before tagging a string.
 
 Tag function authors think in terms of making a DSL. They have
 business policies they want to provide in a Python-familiar way. With tag
@@ -751,10 +751,6 @@ the bar for making a DSL.
 Tag authors can begin with simple use cases. After authors gain experience, tag strings can be used to add larger
 patterns: lazy evaluation, intermediate representations, registries, and more.
 
-Finally, framework authors can provide contact points with their lifecycles.
-For example, decorators which tag function authors can use to memoize
-interpolations in the function args.
-
 Each of these points also match the teaching of decorators. In that case,
 a learner consumes something which applies to the code just after it. They
 don't need to know too much about decorator theory to take advantage of the