Move comments outside note boxes.

The RST-to-markdown exporter had some special cases and some issues
here, because RST and DocC-flavored markdown have different rules around
what block level constructs can nest.  Avoiding the nesting is the best
option, when that's feasible.

Author: amartini51

Sources/TSPL/TSPL.docc/LanguageGuide/Concurrency.md

@@ -316,19 +316,18 @@ you'll get compile-time error instead of introducing a bug.
 >     return ["IMG001", "IMG99", "IMG0404"]
 > }
 > ```
-> 
-> 
-> <!--
-  > - test: `sleep-in-toy-code`
-  > 
-  > ```swifttest
-  > >> struct Data {}  // Instead of actually importing Foundation
-  > -> func listPhotos(inGallery name: String) async throws -> [String] {
-  >        try await Task.sleep(until: .now + .seconds(2), clock: .continuous)
-  >        return ["IMG001", "IMG99", "IMG0404"]
-  > }
-  > ```
-> -->
+
+<!--
+  - test: `sleep-in-toy-code`
+
+  ```swifttest
+  >> struct Data {}  // Instead of actually importing Foundation
+  -> func listPhotos(inGallery name: String) async throws -> [String] {
+         try await Task.sleep(until: .now + .seconds(2), clock: .continuous)
+         return ["IMG001", "IMG99", "IMG0404"]
+  }
+  ```
+-->
 
 <!--
   TODO either add an example or maybe a short section

Sources/TSPL/TSPL.docc/LanguageGuide/Protocols.md

@@ -2707,12 +2707,12 @@ print(differentNumbers.allEqual())
 > Note: If a conforming type satisfies the requirements for multiple constrained extensions
 > that provide implementations for the same method or property,
 > Swift uses the implementation corresponding to the most specialized constraints.
-> 
-> <!--
-  > TODO: It would be great to pull this out of a note,
-  > but we should wait until we have a better narrative that shows how this
-  > works with some examples.
-> -->
+
+<!--
+  TODO: It would be great to pull this out of a note,
+  but we should wait until we have a better narrative that shows how this
+  works with some examples.
+-->
 
 <!--
   TODO: Other things to be included