php 5.5, fix extension name in opcache.ini

1 files changed, 16 insertions, 16 deletions

diff --git a/opcache.ini b/opcache.ini
index 1334f82..05d75af 100644
--- a/opcache.ini
+++ b/opcache.ini
@@ -1,18 +1,18 @@
-; Enable Zend Optimizer+ extension module
+; Enable Zend OPcache extension module
 zend_extension=@EXTPATH@/opcache.so
 
-;	Optimizer+ On/Off switch. When set to Off, code is not optimized.
+;	Opcache On/Off switch. When set to Off, code is not optimized.
 ;opcache.enable=1
 ;opcache.enable_cli=0
 
-;	The Optimizer+ shared memory storage size. The amount of memory for storing
+;	The OPcache shared memory storage size. The amount of memory for storing
 ;	precompiled PHP code in Mbytes.
 opcache.memory_consumption=128
 
 ;	The amount of memory for interned strings in Mbytes.
 opcache.interned_strings_buffer=8
 
-;	The maximum number of keys (scripts) in the Optimizer+ hash table.
+;	The maximum number of keys (scripts) in the OPcache hash table.
 ;	The number is actually the the first one in the following set of prime
 ;	numbers that is bigger than the one supplied: { 223, 463, 983, 1979, 3907,
 ;	7963, 16229, 32531, 65407, 130987 }. Only numbers between 200 and 100000
@@ -22,13 +22,13 @@ opcache.max_accelerated_files=4000
 ;	The maximum percentage of "wasted" memory until a restart is scheduled.
 ;opcache.max_wasted_percentage=5
 
-;	When this directive is enabled, the Optimizer+ appends the current working
+;	When this directive is enabled, the OPcache appends the current working
 ;	directory to the script key, thus eliminating possible collisions between
 ;	files with the same name (basename). Disabling the directive improves
 ;	performance, but may break existing applications.
 ;opcache.use_cwd=1
 
-;	When disabled, you must reset the Optimizer+ manually or restart the
+;	When disabled, you must reset the OPcache manually or restart the
 ;	webserver for changes to the filesystem to take effect.
 ;	The frequency of the check is controlled by the directive
 ;	"opcache.revalidate_freq".
@@ -66,15 +66,15 @@ opcache.fast_shutdown=1
 ;	Allow file existence override (file_exists, etc.) performance feature.
 ;opcache.enable_file_override=0
 
-;	A bitmask, where each bit enables or disables the appropriate Optimizer+
+;	A bitmask, where each bit enables or disables the appropriate OPcache
 ;	passes
 ;opcache.optimization_level="0xffffffff"
 
 ;	Enable this hack as a workaround for "can't redeclare class" errors.
-;	The Optimizer+ stores the places where DECLARE_CLASS opcodes use
+;	The OPcache stores the places where DECLARE_CLASS opcodes use
 ;	inheritance (These are the only opcodes that can be executed by PHP,
 ;	but which may not be executed because the parent class is missing due to
-;	optimization). When the file is loaded, Optimizer+ tries to bind the
+;	optimization). When the file is loaded, OPcache tries to bind the
 ;	inherited classes by using the current environment. The problem with this
 ;	scenario is that, while the DECLARE_CLASS opcode may not be needed for the
 ;	current script, if the script requires that the opcode at least be defined,
@@ -86,8 +86,8 @@ opcache.fast_shutdown=1
 ;	Enable this hack as a workaround for "Cannot redeclare class" errors.
 ;opcache.dups_fix=0
 
-;	The location of the Optimizer+ blacklist file.
-;	The Optimizer+ blacklist file is a text file that holds the names of files
+;	The location of the OPcache blacklist file.
+;	The OPcache blacklist file is a text file that holds the names of files
 ;	that should not be accelerated. The file format is to add each filename
 ;	to a new line. The filename may be a full path or just a file prefix
 ;	(i.e., /var/www/x  blacklists all the files and directories in /var/www
@@ -96,7 +96,7 @@ opcache.fast_shutdown=1
 ;	1) Directories that contain auto generated code, like Smarty or ZFW cache.
 ;	2) Code that does not work well when accelerated, due to some delayed
 ;	   compile time evaluation.
-;	3) Code that triggers an Optimizer+ bug.
+;	3) Code that triggers an OPcache bug.
 ;opcache.blacklist_filename
 
 ;	Allows exclusion of large files from being cached.
@@ -111,18 +111,18 @@ opcache.fast_shutdown=1
 
 ;	How long to wait (in seconds) for a scheduled restart to begin if the cache
 ;	is not being accessed.
-;	The Optimizer+ uses this directive to identify a situation where there may
+;	The OPcache uses this directive to identify a situation where there may
 ;	be a problem with a process. After this time period has passed, the
-;	Optimizer+ assumes that something has happened and starts killing the
+;	OPcache assumes that something has happened and starts killing the
 ;	processes that still hold the locks that are preventing a restart.
 ;	If the log level is 3 or above, a "killed locker" error is recorded
 ;	in the Apache logs when this happens.
 ;opcache.force_restart_timeout=180
 
-;	Optimizer+ error_log file name. Empty string assumes "stderr".
+;	OPcache error_log file name. Empty string assumes "stderr".
 ;opcache.error_log=stderr
 
-;	All Optimizer+ errors go to the Web server log.
+;	All OPcache errors go to the Web server log.
 ;	By default, only fatal errors (level 0) or errors (level 1) are logged.
 ;	You can also enable warnings (level 2), info messages (level 3) or
 ;	debug messages (level 4).