Review_comments

Author: IsmathBadsha

posts/2026-03-10-26.0.0.3-beta.adoc

@@ -38,7 +38,7 @@ See also link:{url-prefix}/blog/?search=beta&key=tag[previous Open Liberty beta
 
 When a client calls a tool, the object that is returned by the tool method is converted to a `ToolResponse`, which usually contains one or more `Content` objects. The `ToolResponse` maps directly to the result returned in the response.
 
-If you need more control over the response from your tool, you can return a `ToolResponse` or `Content` object directly. Now it is also possible to register encoders to control how other objects are converted into a response.
+If you need more control over the response from your tool, you can return a `ToolResponse` or `Content` object directly. Now, it is also possible to register encoders to control how other objects are converted into a response.
 
 * Use `ToolResponseEncoder` to convert an object into a `ToolResponse`, which gives you complete control over the whole response.
 * Use `ContentEncoder` when you only need to convert an object into a `Content` that is included in the response. You can also return a list of objects, and each object is individually converted into a `Content` and included in the response.
@@ -47,7 +47,7 @@ If a tool method returns an object for which no encoder is provided, JSON-B enco
 
 === Example
 
-Consider a tool which does a search over some datastore:
+Consider a tool that does a search over some datastore:
 
 [source,java]
 ----
@@ -60,12 +60,12 @@ public SearchResult search(@ToolArg(name="query", description="the query to run"
 
 In this scenario, the `SearchResult` object encapsulates a list of individual results. Each entry contains a summary, associated metadata, and a relevance score that indicates its relationship to the query.
 
-By default, the `SearchResult` object that is returned is encoded as JSON by using JSON-B and placed into a `TextContent`. However, to return each search result summary as an individual `TextContent` and map the relevance score to a priority annotation, a `ToolResponseEncoder` is to be used
+By default, the `SearchResult` object that is returned is encoded as JSON by using JSON-B and placed into a `TextContent`. However, to return each search result summary as an individual `TextContent` and map the relevance score to a priority annotation, a `ToolResponseEncoder` is to be used.
 
 Create a CDI bean that implements the `ToolResponseEncoder` interface and implement:
 
 * the `encode` method to create a `ToolResponse` from a `SearchResult`
-* the `supports` method to indicate that your encoder can be used for any `SearchResult`.
+* the `supports` method to indicate that your encoder can be used for any `SearchResult`
 
 [source,java]
 ----
@@ -127,7 +127,7 @@ public SearchResult search(@ToolArg(name="query") String query, RequestId reques
 The following bugs have been fixed:
 
 * Output schemas were not generated correctly for asynchronous tool methods which have `structuredContent = true`
-* Omitting the `arguments` object when calling a tool would result in an error. The `arguments` object is optional if the tool does not require any arguments.
+* Omitting the `arguments` object when calling a tool would result in an error. The `arguments` object is optional if the tool does not require any arguments
 
 [#run]
 === Try it now