summaryrefslogtreecommitdiff
path: root/pod/perlhack.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2001-05-27 00:28:34 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2001-05-27 00:28:34 +0000
commit3958b146226a1f41d96ef1aa1e0dde87d11c5498 (patch)
tree5d00d3c47e442c5ae89229cff7122c09ce745d96 /pod/perlhack.pod
parent36f65ada8976e23c1222137b59696bff2b63e8f6 (diff)
downloadperl-3958b146226a1f41d96ef1aa1e0dde87d11c5498.tar.gz
[ID 20010525.001] Pod typo nits fixed
From: lvirden@cas.org Date: Fri, 25 May 2001 06:57:43 -0400 (EDT) Message-Id: <200105251057.f4PAvhY13003@lwv26awu.cas.org> minus the perlsolaris decimation plus the Subject: Re: [ID 20010525.001] Pod typo nits fixed From: "Philip Newton" <Philip.Newton@gmx.net> Date: Fri, 25 May 2001 18:05:55 +0200 Message-Id: <200105251604.f4PG4kt15034@chaos.wustl.edu> p4raw-id: //depot/perl@10226
Diffstat (limited to 'pod/perlhack.pod')
-rw-r--r--pod/perlhack.pod10
1 files changed, 5 insertions, 5 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 94c6dfd96b..6b67e5706b 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -273,7 +273,7 @@ From http://rsync.samba.org/README.html:
"Rsync uses rsh or ssh for communication. It does not need to be
setuid and requires no special privileges for installation. It
- does not require a inetd entry or a deamon. You must, however,
+ does not require an inetd entry or a daemon. You must, however,
have a working rsh or ssh system. Using ssh is recommended for
its security features."
@@ -434,7 +434,7 @@ look how others apply the fix.
=item Finding the source of misbehaviour
When you keep in sync with bleadperl, the pumpking would love to
-I<see> that the community efforts realy work. So after each of his
+I<see> that the community efforts really work. So after each of his
sync points, you are to 'make test' to check if everything is still
in working order. If it is, you do 'make ok', which will send an OK
report to perlbug@perl.org. (If you do not have access to a mailer
@@ -442,7 +442,7 @@ from the system you just finished successfully 'make test', you can
do 'make okfile', which creates the file C<perl.ok>, which you can
than take to your favourite mailer and mail yourself).
-But of course, as always, things will not allways lead to a success
+But of course, as always, things will not always lead to a success
path, and one or more test do not pass the 'make test'. Before
sending in a bug report (using 'make nok' or 'make nokfile'), check
the mailing list if someone else has reported the bug already and if
@@ -1813,9 +1813,9 @@ In Tru64 the following options are available:
=over 4
-=item -p[rodecures]
+=item -p[rocedures]
-Procecures sorted in descending order by the number of cycles executed
+Procedures sorted in descending order by the number of cycles executed
in each procedure. Useful for finding the hotspot procedures.
(This is the default option.)