Skip to content

Commit

Permalink
Change "confidence" to "confident"
Browse files Browse the repository at this point in the history
  • Loading branch information
RobertDeniszczyc committed Aug 10, 2014
1 parent 08d578a commit d55500c
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions lifecycle.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
<a name="overview"></a>
## Overview

When using any tool in the "real world", you feel more confidence if you understand how that tool works. Application development is no different. When you understand how your development tools function, you feel more comfortable and confident using them. The goal of this document is to give you a good, high-level overview of how the Laravel framework "works". By getting to know the overall framework better, everything feels less "magical" and you will be more confident building your applications. In addition to a high-level overview of the request lifecycle, we'll cover "start" files and application events.
When using any tool in the "real world", you feel more confident if you understand how that tool works. Application development is no different. When you understand how your development tools function, you feel more comfortable and confident using them. The goal of this document is to give you a good, high-level overview of how the Laravel framework "works". By getting to know the overall framework better, everything feels less "magical" and you will be more confident building your applications. In addition to a high-level overview of the request lifecycle, we'll cover "start" files and application events.

If you don't understand all of the terms right away, don't lose heart! Just try to get a basic grasp of what is going on, and your knowledge will grow as you explore other sections of the documentation.

Expand Down Expand Up @@ -76,4 +76,4 @@ You may also register a listener on the `matched` event, which is fired when an
//
});

The `finish` event is called after the response from your application has been sent back to the client. This is a good place to do any last minute processing your application requires. The `shutdown` event is called immediately after all of the `finish` event handlers finish processing, and is the last opportunity to do any work before the script terminates. Most likely, you will not have a need to use either of these events.
The `finish` event is called after the response from your application has been sent back to the client. This is a good place to do any last minute processing your application requires. The `shutdown` event is called immediately after all of the `finish` event handlers finish processing, and is the last opportunity to do any work before the script terminates. Most likely, you will not have a need to use either of these events.

0 comments on commit d55500c

Please sign in to comment.