Skip to content

Commit

Permalink
reword; fix broken L<>
Browse files Browse the repository at this point in the history
  • Loading branch information
zoffixznet committed Jun 6, 2017
1 parent b6507d5 commit 725cb4e
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions doc/Language/traps.pod6
Expand Up @@ -284,11 +284,11 @@ the original filesystem object:
}
=end code
The way to avoid this is first, to stop thinking about paths as strings. All
core routines that work with paths can take an L<IO::Path> object, so you don't
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
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.
Expand Down

0 comments on commit 725cb4e

Please sign in to comment.