From: Andi Gutmans <andi@php.net>
Date: Wed, 27 Oct 2004 18:08:56 +0000 (+0000)
Subject: - Tiny fixes
X-Git-Tag: RELEASE_0_2~821
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=47a4a96d2301fb24d74c6ce6d67c1da44c8ee59e;p=php

- Tiny fixes
---

diff --git a/Zend/README.ZEND_VM b/Zend/README.ZEND_VM
index 3020f0ed4d..7bbb46c1f8 100644
--- a/Zend/README.ZEND_VM
+++ b/Zend/README.ZEND_VM
@@ -3,11 +3,11 @@ ZEND_VM
 
 ZEND_VM architecture allows specializing opcode handlers according to op_type
 fields and using different execution methods (call threading, switch threading
-and direct threading). As a result ZE2 got more then 20% speedup on raw PHP
+and direct threading). As a result ZE2 got more than 20% speedup on raw PHP
 code execution (with specialized executor and direct threading execution
-method). As most in most PHP applications raw execution speed isn't the
-limiting factor but system calls and database callls are, your mileage with
-this patch will vary.
+method). As in most PHP applications raw execution speed isn't the limiting
+factor but system calls and database callls are, your mileage with this patch
+will vary.
 
 Most parts of the old zend_execute.c go into zend_vm_def.h. Here you can
 find opcode handlers and helpers. The typical opcode handler template looks
@@ -40,7 +40,7 @@ ZEND_VM_DISPATCH_TO_HELPER_EX(<NAME>,<PARAM>,<VAL>)
 	return <NAME>(<VAL>, ZEND_OPCODE_HANDLER_ARGS_PASSTHRU)
 ZEND_VM_CONTINUE()
 	return 0
-ZEND_VM_NEXT_OPCOD()
+ZEND_VM_NEXT_OPCODE()
 	NEXT_OPCODE()
 ZEND_VM_SET_OPCODE(<TARGET>
 	SET_OPCODE(<TARGET>