diff --git a/docs/docs/101/volumes.md b/docs/docs/101/volumes.md
index d77ba7c8c..690604d33 100644
--- a/docs/docs/101/volumes.md
+++ b/docs/docs/101/volumes.md
@@ -1,6 +1,6 @@
 # Volumes
 
-[Volumes Documentation](https://github.com/Mirantis/virtlet/blob/master/docs/volumes.md)
+[Volumes Documentation](https://github.com/Mirantis/virtlet/blob/master/docs/docs/reference/volumes.md)
 
 Virtlet supports Kubernetes Volumes in a several ways:
 
diff --git a/docs/docs/dev/architecture.md b/docs/docs/dev/architecture.md
index 97e9121cc..1307e14be 100644
--- a/docs/docs/dev/architecture.md
+++ b/docs/docs/dev/architecture.md
@@ -22,7 +22,7 @@ node.
 ## Virtlet manager
 
 The main binary is responsible for providing API fullfiling
-[CRI specification](https://github.com/kubernetes/community/blob/master/contributors/design-proposals/container-runtime-interface-v1.md).
+[CRI specification](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md).
 It serves the requests from kubelet by doing the following:
 
 * setting up libvirt VM environment (virtual drives, network
diff --git a/docs/docs/dev/vm-pod-lifecycle.md b/docs/docs/dev/vm-pod-lifecycle.md
index 9e846b146..d2eff1682 100644
--- a/docs/docs/dev/vm-pod-lifecycle.md
+++ b/docs/docs/dev/vm-pod-lifecycle.md
@@ -25,7 +25,7 @@ Virtlet-specific annotation or an image that has Virtlet-specific prefix.
    (CPU, memory, etc.) as well as pod's nodeSelector and pod/node affinity
    constraints, taints/tolerations and so on.
  * `kubelet` running on the target node accepts the pod.
- * `kubelet` invokes a [CRI](https://contributor.kubernetes.io/contributors/devel/container-runtime-interface/)
+ * `kubelet` invokes a [CRI](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md)
    call RunPodSandbox to create the pod sandbox which
    will enclose all the containers in the pod definition. Note that at this
    point no information about the containers within the pod is passed
@@ -51,7 +51,7 @@ Virtlet-specific annotation or an image that has Virtlet-specific prefix.
    `PullImage` CRI call to pull the image if it doesn't exist or if
    `imagePullPolicy: Always` is used.
  * If `PullImage` is invoked, Virtlet resolves the image location based on the
-   [image name translation configuration](https://github.com/Mirantis/virtlet/blob/master/docs/image-name-translation.md),
+   [image name translation configuration](https://github.com/Mirantis/virtlet/blob/master/docs/docs/reference/images.md#image-name-translation),
    then downloads the file and stores it in the image store.
  * After the image is ready (no pull was needed or the `PullImage` call completed
    successfully), kubelet uses `CreateContainer` CRI call to create
diff --git a/docs/docs/reference/networking.md b/docs/docs/reference/networking.md
index 634520222..76c8eee07 100644
--- a/docs/docs/reference/networking.md
+++ b/docs/docs/reference/networking.md
@@ -83,7 +83,7 @@ Each CNI config must include `cniVersion` field, with minimum version being
 
 ## Sample configuration
 
-Please refer to the [detailed documentation](https://github.com/Mirantis/virtlet/blob/master/docs/multiple-interfaces.md#example-files)
+Please refer to the [detailed documentation](https://github.com/Mirantis/virtlet/blob/master/docs/docs/reference/networking.md#-setting-up-multiple-cnis)
 that contains an example of configuration files for CNI Genie with Calico being used for
 the primary interface and Flannel being used for the secondary one.
 
diff --git a/docs/docs/reference/volumes.md b/docs/docs/reference/volumes.md
index 5879c536c..2f5938425 100644
--- a/docs/docs/reference/volumes.md
+++ b/docs/docs/reference/volumes.md
@@ -104,7 +104,7 @@ enabling read-write access for the VM.
 ## Using FlexVolumes
 
 Virtlet uses custom
-[FlexVolume](https://github.com/kubernetes/community/blob/master/contributors/devel/flexvolume.md)
+[FlexVolume](https://kubernetes.io/docs/concepts/storage/volumes/#flexvolume)
 driver (`virtlet/flexvolume_driver`) to specify block devices for the
 VMs. Flexvolume options must include `type` field with one of the
 following values: