docs: remove notes about shared store limitations

Since v0.47.0 shared stores work fine on all versions of Node

docs/README.md

@@ -11,7 +11,6 @@
 * Advanced
   * [store.yaml](store-yaml.md)
 * Recipes
-  * [Shared store](recipes/shared-store.md)
   * [Usage in monorepos](recipes/usage-in-monorepos.md)
   * [Continuous Integration](recipes/continuous-integration.md)
 * [Contributing](../CONTRIBUTING.md)

docs/recipes/shared-store.md

@@ -1,15 +0,0 @@
-# Shared store
-
-A shared storage saves tons of space! However, a shared store is used by default only on Node.js >= v6.3.0. The reason for that is because
-it uses the `--preserve-symlinks` option (read more about it: [nodejs/node#3402](https://github.com/nodejs/node/issues/3402)).
-
-For pre 6.3.0 pnpm creates a separate store for every package in it's `node_modules` folder. However, it is possible to change the value of
-the `store-path` config key and force `pnpm` to use a shared storage.
-
-The easiest way to do it is via the command line:
-
-```sh
-pnpm config set store-path ~/.store
-```
-
-**Disclaimer!** Packages like babel that heavily rely on peer dependencies won't work with a shared storage without the `--preserve-symlinks` flag.

docs/recipes/usage-in-monorepos.md

@@ -1,6 +1,6 @@
 # Usage in monorepos
 
-`pnpm`'s ability to use a [shared store](./shared-store.md) makes it a perfect choice
+`pnpm`'s usage of a global store makes it a perfect choice
 for monorepo projects. But there are even more benefits you'll get!
 
 When you work in a monorepo, you need all your dependencies linked together via `npm link`.

examples/monorepo/README.md

@@ -20,12 +20,6 @@ This is the most important change for a monorepo.
 The `link-local` config makes `pnpm` symlink local dependencies and convert them to semver
 dependencies before publish. More details about this option at: [usage in monorepos](../../docs/recipes/usage-in-monorepos.md)
 
-**store-path = ~/.store**
-
-This makes `pnpm` use a global store. Packages in monorepos usually have a big set of common
-dependencies. A common store will keep all the dependencies in one place, giving a huge boost
-to the installation time. More details about shared stores [here](../../docs/recipes/shared-store.md).
-
 **save-exact = false**
 
 Specifying a `save-exact` config in the root of your monorepo is not obligatory but a good thing.