guide: fix links that shouold go to now how-to

content/docs/command-reference/config.md

@@ -190,10 +190,9 @@ This section contains the following options, which affect the project's
 - `cache.shared` - permissions for newly created or downloaded cache files and
   directories. The only accepted value right now is `group`, which makes DVC use
   `664` (rw-rw-r--) for files and `775` (rwxrwxr-x) for directories. This is
-  useful when
-  [sharing data storage](/doc/use-cases/sharing-resources-efficiently). The
-  default permissions for cache files is system dependent. In Linux and macOS
-  for example, they're determined using
+  useful when [sharing a cache](/doc/user-guide/how-to/share-a-dvc-cache) among
+  projects. The default permissions for cache files is system dependent. In
+  Linux and macOS for example, they're determined using
   [`os.umask`](https://docs.python.org/3/library/os.html#os.umask).
 
 The following parameters allow setting an

content/docs/command-reference/gc.md

@@ -80,11 +80,10 @@ The default remote is cleaned (see `dvc config core.remote`) unless the
   [experimental](/doc/user-guide/experiment-management) data (including
   checkpoints).
 
-- `-p <paths>`, `--projects <paths>` - if a single remote or a single cache is
-  shared among different projects (e.g. as described
-  [here](/doc/use-cases/sharing-resources-efficiently)), this option can be used
-  to specify a list of them (each project is a path) to keep data that is
-  currently referenced from them.
+- `-p <paths>`, `--projects <paths>` - if a single remote or a single
+  [cache is shared](/doc/user-guide/how-to/share-a-dvc-cache) among different
+  projects, this option can be used to specify a list of them (each project is a
+  path) to keep data that is currently referenced from them.
 
 - `-c`, `--cloud` - remove files in remote storage in addition to local cache.
   **This option is dangerous.** The default remote is used unless a specific one

content/docs/start/data-and-model-versioning.md

@@ -250,9 +250,8 @@ In cases where you process very large datasets, you need an efficient mechanism
 versions. Do you use network attached storage (NAS)? Or a large external volume?
 You can learn more about advanced workflows using these links:
 
-- A [shared cache](/doc/use-cases/sharing-resources-efficiently) can be set up
-  to store, version and access a lot of data on a large shared volume
-  efficiently.
+- A [shared cache](/doc/user-guide/how-to/share-a-dvc-cache) can be set up to
+  store, version and access a lot of data on a large shared volume efficiently.
 - A quite advanced scenario is to track and version data directly on the remote
   storage (e.g. S3). See
   [Managing External Data](https://dvc.org/doc/user-guide/managing-external-data)

content/docs/use-cases/versioning-data-and-model-files/index.md

@@ -62,11 +62,10 @@ Benefits of our approach include:
   DVC [optimizes](/doc/user-guide/large-dataset-optimization) storing and
   transferring large files.
 
-- **Collaboration**: Easily distribute your project development and
-  [share limited resources](/doc/use-cases/sharing-resources-efficiently).
-  [Access results](/doc/use-cases/sharing-data-and-model-files) from anywhere,
-  or [reuse data and models](/doc/start/data-and-model-access) it in other
-  places.
+- **Collaboration**: Easily distribute your project development and share its
+  data [internally](/doc/user-guide/how-to/share-a-dvc-cache) and
+  [remotely](/doc/use-cases/sharing-data-and-model-files), or
+  [reuse](/doc/start/data-and-model-access) it in other places.
 
 - **Data compliance**: Review data modification attempts as Git
   [pull requests](https://www.dummies.com/web-design-development/what-are-github-pull-requests/).

content/docs/user-guide/managing-external-data.md

@@ -65,7 +65,7 @@ location, e.g. `s3://mybucket/cache` or `ssh://[email protected]/cache` (see the
 examples below).
 
 > ⚠️ An external cache could be
-> [shared](/doc/use-cases/sharing-resources-efficiently) among copies of a DVC
+> [shared](/doc/user-guide/how-to/share-a-dvc-cache) among copies of a DVC
 > project. Please **do not** use external outputs in that scenario, as
 > `dvc checkout` in any project would overwrite the working data for all
 > projects.