Skip to content

Commit 7b3c6a1

Browse files
committed
Merge branch '5.1'
* 5.1: Getting a stack trace follow up
2 parents d3b9cb7 + 40415a5 commit 7b3c6a1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

contributing/code/stack_trace.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ displayed by default if the exception is not caught. When using Symfony,
2727
such exceptions go through a custom exception handler, which enhances
2828
them in various ways before displaying them according to the current
2929
Server API (CLI or not).
30-
This means a better way to get a stack trace when you do need the
30+
This means a better way to get a stack trace when you do not need the
3131
program to continue is to throw an exception, as follows:
3232
``throw new \Exception();``
3333

@@ -91,7 +91,7 @@ Several things need to be paid attention to when picking a stack trace
9191
from your development environment through a web browser:
9292

9393
1. Are there several exceptions? If yes, the most interesting one is
94-
often exception 1/n which, is shown _last_ in the example below (it
94+
often exception 1/n which, is shown *last* in the example below (it
9595
is the one marked as exception [1/2]).
9696
2. Under the "Stack Traces" tab, you will find exceptions in plain
9797
text, so that you can easily share them in e.g. bug reports. Make

0 commit comments

Comments
 (0)