applied patch, with indentation tweaks

[p5sagit/p5-mst-13.2.git] / pod / perlfaq3.pod

diff --git a/pod/perlfaq3.pod b/pod/perlfaq3.pod
index 7489e98..7a30759 100644 (file)
--- a/pod/perlfaq3.pod
+++ b/pod/perlfaq3.pod
@@ -1,6 +1,6 @@
 =head1 NAME
 
-perlfaq3 - Programming Tools ($Revision: 1.21 $, $Date: 1997/04/23 18:04:23 $)
+perlfaq3 - Programming Tools ($Revision: 1.22 $, $Date: 1997/04/24 22:43:42 $)
 
 =head1 DESCRIPTION
 
@@ -15,7 +15,7 @@ Have you read the appropriate man pages?  Here's a brief index:
 
        Objects         perlref, perlmod, perlobj, perltie
        Data Structures perlref, perllol, perldsc
-       Modules         perlmod, perlsub
+       Modules         perlmod, perlmodlib, perlsub
        Regexps         perlre, perlfunc, perlop
        Moving to perl5 perltrap, perl
        Linking w/C     perlxstut, perlxs, perlcall, perlguts, perlembed
@@ -85,7 +85,7 @@ perl-mode for emacs can provide a remarkable amount of help with most
 (but not all) code, and even less programmable editors can provide
 significant assistance.
 
-If you are using to using vgrind program for printing out nice code to
+If you are used to using vgrind program for printing out nice code to
 a laser printer, you can take a stab at this using
 http://www.perl.com/CPAN/doc/misc/tips/working.vgrind.entry, but the
 results are not particularly satisfying for sophisticated code.
@@ -260,7 +260,7 @@ module written in C can.  With the FCGI module (from CPAN), a Perl
 executable compiled with sfio (see the F<INSTALL> file in the
 distribution) and the mod_fastcgi module (available from
 http://www.fastcgi.com/) each of your perl scripts becomes a permanent
-CGI daemon processes.
+CGI daemon process.
 
 Both of these solutions can have far-reaching effects on your system
 and on the way you write your CGI scripts, so investigate them with
@@ -285,9 +285,9 @@ source.  Security through obscurity, the name for hiding your bugs
 instead of fixing them, is little security indeed.
 
 You can try using encryption via source filters (Filter::* from CPAN).
-But crackers might be able to decrypt it.  You can try using the
-byte code compiler and interpreter described below, but crackers might
-be able to de-compile it.  You can try using the native-code compiler
+But crackers might be able to decrypt it.  You can try using the byte
+code compiler and interpreter described below, but crackers might be
+able to de-compile it.  You can try using the native-code compiler
 described below, but crackers might be able to disassemble it.  These
 pose varying degrees of difficulty to people wanting to get at your
 code, but none can definitively conceal it (this is true of every