Docs (WIP).

Author: ffernandolima

docs/Idempotency/RedisIdempotency.md

@@ -14,7 +14,7 @@ To install the package and start integrating with Redis:
 dotnet add package Confluent.Kafka.Core.Idempotency.Redis
 ```
 
-### Usage and Configuration :bar_chart:
+### Usage and Configuration :jigsaw:
 To configure the idempotency handler, use the `WithRedisIdempotencyHandler` method. This handler can be added to both worker and retry worker for idempotent processing.
 
 To add the Redis idempotency handler to a Kafka worker:
@@ -65,7 +65,7 @@ builder.Services.AddKafka(builder =>
                        /*.With...*/)))); // Additional options can be added here
 ```
 
-### Recommended Interface for Message Value :envelope_with_arrow:
+### Recommended Interface for Message Value :e-mail:
 
 It is strongly recommended to implement the `IMessageValue` interface from the namespace `Confluent.Kafka.Core.Models` within the message value to create a standard and simplify message Id discovery. This interface includes the `Id` property as a `Guid` and can be used with the `MessageIdHandler`.
 

docs/OpenTelemetry/OpenTelemetry.md

@@ -18,7 +18,7 @@ To install the package and start integrating with OpenTelemetry:
 dotnet add package Confluent.Kafka.Core.OpenTelemetry
 ```
 
-### Usage and Custom Enrichment :bar_chart:
+### Usage and Custom Enrichment :jigsaw:
 
 To enable distributed tracing, call the `AddKafkaDiagnostics` method while registering Kafka Core services into the Microsoft built-in container. Below are some examples:
 

docs/Serialization/JsonCore.md

@@ -12,7 +12,7 @@ To install the package and start integrating with System.Text.Json:
 dotnet add package Confluent.Kafka.Core.Serialization.JsonCore
 ```
 
-### Usage and Options Configuration :bar_chart:
+### Usage and Options Configuration :jigsaw:
 
 There are multiple ways to configure the JsonCore serializer for your Kafka producer and consumer, allowing you to set the serializer for either the Key, the Value, or both, depending on your use case. The System.Text.Json library offers many options for configuring how JSON is handled in your messages. These options can be passed through the JsonCore serializer, providing fine-grained control over serialization and deserialization behavior. The options configuration is optional, and if not provided, default options will be assumed internally.
 

docs/Serialization/JsonNET.md

@@ -12,7 +12,7 @@ To install the package and start integrating with Newtonsoft.Json:
 dotnet add package Confluent.Kafka.Core.Serialization.NewtonsoftJson
 ```
 
-### Usage and Settings Configuration :bar_chart:
+### Usage and Settings Configuration :jigsaw:
 
 There are multiple ways to configure the Json.NET serializer for your Kafka producer and consumer, allowing you to set the serializer for either the Key, the Value, or both, depending on your use case. The Newtonsoft.Json library offers many settings for configuring how JSON is handled in your messages. These settings can be passed through the Json.NET serializer, providing fine-grained control over serialization and deserialization behavior. The settings configuration is optional, and if not provided, default settings will be assumed internally.
 

docs/Serialization/ProtobufNet.md

@@ -12,7 +12,7 @@ To install the package and start integrating with protobuf-net:
 dotnet add package Confluent.Kafka.Core.Serialization.ProtobufNet
 ```
 
-### Usage and Options Configuration :bar_chart:
+### Usage and Options Configuration :jigsaw:
 
 There are multiple ways to configure the protobuf-net serializer for your Kafka producer and consumer, allowing you to set the serializer for either the Key, the Value, or both, depending on your use case. The protobuf-net library offers some options for configuring how your messages are serialized using protocol buffers. These options can be passed through the protobuf-net serializer, providing fine-grained control over serialization and deserialization behavior. The options configuration is optional, and if not provided, default options will be assumed internally.
 

docs/Serialization/SchemaRegistryAvro.md

@@ -12,7 +12,7 @@ To install the package and start integrating with Confluent.SchemaRegistry.Serde
 dotnet add package Confluent.Kafka.Core.Serialization.SchemaRegistry.Avro
 ```
 
-### Usage and Configuration :bar_chart:
+### Usage and Configuration :jigsaw:
 
 There are multiple ways to configure the SchemaRegistry.Avro serializer for your Kafka producer and consumer, allowing you to set the serializer for either the Key, the Value, or both, depending on your use case. It provides several configurations for controlling how your messages interact with the Confluent Schema Registry. These configurations can be passed through the SchemaRegistry.Avro serializer, allowing for fine-grained control over schema registration, compatibility checks, and both serialization and deserialization behaviors. The Schema Registry client configuration is required, but the other configurations are optional, and if not provided, default configurations will be assumed internally.
 

docs/Serialization/SchemaRegistryJson.md

@@ -13,7 +13,7 @@ To install the package and start integrating with Confluent.SchemaRegistry.Serde
 dotnet add package Confluent.Kafka.Core.Serialization.SchemaRegistry.Json
 ```
 
-### Usage and Configuration :bar_chart:
+### Usage and Configuration :jigsaw:
 
 There are multiple ways to configure the SchemaRegistry.Json serializer for your Kafka producer and consumer, allowing you to set the serializer for either the Key, the Value, or both, depending on your use case. It provides several configurations for controlling how your messages interact with the Confluent Schema Registry. These configurations can be passed to the SchemaRegistry.Json serializer, allowing for fine-grained control over schema registration, compatibility checks, and both serialization and deserialization behaviors. The Schema Registry client configuration is required, but the other configurations are optional, and if not provided, default configurations will be assumed internally.
 

docs/Serialization/SchemaRegistryProtobuf.md

@@ -12,7 +12,7 @@ To install the package and start integrating with Confluent.SchemaRegistry.Serde
 dotnet add package Confluent.Kafka.Core.Serialization.SchemaRegistry.Protobuf
 ```
 
-### Usage and Configuration :bar_chart:
+### Usage and Configuration :jigsaw:
 
 There are multiple ways to configure the SchemaRegistry.Protobuf serializer for your Kafka producer and consumer, allowing you to set the serializer for either the Key, the Value, or both, depending on your use case. It provides several configurations for controlling how your messages interact with the Confluent Schema Registry. These configurations can be passed to the SchemaRegistry.Protobuf serializer, allowing for fine-grained control over schema registration, compatibility checks, and both serialization and deserialization behaviors. The Schema Registry client configuration is required, but the other configurations are optional, and if not provided, default configurations will be assumed internally.