summaryrefslogtreecommitdiff
path: root/pod/perlfaq6.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2002-03-20 01:17:27 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2002-03-20 01:17:27 +0000
commit23039c1f8de5a3b99d1131da9e0fcd1b09504d49 (patch)
treee8f9c7592298619dcf9cfa620a41208a48ee43e6 /pod/perlfaq6.pod
parentb2deec1dd027f4c2aeb4cf477b403374906455ae (diff)
downloadperl-23039c1f8de5a3b99d1131da9e0fcd1b09504d49.tar.gz
Tpo.
p4raw-id: //depot/perl@15353
Diffstat (limited to 'pod/perlfaq6.pod')
-rw-r--r--pod/perlfaq6.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlfaq6.pod b/pod/perlfaq6.pod
index c4512e695a..dd76588ec0 100644
--- a/pod/perlfaq6.pod
+++ b/pod/perlfaq6.pod
@@ -9,7 +9,7 @@ littered with answers involving regular expressions. For example,
decoding a URL and checking whether something is a number are handled
with regular expressions, but those answers are found elsewhere in
this document (in L<perlfaq9>: ``How do I decode or create those %-encodings
-on the web'' and L<perfaq4>: ``How do I determine whether a scalar is
+on the web'' and L<perlfaq4>: ``How do I determine whether a scalar is
a number/whole/integer/float'', to be precise).
=head2 How can I hope to use regular expressions without creating illegible and unmaintainable code?