Fix phases and sequence in job-lifecycle.md

The table had the phases in wrong sequence of execution

Author: michal-at-travisci

user/job-lifecycle.md

@@ -21,9 +21,9 @@ The ‘.travis.yml’ file describes the build process for Travis CI. A *build*
 
 Each *job* is a sequence of *phases*, which are sequential steps that form a job. The following table shows the main phases that users can add to jobs. 
 
-| **Pre-Install Phase (Optional)** | **Install Phase** | **Script Phase** | **Deploy Phase (Optional)** |
-|---|---|---|---|
-| Travis CI can run these optional commands in this phase:<br>- [`apt addons`](/user/installing-dependencies/#installing-packages-with-the-apt-addon)<br>- `before_cache` (if and only if caching is effective)<br>- [`cache components`](/user/caching/) | Travis CI can run the following custom commands in this main phase:<br>- `install`: installs any dependencies required.<br>  - `before_install`: before the install phase.<br>  - `before_script`: before the script phase.<br>  - `after_script`: after the script phase.<br>  - `after_success`: when the build *succeeds* (e.g., building documentation), the result is in the `TRAVIS_TEST_RESULT` environment variable.<br>  - `after_failure`: when the build *fails* (e.g., uploading log files), the result is in the `TRAVIS_TEST_RESULT` environment variable. | Travis CI can run the following custom commands in this main phase:<br>- `script`: run the build script.<br>  - `before_install`: before the install phase.<br>  - `before_script`: before the script phase.<br>  - `after_script`: after the script phase.<br>  - `after_success`: when the build *succeeds* (e.g., building documentation), the result is in the `TRAVIS_TEST_RESULT` environment variable.<br>  - `after_failure`: when the build *fails* (e.g., uploading log files), the result is in the `TRAVIS_TEST_RESULT` environment variable. | Travis CI can run custom commands in the phases:<br>- `deploy`: optional deployment phase.<br>- `before_deploy`: (if and only if deployment is active)<br>- `after_deploy`: (if and only if deployment is active) |
+| **Pre-Install Phase (Optional)** | **Install Phase** | **Script Phase** | **Deploy Phase (Optional)** | **After Script Phase** |
+|---|---|---|---|---|
+| Travis CI can run these optional commands in this phase, in following sequence:<br>- [`apt addons`](/user/installing-dependencies/#installing-packages-with-the-apt-addon)<br>- [`cache components`](/user/caching/) | Travis CI can run the following custom commands in this main phase, in this sequence:<br>- `before_install`: before the install phase.<br>- `install`: installs any dependencies required. | Travis CI can run the following custom commands in this main phase, in following sequence:<br>  - `before_script`: before the script phase.<br>- `script`: run the build script.<br> - `before_cache`: (OPTIONAL, if and only if caching is effective)<br> - `after_success`: when the build *succeeds* (e.g., building documentation), the result is in the `TRAVIS_TEST_RESULT` environment variable.<br>  - `after_failure`: when the build *fails* (e.g., uploading log files), the result is in the `TRAVIS_TEST_RESULT` environment variable. | Travis CI can run custom commands in the phases, in a following sequence:<br>- `before_deploy`: (if and only if deployment is active)<br>- `deploy`: optional deployment phase.<br>- `after_deploy`: (if and only if deployment is active) | Travis CI can run custom commands in the phases, in a following sequence:<br> - `after_script`: after the script phase.<br>|
 
  > **Note**: A *build* can be composed of many jobs.