Remove warnings about hook ordering guarantees

With hook weights, execution ordering can be built.

docs/charts_hooks.md

@@ -155,12 +155,10 @@ One resource can implement multiple hooks:
 
 Similarly, there is no limit to the number of different resources that
 may implement a given hook. For example, one could declare both a secret
-and a config map as a pre-install hook. It is important to keep in mind,
+and a config map as a pre-install hook.
-though, that there are no ordering guarantees about hooks.
 
 When subcharts declare hooks, those are also evaluated. There is no way
-for a top-level chart to disable the hooks declared by subcharts. And
+for a top-level chart to disable the hooks declared by subcharts.
-again, there is no guaranteed ordering.
 
 It is also possible to define a weight for a hook which will help build a
 deterministic executing order. Weights are defined using the following annotation: