From ed3339f627b499edde4af302638718e470130ba5 Mon Sep 17 00:00:00 2001 From: krakjoe Date: Wed, 13 Nov 2013 10:25:51 +0000 Subject: [PATCH] ... --- tutorials/intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tutorials/intro.md b/tutorials/intro.md index 77a84c634c..6625dd0c6b 100644 --- a/tutorials/intro.md +++ b/tutorials/intro.md @@ -16,7 +16,7 @@ Breaking Execution ================== *Telling phpdbg when to stop ...* -In order to debug your code, execution must be interrupted at a very specific points during execution, and allow access to, and inspection of, the execution environment. For extreeme circumstances, and geeks (me included), phpdbg can step through the execution of your script, showing you information about every opcode the vm executes, including the address (in case you need to break at that specific point on the next execution). +In order to debug your code, execution must be interrupted at a very specific points during execution, and allow access to, and inspection of, the execution environment. For extreme circumstances, and geeks (me included), phpdbg can step through the execution of your script, showing you information about every opcode the vm executes, including the address (in case you need to break at that specific point on the next execution). phpdbg provides many options for specifying break points, as illustrated by a screenshot of the help menu for the break command: -- 2.40.0