diff --git a/en/troubleshooting/managed-kubernetes/known-issues/multi-attach-error-for-volume.md b/en/troubleshooting/managed-kubernetes/known-issues/multi-attach-error-for-volume.md
index dd789ebd79..d103830915 100644
--- a/en/troubleshooting/managed-kubernetes/known-issues/multi-attach-error-for-volume.md
+++ b/en/troubleshooting/managed-kubernetes/known-issues/multi-attach-error-for-volume.md
@@ -16,10 +16,13 @@ Such errors can also occur if the pods that should use the `volume` are located
 
 If you need to use `ReadWriteMany`, we recommend using CSI for our object storage because the volumes based on it support this access mode:
 
-Automatic installation via the marketplace or `Helm` chart is described [here](../../../docs/managed-kubernetes/operations/volumes/s3-csi-integration), and manual integration is described [here](../../../managed-kubernetes/operations/volumes/s3-csi-integration).
+Automatic installation via the marketplace or `Helm` chart is described [here](../../../managed-kubernetes/operations/volumes/s3-csi-integration.md), and manual integration is described [here](../../../managed-kubernetes/operations/volumes/s3-csi-integration.md?tabs=instructions_manual).
+
+
 
 
 ## If the issue persists {#if-issue-still-persists}
 
 If the actions described above did not help solve the issue, you can try to organize storage on your own. Some of the possible solutions also support multiple access (for example, nfs or CEPH). You can read more about this in the [k8s official documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes).
 
+