Fix broken docs links (#5085)

alexyadon · web-flow · commit c61f0ceada66 · 2021-02-25T14:09:49.000-06:00
* docs: fix broken links

Signed-off-by: Alex Yadon &lt;alex.yadon@ibm.com&gt;

* docs: use relative paths

Signed-off-by: Alex Yadon &lt;alex.yadon@ibm.com&gt;
diff --git a/docs/PLUGINS.md b/docs/PLUGINS.md
@@ -32,7 +32,7 @@ These binaries are used to start the shim process for containerd and allows
 containerd to manage those containers using the runtime shim api returned by
 the binary.
 
-See [runtime v2 documentation](runtime/v2/README.md)
+See [runtime v2 documentation](../runtime/v2/README.md)
 
 ### Proxy Plugins
 
diff --git a/docs/RUNC.md b/docs/RUNC.md
@@ -1,6 +1,6 @@
 containerd is built with OCI support and with support for advanced features provided by [runc](https://github.com/opencontainers/runc).
 
-We depend on a specific `runc` version when dealing with advanced features.  You should have a specific runc build for development.  The current supported runc commit is described in [`go.mod`](go.mod). Please refer to the line that starts with `github.com/opencontainers/runc`.
+We depend on a specific `runc` version when dealing with advanced features.  You should have a specific runc build for development.  The current supported runc commit is described in [`go.mod`](../go.mod). Please refer to the line that starts with `github.com/opencontainers/runc`.
 
 For more information on how to clone and build runc see the runc Building [documentation](https://github.com/opencontainers/runc#building).
 
diff --git a/docs/cri/containerd.png b/docs/cri/containerd.png
diff --git a/docs/cri/installation.md b/docs/cri/installation.md
@@ -82,7 +82,7 @@ Information about the binaries in the release tarball:
 |               runc             | seccomp, apparmor, selinux  | linux |     amd64    |
 
 
-If you have other requirements for the binaries, e.g. another architecture support etc., you need to build the binaries yourself following [the instructions](../BUILDING.md).
+If you have other requirements for the binaries, e.g. another architecture support etc., you need to build the binaries yourself following [the instructions](../../BUILDING.md).
 
 ### Download
 
diff --git a/docs/cri/performance.png b/docs/cri/performance.png
diff --git a/docs/cri/testing.md b/docs/cri/testing.md
@@ -5,7 +5,7 @@ This document assumes you have already setup the development environment (go, gi
 Before sending pull requests you should at least make sure your changes have passed code verification, unit, integration and CRI validation tests.
 
 ## Build
-Follow the [building](../BUILDING.md) instructions.
+Follow the [building](../../BUILDING.md) instructions.
 
 ## CRI Integration Test
 * Run CRI integration test:
