Update documentation

Signed-off-by: Gabriele Santomaggio <[email protected]>

Author: Gsantomaggio

README.md

@@ -16,7 +16,7 @@ The RabbitMQ Stream .NET Client is a .NET library to communicate with the [Rabbi
 
 The client is distributed via [NuGet](https://www.nuget.org/packages/RabbitMQ.Stream.Client/).
 
-Please refer to the [documentation](https://rabbitmq.github.io/rabbitmq-stream-dotnet-client/stable/htmlsingle/index.html) ([PDF](https://rabbitmq.github.io/rabbitmq-stream-dotnet-client/stable/documentation.pdf)) to find out more.
+Please refer to the [documentation](https://rabbitmq.github.io/rabbitmq-stream-dotnet-client/stable/htmlsingle/index.html) ([PDF](https://rabbitmq.github.io/rabbitmq-stream-dotnet-client/stable/dotnet-stream-client.pdf)) to find out more.
 
 
 ### Support

RabbitMQ.Stream.Client/Reliable/Producer.cs

@@ -133,7 +133,7 @@ public class Producer : ProducerFactory
 
     protected override ILogger BaseLogger => _logger;
 
-    private protected Producer(ProducerConfig producerConfig, ILogger<Producer> logger = null)
+    private Producer(ProducerConfig producerConfig, ILogger<Producer> logger = null)
     {
         _producerConfig = producerConfig;
         _confirmationPipe = new ConfirmationPipe(

docs/asciidoc/api.adoc

@@ -978,6 +978,15 @@ Like the `RawProducer` class, the `Raw*` classes have the same events to handle
 
 It is up to the user to handle the disconnection and metadata update events.
 
+[WARNING]
+.Be careful when using the `Raw*` classes.
+====
+They are low-level classes and you need to handle the disconnection and metadata update events. If you don't handle them, you will end up with a disconnected client and you will not be able to reconnect to the server.
+
+"RawProducer:send" is not thread-safe. You need to synchronize access to it.
+"RawProducer" does not handle the timeout/error confirmation messages. You need to handle it yourself.
+====
+
 ===== High-level classes
 
 ** <<creating-a-producer, `Producer`>> - High-level producer class