Move IO::Path stringification into own I/O section

Author: zoffixznet

doc/Language/traps.pod6

@@ -265,34 +265,6 @@ There are methods that Str inherits from Any that work on iterables like lists.
     say "cba".sort;              # OUTPUT: «(cba)␤» (what is wrong)
     say "cba".comb.sort.join;    # OUTPUT: «abc␤»
 
-=head2 IO::Path Stringification
-
-Partly for historical reasons and partly by design, an L<IO::Path> object
-L<stringifies|/type/IO::Path#method_Str> without considering its
-L«C<CWD> attribute|/type/IO::Path#attribute_CWD», which means if you L<chdir>
-and then stringify an L<IO::Path>, the resultant string won't reference
-the original filesystem object:
-
-=begin code
-    with 'foo'.IO {
-        .Str.say;       # OUTPUT: «foo␤»
-        .relative.say;  # OUTPUT: «foo␤»
-
-        chdir "/tmp";
-        .Str.say;       # OUTPUT: «foo␤»
-        .relative.say   # OUTPUT: «../home/camelia/foo␤»
-    }
-=end code
-
-The easy way to avoid this issue is to not stringify an L<IO::Path> object at all.
-Core routines that work with paths can take an L<IO::Path> object, so you don't
-need to stringify the paths.
-
-If you do have a case where you need a stringified version of an L<IO::Path>, use
-L<absolute> or L<relative> methods to stringify it into an absolute or relative
-path, respectively.
-
-
 =head1 Operators
 
 Some operators commonly shared among other languages were repurposed in Perl 6 for other, more common, things:
@@ -509,6 +481,35 @@ The nice thing about the distinction here is that it gives the developer the
 option of passing pairs as either named or positional arguments, which can be
 handy in various instances.
 
+=head1 Input and Output
+
+=head2 IO::Path Stringification
+
+Partly for historical reasons and partly by design, an L<IO::Path> object
+L<stringifies|/type/IO::Path#method_Str> without considering its
+L«C<CWD> attribute|/type/IO::Path#attribute_CWD», which means if you L<chdir>
+and then stringify an L<IO::Path>, the resultant string won't reference
+the original filesystem object:
+
+=begin code
+    with 'foo'.IO {
+        .Str.say;       # OUTPUT: «foo␤»
+        .relative.say;  # OUTPUT: «foo␤»
+
+        chdir "/tmp";
+        .Str.say;       # OUTPUT: «foo␤»
+        .relative.say   # OUTPUT: «../home/camelia/foo␤»
+    }
+=end code
+
+The easy way to avoid this issue is to not stringify an L<IO::Path> object at all.
+Core routines that work with paths can take an L<IO::Path> object, so you don't
+need to stringify the paths.
+
+If you do have a case where you need a stringified version of an L<IO::Path>, use
+L<absolute> or L<relative> methods to stringify it into an absolute or relative
+path, respectively.
+
 =head1 Exception Handling
 
 =head2 Sunk C<Proc>