svn commit: r219900 - /perl/modperl/docs/trunk/src/docs/2.0/user/porting/compat.pod

[st...@apache.org]

Author: stas
Date: Wed Jul 20 07:03:34 2005
New Revision: 219900

URL: http://svn.apache.org/viewcvs?rev=219900&view=rev
Log:
typo fix
submitted by: Delfim Machado <db...@co.sapo.pt>

Modified:
    perl/modperl/docs/trunk/src/docs/2.0/user/porting/compat.pod

Modified: perl/modperl/docs/trunk/src/docs/2.0/user/porting/compat.pod
URL: http://svn.apache.org/viewcvs/perl/modperl/docs/trunk/src/docs/2.0/user/porting/compat.pod?rev=219900&r1=219899&r2=219900&view=diff
==============================================================================
--- perl/modperl/docs/trunk/src/docs/2.0/user/porting/compat.pod (original)
+++ perl/modperl/docs/trunk/src/docs/2.0/user/porting/compat.pod Wed Jul 20 07:03:34 2005
@@ -509,9 +509,9 @@
 C<L<Apache2::RequestUtil-E<gt>request|docs::2.0::api::Apache2::RequestUtil/C_request_>>
 usage should be avoided under mod_perl 2.0 C<$r> should be passed
 around as an argument instead (or in the worst case maintain your own
-global variable). Since your application may run under under threaded
-mpm, the C<Apache2::RequestUtil-E<gt>request> usage involves storage and retrieval
-from the thread local storage, which is expensive.
+global variable). Since your application may run under threaded mpm,
+the C<Apache2::RequestUtil-E<gt>request> usage involves storage and
+retrieval from the thread local storage, which is expensive.
 
 It's possible to use C<$r> even in CGI scripts running under
 C<L<Registry|docs::2.0::api::ModPerl::RegistryCooker>> modules,



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org