From ebb77d1e3de79ce632aeb0b883b9beeb19ce33ef Mon Sep 17 00:00:00 2001 From: Ron Chmara Date: Sat, 13 Jan 2001 08:36:39 +0000 Subject: [PATCH] Typo fix. (thanks, cynic!). git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@39339 c90b9560-bf6c-de11-be94-00142212c4b1 --- chapters/security.xml | 2 +- security/index.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/chapters/security.xml b/chapters/security.xml index b9047c1dbd..4e5a2ebf62 100644 --- a/chapters/security.xml +++ b/chapters/security.xml @@ -438,7 +438,7 @@ if (!ereg('^[^./][^/]*$', $userfile)) developer who is trying to debug a script, indicating such things as the function or file that failed, the PHP file it failed in, and the line number which the failure occured in. This is all - information that can be exploited. It not uncommon for a php + information that can be exploited. It is not uncommon for a php developer to use show_source(), highlight_string(), or highlight_file() as a debugging measure, but in a live site, this can expose hidden variables, unchecked syntax, and other dangerous diff --git a/security/index.xml b/security/index.xml index b9047c1dbd..4e5a2ebf62 100644 --- a/security/index.xml +++ b/security/index.xml @@ -438,7 +438,7 @@ if (!ereg('^[^./][^/]*$', $userfile)) developer who is trying to debug a script, indicating such things as the function or file that failed, the PHP file it failed in, and the line number which the failure occured in. This is all - information that can be exploited. It not uncommon for a php + information that can be exploited. It is not uncommon for a php developer to use show_source(), highlight_string(), or highlight_file() as a debugging measure, but in a live site, this can expose hidden variables, unchecked syntax, and other dangerous