Give authors a choice whether to move their explainer into their spec.

Co-authored-by: Daniel Appelquist <dan@torgo.com>

Author: jyasskin

index.bs

@@ -53,9 +53,9 @@ Follow the [tips](#tips) below to make your explainer as effective as possible.
 Once there is a reasonable amount of consensus on the approach and high-level design,
 use the explainer to guide spec writing.
 Start your specification using whatever tool you prefer
-(e.g. [Bikeshed](https://speced.github.io/bikeshed/) or [Respec](https://respec.org/)),
-and then move (don't copy) sections from your explainer into the specification.
-Be sure to leave links from the now-empty explainer sections
+(e.g. [Bikeshed](https://speced.github.io/bikeshed/) or [Respec](https://respec.org/)).
+You may want to move (not copy) sections from your explainer into the specification as you write it.
+If you do, be sure to leave links from the now-empty explainer sections
 to the specification sections that received their content.
 
 As your specification evolves,