Update README OfX-EFCore, Move OfXConfigFor guide to OfX because it i…

…s not depend on EfCore!

README.md

@@ -110,7 +110,20 @@ public sealed class SomeDataResponse
 }
 ```
 
-### 3. Write a Handler in Your Service to Fetch the Data when you are using OfX only. If you use OfX-gRPC or other transport data layer(next version extension packages), there are no need to create Handlers anymore!
+### 3. Mark the model you want to use with OfXAttribute
+Example:
+
+```csharp
+[OfXConfigFor<UserOfAttribute>(nameof(Id), nameof(Name))]
+public class User
+{
+    public string Id { get; set; }
+    public string Name { get; set; }
+    public string Email { get; set; }
+}
+```
+
+### 4. Write a Handler in Your Service to Fetch the Data when you are using OfX only. If you use OfX-gRPC, OfX-Nats... or other transport data layer(next version extension packages), there are no need to create Handlers anymore, they should be dynamic proxy handlers!
 Implement a handler to process data requests. For example:
 ```csharp
 public class UserRequestHandler(): IMappableRequestHandler<UserOfAttribute>

src/OfX.EntityFrameworkCore/README.md

@@ -49,20 +49,8 @@ builder.Services.AddOfXEntityFrameworkCore(cfg =>
 });
 ```
 
-After installing the package OfX-EFCore, you can use the method `AddDbContexts()`, which takes `DbContext(s)` to executing.
+Here, you can use the method `AddDbContexts()`, which takes `DbContext(s)` to executing.
 
-### 2. Mark the model you want to use with OfXAttribute
-Example:
-
-```csharp
-[OfXConfigFor<UserOfAttribute>(nameof(Id), nameof(Name))]
-public class User
-{
-    public string Id { get; set; }
-    public string Name { get; set; }
-    public string Email { get; set; }
-}
-```
 That all! Let go to the moon!
 
 Note: In this release, Id is exclusively supported as a string. But hold tight—I'm gearing up to blow your mind with the next update! Stay tuned!