Update v3.0.md

Author: keroxp

changelogs/v3.0.md

@@ -6,29 +6,29 @@ Software Engineer at LoiLo Inc.
 
 ## Summary
 
-We release `exql` v3, the second major update since 2020. For additional 3 years after v2 release, we noticed that the tool is mature enough to keep using on the next 3 years.
+We are releasing `exql` v3, the second major update since 2020. Over the three years since the v2 release, we have found that the tool is mature enough to keep using for the next three years.
 
-To develop v3, we concentrated on tightening the security, backing to the our first design concept: **Safe**.
+In developing v3, we concentrated on tightening security and returning to our original design concept: **Safe**.
 
 ## Cleaning a Vulnerability
 
-`exql` is thin, dependency less tool. Until now, we were depending on few external modules to interpolate very small gaps.
+`exql` is a thin, dependency-small tool. Until now, we had relied on a few external modules to fill very small gaps.
 
-However, situations around us have been changed silently. We’re still using `exql` aggressively internally. Developers mostly are satisfied with features. Any other ORM libraries are absolutely not attaractive to us.
+However, the situation around us has changed silently. We still use `exql` aggressively internally. Developers are mostly satisfied with its features. Other ORM libraries are absolutely not attractive to us.
 
-We’ve seen a decline — or stabilization — of Go community in this several years. Many famous tools got archived and developers come to a diaspora. I know, of course, that is the right being of free open software. But, there’re things unacceptable: **Vulnerability**.
+Over the past several years, we have seen a decline, or at least a stabilization, in the Go community. Many well-known tools have been archived, and developers have dispersed. Of course, I understand that this is part of the nature of free and open source software. But there is one thing we cannot accept: **vulnerability**.
 
 ## Importance of Purity
 
-Recently we found a highly dangerous zero-day vulnerability within `exql` dependencies. I reported the issue to maintainers, recommending to fix the problem. But no message returned. Project is completely dead.
+Recently, we found a highly dangerous zero-day vulnerability in one of `exql`'s dependencies. I reported the issue to the maintainers and recommended that they fix the problem. But no response came back. The project is completely dead.
 
-So, we decided to remove all external dependencies and make us “pure” module from v3. Now all core logics are implemented by Go (`database/sql`) and `exql` itself.
+So, we decided to remove all external dependencies and make `exql` a "pure" module from v3 onward. Now all core logic is implemented in Go (`database/sql`) and `exql` itself.
 
 ## Migration
 
- From v3, for the field value of nullable columns of generated model, `loilo-inc/exql/v3/null` will be used. They are inheriting implementation of `sql.Null[T]`, added in Go 1.22. We additionally added several interfaces to interpolate a gap.
+From v3, `loilo-inc/exql/v3/null` will be used for nullable column fields in generated models. It inherits the implementation of `sql.Null[T]`, which was added in Go 1.22. We additionally added several interfaces to fill the remaining gap.
 
-`sql.Null[T` implements:
+`sql.Null[T]` implements:
 
 - `driver.Valuer`
 - `sql.Scanner`
@@ -39,22 +39,22 @@ So, we decided to remove all external dependencies and make us “pure” module
 - `json.Marshaler`
 - `encoding.TextUnmarshaler`
 
-Those are interfaces that were implemented in `volatiletech/null`.
+These are the interfaces that were implemented in `volatiletech/null`.
 
 ## Performance
 
-Introduced minor performance improvoments. For detail, see:
+We introduced minor performance improvements. For details, see:
 
 <https://github.com/loilo-inc/exql/pull/72>
 
 ## Breaking Changes
 
-- `exql.Mapper` has been removed for it was scheduled.
-- `xerrors` has been replaced with `errors` / `fmt` for deprecation.
+- `exql.Mapper` has been removed, as planned.
+- `xerrors` has been replaced with `errors` / `fmt` due to its deprecation.
 
 ### Error handling changes
 
-`exql.ErrRecordNotFound` has changed to struct from variable. Use `errors.Is` to check them. From v3, all explicit errors must be exported as struct.
+`exql.ErrRecordNotFound` has changed from a variable to a struct. Use `errors.Is` to check for it. From v3, all explicit errors are exported as structs.
 
 ```go
 err = MapRows(rows, &dest)
@@ -63,5 +63,3 @@ if errors.Is(err, ErrRecordNotFound{}) {
 }
 ```
 
-
-