From: Frank Wiegand Date: Fri, 26 Jun 2009 11:18:56 +0000 (+0200) Subject: pod/perlfilter.pod: two POD typos X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=d00c6acb5649055ca8b949a4bc7e614ee7cf8323;p=p5sagit%2Fp5-mst-13.2.git pod/perlfilter.pod: two POD typos Hi, while reading perlfilter.pod I found two typos, patch is attached. Thanks, Frank From ab8b547c7f60f1793dfd111d0d758853a07fbc95 Mon Sep 17 00:00:00 2001 From: Frank Wiegand Date: Fri, 26 Jun 2009 13:15:24 +0200 Subject: [PATCH] perlfilter.pod: fix two typos Signed-off-by: H.Merijn Brand --- diff --git a/pod/perlfilter.pod b/pod/perlfilter.pod index f96fe66..ca5cfd9 100644 --- a/pod/perlfilter.pod +++ b/pod/perlfilter.pod @@ -204,7 +204,7 @@ source filter (see Decryption Filters, below). All decryption filters work on the principle of "security through obscurity." Regardless of how well you write a decryption filter and -how strong your encryption algorithm, anyone determined enough can +how strong your encryption algorithm is, anyone determined enough can retrieve the original source code. The reason is quite simple - once the decryption filter has decrypted the source back to its original form, fragments of it will be stored in the computer's memory as Perl @@ -226,7 +226,7 @@ module. An alternative to writing the filter in C is to create a separate executable in the language of your choice. The separate executable reads from standard input, does whatever processing is necessary, and -writes the filtered data to standard output. C is an +writes the filtered data to standard output. C is an example of a source filter implemented as a separate executable - the executable is the C preprocessor bundled with your C compiler.