X-Git-Url: http://git.shiar.net/perl/plp/.git/blobdiff_plain/7509565253b19493771cfc2e13ab166f1a8cc5f8..d7fd5b9d9c2a137d73f2c42751011503ec96dd37:/PLP/FAQ.pod

diff --git a/PLP/FAQ.pod b/PLP/FAQ.pod
index 2aac805..7496f54 100644
--- a/PLP/FAQ.pod
+++ b/PLP/FAQ.pod
@@ -1,10 +1,15 @@
-=head1 Frequently Asked Questions about PLP
+=head1 NAME
+
+PLP::FAQ - Frequently Asked Questions about PLP
+
+=head1 FAQ
 
 =over 10
 
 =item What does PLP stand for?
 
-PerlPage. The name used to be HTMPL, but HyperText Markup with Perl Language was too long.
+PerlPage. The name used to be HTMPL, but HyperText Markup with Perl Language
+was too long.
 
 =item Is PLP hard to install?
 
@@ -44,17 +49,17 @@ design, you can add a little more speed.
 
 =item Can I use Perl's CGI module with PLP?
 
-You certainly can! If you do not want %get and %post and the like, just not use
-them. They will be generated on first access, so if you never access them, the
-hashes are never filled.
+You certainly can! If you do not want %get and %post and the like, just don't
+use them. They will be generated on first access, so if you never access them,
+the hashes are never filled.
 
 If you want to use CGI.pm's header functions, C<select STDOUT;> first, to break
 out of PLP's tied C<PLPOUT> filehandle.
 
 =item Why does C<< <($filename)> >> not work?
 
-C<< <(...)> >> is a compile-time tag, opposed to C<include()>, which is evaluated at
-run-time. At compile time, variables are not yet known, and PLP will try to
+C<< <(...)> >> is a compile-time tag, opposed to C<include()>, which is evaluated
+at run-time. At compile time, variables are not yet known, and PLP will try to
 include a file literally called C<$filename>.
 
     <: $filename = 'foo.inc.plp'; include($filename); :>
@@ -90,7 +95,7 @@ run-time errors. To do so, set the 0-bit (1) of C<$PLP::DEBUG> off. If you only
 want error reporting disabled for a single command, use Perl's C<eval BLOCK>
 function (not C<eval "">, but C<eval {}>, which is not slow or insecure.).
 
-    <: $PLP::DEBUG ^= 1 if $PLP::DEBUG & 1; :>
+    <: $PLP::DEBUG &= ~1; :>
 
 =item Can I have my own error messages?
 
@@ -111,7 +116,7 @@ version.
 There is. Set C<$PLP::DEBUG>'s 1-bit (2), and it will output a plain text header
 before outputting the other one.
 
-    <: $PLP::DEBUG ^= 2 unless $PLP::DEBUG & 2 :>
+    <: $PLP::DEBUG |= 2; :>
 
 =back