summaryrefslogtreecommitdiff
path: root/pod/perlfaq6.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2002-03-22 13:30:38 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2002-03-22 13:30:38 +0000
commit5c5831a3a4d0f27f5e5fa1a5fecbc86bc6e75ee8 (patch)
tree43611012b4078000d00deed7b305ea90acaa8ace /pod/perlfaq6.pod
parente3ebf0f9310732e9e8d6d289c5325911e9798061 (diff)
downloadperl-5c5831a3a4d0f27f5e5fa1a5fecbc86bc6e75ee8.tar.gz
FAQ sync.
p4raw-id: //depot/perl@15415
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 dd76588ec0..c4512e695a 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<perlfaq4>: ``How do I determine whether a scalar is
+on the web'' and L<perfaq4>: ``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?