diff --git a/Directory.Build.props b/Directory.Build.props
index b29d24a3f..5c3ddd222 100644
--- a/Directory.Build.props
+++ b/Directory.Build.props
@@ -5,7 +5,7 @@
Silverback is a simple framework to build reactive, event-driven, microservices.MITCopyright (c) 2019 Sergio Aquilini
- -rc3
+ 1.1.0$(VersionSuffix)https://beagle1984.github.io/silverback/https://github.com/BEagle1984/silverback/
diff --git a/docs/_docs/0-introduction/003-releases.md b/docs/_docs/0-introduction/003-releases.md
index 544cb820b..db68e6c9d 100644
--- a/docs/_docs/0-introduction/003-releases.md
+++ b/docs/_docs/0-introduction/003-releases.md
@@ -4,7 +4,7 @@ permalink: /docs/releases
toc: true
---
-## [1.1.0-rc3](https://github.com/BEagle1984/silverback/releases/tag/1.1.0-rc3)
+## [1.1.0](https://github.com/BEagle1984/silverback/releases/tag/1.1.0)
### What's new
* Added `IEndpointsConfigurator` interface to allow splitting the endpoints configuration across multiple types (see [Connecting to a Message Broker]({{ site.baseurl }}/docs/quickstart/message-broker#using-iendpointsconfigurator))
diff --git a/docs/_docs/1-quickstart/107-behaviors.md b/docs/_docs/1-quickstart/107-behaviors.md
index 5cec3815d..606d39357 100644
--- a/docs/_docs/1-quickstart/107-behaviors.md
+++ b/docs/_docs/1-quickstart/107-behaviors.md
@@ -1,69 +1,106 @@
---
title: Behaviors
permalink: /docs/quickstart/behaviors
-toc: false
+toc: true
---
The behaviors can be used to build a custom pipeline (similar to the asp.net pipeline), easily adding your cross-cutting functionalities such as logging, validation, etc.
## IBehavior
-A behavior must implement the `IBehavior` interface and be registered for dependency injection.
+The behaviors implementing the `IBehavior` interface will be invoked by the `IPublisher` internals every time a message is published to the internal bus (this includes the wrapped `IInboundMessage` and `IOutboundMessages` that are generated to produce or consume a message from the message broker).
+
+At every call to `IPublisher.Publish` the `Handle` method of each registered behavior is called, passing in the collection of messages and the delegate to the next step in the pipeline. This gives you the flexibility to execute any sort of code before and after the messages have been actually published (before or after calling the `next()` step). You can for example modify the messages before publishing them, validate them (like in the above example), add some logging / tracing, etc.
+
+### IBehavior example
+
+The following example demonstrates how to use a behavior to trace the messages.
```c#
using Silverback.Messaging.Publishing;
-public class ValidationBehavior : IBehavior
+public class TracingBehavior : IBehavior
{
+ private readonly ITracer _tracer;
+
+ public TracingBehavior(ITracer tracer)
+ {
+ _tracer = tracer;
+ }
+
public async Task> Handle(
IEnumerable