Skip to content

Commit 0b9f7f7

Browse files
Apply suggestions from code review
Co-authored-by: Antoine Makdessi <[email protected]>
1 parent 357a6b6 commit 0b9f7f7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

contributing/code/stack_trace.rst

+4-4
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ unexpected places, such as lines of code where exceptions are thrown.
2121
Stack Traces and Exceptions
2222
---------------------------
2323

24-
In PHP, every exception comes with it own stack trace, which is
24+
In PHP, every exception comes with its own stack trace, which is
2525
displayed by default if the exception is not caught. When using Symfony,
2626
such exceptions go through a custom exception handler, which enhances
2727
them in various ways before displaying them according to the current
@@ -34,7 +34,7 @@ Nested Exceptions
3434
-----------------
3535

3636
When programs get bigger, complexity is often tackled with layers of
37-
architecture that need to be kept separate. For instance, if you have an
37+
architecture that need to be kept separate. For instance, if you have a
3838
web application that makes a call to a remote API, it might be good to
3939
wrap exceptions thrown when making that call with exceptions that have
4040
special meaning in your domain, and to build appropriate HTTP exceptions
@@ -57,7 +57,7 @@ code and then your code might call it. This means you will always have
5757
at least 2 parts, very often 3 in your stack traces when using Symfony:
5858
a part that starts in one of the entrypoints of the framework
5959
(``bin/console`` or ``public/index.php`` in most cases), and ends when
60-
reaching your code, most times in a command or in an action found under
60+
reaching your code, most times in a command or in a controller found under
6161
``src``. Then, either the exception is thrown in your code or in
6262
libraries you call. If it is the latter, there should be a third part in
6363
the stack trace with calls made in files under ``vendor``. Before
@@ -80,7 +80,7 @@ symfony/symfony`` when reporting a bug for any component.
8080
Getting Stack Traces with Symfony
8181
---------------------------------
8282

83-
Now that we have all this in mind, let us see how to get a Stack trace
83+
Now that we have all this in mind, let us see how to get a stack trace
8484
with Symfony.
8585

8686
Stack Traces in your Web Browser

0 commit comments

Comments
 (0)