[ksqlDB.RestApi.Client]: doc improvements

Author: tomasfabian

README.md

@@ -162,7 +162,7 @@ run in command line:
 
 In [Blazor](https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor), the application logic and UI rendering occur on the server. The client's web browser receives updates and UI changes through a **SignalR** connection.
 This ensures smooth integration with the `ksqlDB.RestApi.Client` library, allowing the **Apache Kafka broker** and **ksqlDB** to remain hidden from direct exposure to clients.
-The **server-side Blazor** application communicates with ksqlDB using the `ksqlDB.RestApi.Client`.
+The **server-side Blazor** application communicates with `ksqlDB` using the `ksqlDB.RestApi.Client`.
 Whenever an event in `ksqlDB` occurs, the server-side Blazor app responds and signals the UI in the client's browser to update. This setup allows a smooth and continuous update flow, creating a real-time, reactive user interface.
 
 - set `docker-compose.csproj` as startup project in [InsideOut.sln](https://github.com/tomasfabian/ksqlDB.RestApi.Client-DotNet/tree/main/Samples/InsideOut) for embedded Kafka connect integration and stream processing examples.
@@ -421,7 +421,7 @@ CREATE TABLE IF NOT EXISTS Accounts (
 ) WITH ( KAFKA_TOPIC='Account', VALUE_FORMAT='Json', PARTITIONS='3', REPLICAS='3' );
 ```
 
-The Description property within the `Payment` type has been customized to override the resulting column name as "Desc".
+The `Description` property within the `Payment` type has been customized to override the resulting column name as "Desc".
 Additionally, the `Id` property within the `Account` table has been designated as the **primary key**, while the `Secret` property is disregarded during code generation.
 
 ### Aggregation functions

docs/modelbuilder.md

@@ -147,7 +147,7 @@ modelBuilder.AddConvention(decimalTypeConvention);
 ### WithHeader
 **v5.1.0**
 
-Properties of en entity can be marked as a [HEADER](https://docs.ksqldb.io/en/latest/reference/sql/data-definition/#headers) with the model builder's fluent API as demonstrated below:
+Properties of an entity can be marked as a [HEADER](https://docs.ksqldb.io/en/latest/reference/sql/data-definition/#headers) with the model builder's fluent API as demonstrated below:
 
 ```C#
 using ksqlDb.RestApi.Client.FluentAPI.Builders;
@@ -181,7 +181,7 @@ The `WithHeader` function within the fluent API takes precedence over the `Heade
 ### WithHeaders
 **v5.1.0**
 
-Properties of en entity can be marked as a [HEADERS](https://docs.ksqldb.io/en/latest/reference/sql/data-definition/#headers) with the model builder's fluent API as demonstrated below:
+Properties of an entity can be marked as a [HEADERS](https://docs.ksqldb.io/en/latest/reference/sql/data-definition/#headers) with the model builder's fluent API as demonstrated below:
 
 ```C#
 using ksqlDb.RestApi.Client.Metadata;
@@ -239,7 +239,7 @@ modelBuilder.Entity<Payment>()
   .HasColumnName("Desc");
 
 var statement = new CreateInsert(modelBuilder)
-    .Generate(movie, new InsertProperties { IdentifierEscaping = IdentifierEscaping.Keywords });
+    .Generate(payment, new InsertProperties { IdentifierEscaping = IdentifierEscaping.Keywords });
 ```
 
 The KSQL snippet illustrates an example INSERT statement with the overridden column name, showing how it corresponds to the fluent API configuration:

docs/statements.md

@@ -747,7 +747,6 @@ var properties = new DropFromItemProperties
   IdentifierEscaping = IdentifierEscaping.Always
 };
 
-//Act
 var response1 = await ksqlDbRestApiClient.DropTableAsync<TestTable>(properties);
 var response2 = await ksqlDbRestApiClient.DropStreamAsync<TestStream>(properties);
 ```
@@ -1245,7 +1244,6 @@ Expression<Func<string>> valueExpression = () => INITCAP("One little mouse");
 
 var insertValues = new InsertValues<Movie>(new Movie { Id = 5 });
 
-//Act
 insertValues.WithValue(c => c.Title, valueExpression);
 
 Context.Add(insertValues);