<commit_before>@milosloub  @wisepotato.

New hooks API is pretty much finished. Below is the usage guide, can also be found in the docs.  Time for a re-review.

Let us focus first on the discussion of the usage / hooks API / backward compatiblity related stuff. 

As soon as we're totally aligned with respect to this, we can quibble about internals: at this point any changes internally should not affect the interfaces/hooks API, therefore shouldn't be breaking



# Resource Hooks
This section covers the usage of **Resource Hooks**, which is a feature of`ResourceDefinition<T>`. See the [ResourceDefinition usage guide](resource-definitions.md) for a general explanation on how to set up a `ResourceDefinition<T>`.

By implementing resource hooks on a `ResourceDefintion<T>`, it is possible to intercept the execution of the **Resource Service Layer** (RSL) in various ways. This enables the developer to conveniently define business logic without having to override the RSL. It can be used to implement e.g.
* Authorization
* [Event-based synchronisation between microservices](https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/multi-container-microservice-net-applications/integration-event-based-microservice-communications)
* Logging 
* Transformation of the served data

This usage guide covers the following sections
1.  [**Semantics: pipelines, actions and hooks**](#semantics-pipelines-actions-and-hooks).
Understanding the semantics will be helpful in identifying which hooks on `ResourceDefinition<T>` you need to implement for your use-case.
2.  [**Hook execution overview**](#hook-execution-overview)
A table overview of all pipelines and involved hooks<commit_msg>Update hooks.md<commit_after># Resource Hooks
This section covers the usage of **Resource Hooks**, which is a feature of`ResourceDefinition<T>`. See the [ResourceDefinition usage guide](resource-definitions.md) for a general explanation on how to set up a `ResourceDefinition<T>`.

By implementing resource hooks on a `ResourceDefintion<T>`, it is possible to intercept the execution of the **Resource Service Layer** (RSL) in various ways. This enables the developer to conveniently define business logic without having to override the RSL. It can be used to implement e.g.
* Authorization
* [Event-based synchronisation between microservices](https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/multi-container-microservice-net-applications/integration-event-based-microservice-communications)
* Logging 
* Transformation of the served data

This usage guide covers the following sections
1.  [**Semantics: pipelines, actions and hooks**](#semantics-pipelines-actions-and-hooks).
Understanding the semantics will be helpful in identifying which hooks on `ResourceDefinition<T>` you need to implement for your use-case.
2.  [**Hook execution overview**](#hook-execution-overview)
A table overview of all pipelines and involved hooks
{'fraction_non_alphanumeric': 0.07692307692307693, 'fraction_numerical': 0.001349527665317139, 'mean_word_length': 5.487964989059081, 'pattern_counts': {'":': 0, '<': 11, '<?xml version=': 0, '>': 11, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6861225', 'n_tokens_mistral': 774, 'n_tokens_neox': 717, 'n_words': 337}