- clarification

Author: modabas

README.md

@@ -28,7 +28,7 @@
 
 ### WebResultEndpoint
 
-- **Purpose**: Converts business results into standardized HTTP responses, ensuring consistent and type-safe API behavior.
+- **Purpose**: Converts business results into standardized HTTP status codes and response formats, ensuring consistent and type-safe API behavior.
 - **Usage**: Perfect for centralizing and abstracting the logic of converting business results into HTTP responses.
 
 ### BusinessResultEndpoint  
@@ -49,7 +49,7 @@
 
 Each endpoint must implement two virtual methods:
 
-1. **Configure**: Called at application startup to define routes and associate them with handler methods (`MapGet`, `MapPost`, etc.). The returned `RouteHandlerBuilder` can be used to further customize endpoints.
+1. **Configure**: Invoked during application startup to define the route and HTTP method for an endpoint. It begins with methods like `MapGet`, `MapPost`, etc., to specify the route pattern. The returned `RouteHandlerBuilder` from the Map[HttpVerb] method can then be used for further endpoint customization.
 
 2. **HandleAsync**: Contains the logic to handle incoming requests. Called after the request is validated (if applicable).