update README.md

README.md

@@ -1,15 +1,15 @@
 # Monorepo
 
-This is a bazel monorepo that I'm hoping eventually will contain most of my side-projects.
+This is a bazel monorepo containing most of my side-projects and websites etc. Using a monorepo in this way makes it much easier to ensure linting and deployment are consistent across many projects, and prevents a lot of version rot.
 
-Via the github actions workflows in [.github/workflows/ci.yml], changes in any dependencies are automatically tested and merged.
+## Usage
 
-Then, a secondary action runs which increments any version numbers necessary and commits to the [versioned branch]. This branch tracks and increments versions for export to third-party package managers like NPM.
+The repo is going through a bit of an identity crisis at the moment. I have just completed migration to rules_js, which uses PNPM -- and the PNPM binary is controlled by bazel itself.
 
-[.github/workflows/ci.yml]: .github/workflows/ci.yml
-[versioned branch]: https://github.com/Zemnmez/monorepo/tree/versioned
+I recommend having a local 'bazel' installation. However, if you just have NPM installed, you can:
 
-The deploy scripts in [deploy/BUILD] run only on the versioned branch.
+```
+npx @bazel/bazelisk test //...
+```
 
-
-[deploy/build]: deploy/BUILD
+This will recursively run all tests in parallel.