Update build overview / pinned dependency doc

Author: ryyppy

pages/docs/manual/latest/build-overview.mdx

@@ -11,43 +11,37 @@ ReScript comes with a build system, bsb, that's meant to be fast, lean and used
 
 The build description file is called `bsconfig.json`. Every ReScript project needs one.
 
-**To build a project**, run:
+## Build Project 
+
+Each build will create build artifacts from your project's source files.
+
+**To build a project (including its dependencies / pinned-dependencies)**, run:
 
 ```sh
 bsb -make-world
 ```
 
 Add `-w` to keep the built-in watcher running. Any new file change will be picked up and the build will re-run.
 
-**Note**: third-party libraries (in `node_modules`) aren't watched, as doing so may exceed the node.js watcher count limit. If you're doing quick and dirty modifications inside `node_modules`, you have to do `bsb -clean-world -make-world` to rebuild them.
-
-**Note 3**: If you are developing across multiple devices, you may find the `-ws` configuration useful in order to have live-reloading across the network. Possible configurations are:
-- `bsb -make-world -w -ws _` (default)
-- `bsb -make-world -w -ws 0.0.0.0:9999`
-- `bsb -make-world -w -ws 5000`
+**Note**: third-party libraries (in `node_modules`, or via `pinned-dependencies`) aren't watched, as doing so may exceed the node.js watcher count limit.
 
-**To build only yourself**, use `bsb`.
+**Note 2**: In case you want to set up a project in a JS-monorepo-esque approach (`yarn workspaces` / `lerna`) where changes in your sub packages should be noticed by the compiler (`bsb -make-world`), you will need to define pinned dependencies in your main project's `bsconfig.json`. More details [here](./build-pinned-dependencies).
 
-`bsb -help` to see all the available options.
+**To build only your project's files (without dependencies)**, run:
 
-## Artifacts Cleaning
-
-If you ever get into a stable build for edge-case reasons, use:
 
 ```sh
-bsb -clean-world
+bsb
 ```
 
-Or `bsb -clean` to clean only your own artifacts.
+## Clean Project
 
-## Editor Support
+If you ever get into a stale build for edge-case reasons, use:
 
-Bsb generates a `.merlin` file, used by various [editor plugins](editor-plugins.md) under the hood to power e.g. autocomplete, type hint, diagnosis, etc.
-
-### Tips & Tricks
-
-A typical problem with traditional build systems is that they're not resilient against the user moving/deleting source files. Most don't clean up the old artifacts correctly after such user action\*. Bsb is unfortunately no different, **unless** you turn on `"suffix": ".bs.js"` in `bsconfig.json`, in which case we can track which JS artifact belongs to which source file correctly, even against source file moving/deletion.
+```sh
+bsb -clean-world
+```
 
-## Design Decisions
+This will clean all your project's build artifacts, including those in your dependencies. Alternatively you can run `bsb -clean` to clean your project's build artifacts only.
 
-\* One such build system that tracks these correctly & efficiently is [Tup](http://gittup.org/tup/). See the (rather accessible!) paper [here](http://gittup.org/tup/build_system_rules_and_algorithms.pdf). Unfortunately, Tup's implementation uses FUSE and other systems, which we can't safely use on every platform.
+For more infos, run `bsb -help` to see all the available options.

pages/docs/manual/latest/build-pinned-dependencies.mdx

@@ -14,7 +14,7 @@ Usually we'd recommend to use ReScript in a single-codebase style: One `bsconfig
 There are scenarios where you still want to connect and build multiple independent ReScript packages for one main project though. This is where `pinned-dependencies` come into play.
 
 
-### Package Types
+## Package Types
 
 Before we go into detail, let's first explain all the different package types recognized by the build system:
 
@@ -24,7 +24,7 @@ Before we go into detail, let's first explain all the different package types re
 
 Whenever a package is being built (`bsb -make-world`), the build system will build the toplevel package with its pinned-dependencies. So any changes made in a pinned dependency will automatically be reflected in the final app.
 
-### Build System Package Rules
+## Build System Package Rules
 
 The build system respects the following rules for each package type: