- update README

Author: modabas

README.md

@@ -8,7 +8,7 @@
 
 [WebResultEndpoints](#webresultendpoint), [BusinessResultEndpoints](#businessresultendpoint), and [ServiceEndpoints](#serviceendpoint) structure ASP.NET Core Minimal APIs into REPR format endpoints and seamlessly integrate with the [result](https://github.com/modabas/ModResults) pattern. WebResultEndpoints transform the business result returned by the handler method into a Minimal API IResult for client responses, while BusinessResultEndpoints and ServiceEndpoints directly return the raw business result. These are provided within the <ins>ModEndpoints</ins> package.
 
-All endpoint abstractions are a structured approach to defining endpoints in ASP.NET Core applications. They extend the Minimal API pattern with reusable, testable, and consistent components for request handling, validation, and response mapping.
+All endpoint abstractions are a structured approach to defining endpoints in ASP.NET Core applications. They extend the Minimal API pattern with reusable, testable, and consistent components for request validation, handling, and response mapping.
 
 [ServiceEndpoint](#serviceendpoint) is a highly specialized endpoint intended to be used in conjunction with its dedicated [client implementation](#serviceendpoint-clients) in <ins>ModEndpoints.RemoteServices</ins> package. Aim is to abstract away HTTP plumbing on client side and enable remote service consumption with the knowledge of strongly typed request and response models shared between server and client projects. Additionally, <ins>ModEndpoints.RemoteServices.Core</ins> package contains the interfaces required for ServiceEndpoint request models.
 

src/ModEndpoints.RemoteServices/assets/README.md

@@ -1,3 +1,3 @@
 # ModEndpoints.RemoteServices
 
-Contains ServiceEndpoint client implementation along with extensions required for its registration.
+Contains ServiceEndpoint client implementation along with extensions required for its registration. In conjunction with ServiceEndpoints, aim is to abstract away HTTP plumbing on client side and enable remote service consumption with the knowledge of strongly typed request and response models shared between server and client projects.