From: Piotr Fusik <pfusik@op.pl>
Date: Sun, 24 Jul 2005 12:55:09 +0000 (+0200)
Subject: perlfunc.pod: s/definetely/definitely/
X-Git-Tag: accepted/trunk/20130322.191538~20044
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2e98ff8bbc77b3356fd04714206897c36f3e6015;p=platform%2Fupstream%2Fperl.git

perlfunc.pod: s/definetely/definitely/
From: "Piotr Fusik" <pfusik@op.pl>
Message-ID: <004e01c5903e$2affb3a0$60d24dd5@piec>

p4raw-id: //depot/perl@25219
---

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 394153c..43dc07b 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -3707,7 +3707,7 @@ binary representation (e.g. IEEE floating point format).  Even if all
 platforms are using IEEE, there may be subtle differences.  Being able
 to use C<E<gt>> or C<E<lt>> on floating point values can be very useful,
 but also very dangerous if you don't know exactly what you're doing.
-It is definetely not a general way to portably store floating point
+It is definitely not a general way to portably store floating point
 values.
 
 When using C<E<gt>> or C<E<lt>> on an C<()>-group, this will affect