summaryrefslogtreecommitdiff
path: root/Master/tlpkg/tlperl/lib/pods/perlperf.pod
diff options
context:
space:
mode:
Diffstat (limited to 'Master/tlpkg/tlperl/lib/pods/perlperf.pod')
-rw-r--r--Master/tlpkg/tlperl/lib/pods/perlperf.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/Master/tlpkg/tlperl/lib/pods/perlperf.pod b/Master/tlpkg/tlperl/lib/pods/perlperf.pod
index cac6eee6655..007a02bc876 100644
--- a/Master/tlpkg/tlperl/lib/pods/perlperf.pod
+++ b/Master/tlpkg/tlperl/lib/pods/perlperf.pod
@@ -30,7 +30,7 @@ optimization process.
Firstly, you need to establish a baseline time for the existing code, which
timing needs to be reliable and repeatable. You'll probably want to use the
-C<Benchmark> or C<Devel::DProf> modules, or something similar, for this step,
+C<Benchmark> or C<Devel::NYTProf> modules, or something similar, for this step,
or perhaps the Unix system C<time> utility, whichever is appropriate. See the
base of this document for a longer list of benchmarking and profiling modules,
and recommended further reading.
@@ -597,7 +597,7 @@ the code.
C<NYTProf> will generate a report database into the file F<nytprof.out> by
default. Human readable reports can be generated from here by using the
supplied C<nytprofhtml> (HTML output) and C<nytprofcsv> (CSV output) programs.
-We've used the Unix sytem C<html2text> utility to convert the
+We've used the Unix system C<html2text> utility to convert the
F<nytprof/index.html> file for convenience here.
$> html2text nytprof/index.html