summaryrefslogtreecommitdiff
path: root/pod/perlfaq9.pod
diff options
context:
space:
mode:
authorAndy Lester <andy@petdance.com>2005-06-02 11:19:54 -0500
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2005-06-03 08:04:25 +0000
commitb432a67249666bce4aa3385263660dc667d150d7 (patch)
treed7fccc07dbacb727f1e2d96499970be0b3682421 /pod/perlfaq9.pod
parent3a205795a9fa8c21e484e9a8efe6e9257c24bd1e (diff)
downloadperl-b432a67249666bce4aa3385263660dc667d150d7.tar.gz
Quotes in pod/*.pod
Message-ID: <20050602211954.GA22107@petdance.com> p4raw-id: //depot/perl@24686
Diffstat (limited to 'pod/perlfaq9.pod')
-rw-r--r--pod/perlfaq9.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlfaq9.pod b/pod/perlfaq9.pod
index 1a40c3beae..be4ffcb4e7 100644
--- a/pod/perlfaq9.pod
+++ b/pod/perlfaq9.pod
@@ -322,7 +322,7 @@ The HTTPD::UserAdmin and HTTPD::GroupAdmin modules provide a
consistent OO interface to these files, regardless of how they're
stored. Databases may be text, dbm, Berkeley DB or any database with
a DBI compatible driver. HTTPD::UserAdmin supports files used by the
-`Basic' and `Digest' authentication schemes. Here's an example:
+"Basic" and "Digest" authentication schemes. Here's an example:
use HTTPD::UserAdmin ();
HTTPD::UserAdmin
@@ -439,7 +439,7 @@ A related strategy that's less open to forgery is to give them a PIN
(personal ID number). Record the address and PIN (best that it be a
random one) for later processing. In the mail you send, ask them to
include the PIN in their reply. But if it bounces, or the message is
-included via a ``vacation'' script, it'll be there anyway. So it's
+included via a "vacation" script, it'll be there anyway. So it's
best to ask them to mail back a slight alteration of the PIN, such as
with the characters reversed, one added or subtracted to each digit, etc.