fixup! ci: remove lerna, leverage basic shell script

Author: ElysaSrc

README.md

@@ -18,12 +18,12 @@ The version numbers for our releases are solely managed through git tags. It imp
 
 It's the tradeoff we make to keep the project simple and easy to manage, and to avoid the complexity of managing multiple compatible versions of the project.
 
-In summary : we conside a version number as being an indivisible release of all the subpackages of the repository.
+In summary : we consider a version number as being an indivisible release of all the subpackages of the repository.
 
 ### Making a release
 
 1. Create a git tag (let's say `0.0.30`) on the `dev` branch and push it. **Note: we do not tag with a V in front of the semver, IT'S 0.0.30 AND NOT v0.0.30**.
-2. Create a github release (By convention, we use the same name as the tag with a v in front of it, `v0.0.30`. You can give fancy names to release if you want to : `0.0.30 : Camembert`, it will only appear in the release page of GitHub).
+2. Create a github release (By convention, we use the same name as the tag with the letter `v` in front of it, `v0.0.30`. You can give fancy names to release if you want to : `0.0.30 : Camembert`, it will only appear in the release page of GitHub).
 
 ### Adding a new package to the monorepo