Merge branch 'release-5.1.5' of github.com:Emrehzl94/docs-kafka-connector into release-5.1.5

merge changes

Author: Emrehzl94

modules/ROOT/pages/changelog.adoc

@@ -15,7 +15,7 @@ label:functionality[]
 label:new[]
 
 Added `neo4j.payload-mode` configuration property for source connector.
-| Introduced the `neo4j.payload-mode` option to define the structure of change messages. Available values are `COMPACT` and `EXTENDED`. `COMPACT` provides simpler messages but may have schema compatibility issues with property type changes, while `EXTENDED` includes type information to avoid such issues. Default is `EXTENDED`.
+| Introduced the `neo4j.payload-mode` option to define the structure of change messages. Available values are `COMPACT` and `EXTENDED`. `COMPACT` provides simpler messages but faces schema compatibility issues with property type changes, while `EXTENDED` includes type information to avoid such issues. Default is `EXTENDED`.
 
 a|
 label:bug[]

modules/ROOT/pages/source/configuration.adoc

@@ -36,7 +36,7 @@ Default: `false`
 Default: `1000`
 
 | neo4j.payload-mode
-| Defines the structure of change messages. One of `COMPACT`, `EXTENDED`. `COMPACT` provides simpler messages but may face schema compatibility issues if property types change. `EXTENDED` includes type information to avoid such issues.
+| Defines the structure of change messages. One of `COMPACT`, `EXTENDED`. `COMPACT` provides simpler messages but faces schema compatibility issues if property types change. `EXTENDED` includes type information to avoid such issues.
 
 Default: `EXTENDED`.
 |===

modules/ROOT/pages/source/payload-mode.adoc

@@ -6,7 +6,7 @@ The Kafka Source Connector for Neo4j supports two payload modes to control the f
 
 The `neo4j.payload-mode` configuration offers the following options:
 
-* **`EXTENDED` (Default)**: Provides a detailed structure for each property, supporting schema compatibility and consistency. This format is especially useful in cases where schema changes (such as type conversions) or temporal types are present, ensuring data consistency across changes.
+* **`EXTENDED` (Default)**: Provides a detailed structure for each property, supporting schema compatibility and consistency. This format is especially useful in cases where schema changes (such as property type changes) or temporal types are present, ensuring data consistency across changes.
 
 * **`COMPACT`**: Produces a simpler format that only includes the essential fields. This format is lighter and may be preferable when schema compatibility or complex data types are not required.