From e9e9733fe26025218e8a97d5a08ceb18f0d2dc15 Mon Sep 17 00:00:00 2001 From: Jon Date: Mon, 15 Sep 2014 22:59:41 +0100 Subject: [PATCH] Remove repetition, inline code formatting, wording --- 3-error-handler.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/3-error-handler.md b/3-error-handler.md index 8fcc823..f3b887d 100644 --- a/3-error-handler.md +++ b/3-error-handler.md @@ -27,9 +27,9 @@ Now before you start adding the error handler code to the **Important:** Never show any errors in your production environment. A stack trace or even just a simple error message can help someone to gain access to your system. Always show a user friendly error page instead and send an email to yourself, write to a log or something similar. So only you can see the errors in the production environment. -For development that does not make sense though and you want a nice error page. So the solution is to have an environment switch in your code. For now you can just set it to `development`. +For development that does not make sense though -- you want a nice error page. The solution is to have an environment switch in your code. For now you can just set it to `development`. -Then after the error handler registration, throw an Exception to test if everything is working correctly. Your `Bootstrap.php` should now look similar to this: +Then after the error handler registration, throw an `Exception` to test if everything is working correctly. Your `Bootstrap.php` should now look similar to this: ``` >](4-http.md)