Add documentation for kedro run lifecycle

RELEASE.md

@@ -13,7 +13,8 @@
 * Added logging about not using async mode in `SequentiallRunner` and `ParallelRunner`.
 
 ## Documentation changes
-* Added documentations about `bootstrap_project` and `configure_project`.
+* Added documentation about `bootstrap_project` and `configure_project`.
+* Added documentation about `kedro run` and hook execution order.
 
 ## Community contributions
 

docs/source/hooks/introduction.md

@@ -1,4 +1,4 @@
-# Hooks
+# Introduction to Hooks
 
 ## Concepts
 
@@ -8,18 +8,18 @@
 
 Kedro defines Hook specifications for particular execution points where users can inject additional behaviour. Currently, the following Hook specifications are provided in [kedro.framework.hooks](/kedro.framework.hooks):
 
+* `after_context_created`
 * `after_catalog_created`
-* `before_node_run`
-* `after_node_run`
-* `on_node_error`
 * `before_pipeline_run`
-* `after_pipeline_run`
-* `on_pipeline_error`
 * `before_dataset_loaded`
 * `after_dataset_loaded`
+* `before_node_run`
+* `after_node_run`
 * `before_dataset_saved`
 * `after_dataset_saved`
-* `after_context_created`
+* `after_pipeline_run`
+* `on_node_error`
+* `on_pipeline_error`
 
 The naming convention for non-error Hooks is `<before/after>_<noun>_<past_participle>`, in which:
 
@@ -32,6 +32,8 @@
 
 [kedro.framework.hooks](/kedro.framework.hooks) lists the full specifications for which you can inject additional behaviours by providing an implementation.
 
+This diagram illustrates the execution order of hooks during `kedro run`:
+![kedro run hook execution order](../meta/images/kedro_run_lifecycle.png)
 
 ### CLI Hooks