From c07237df33f488c3cc2a0799dbc58f6f6b3871b5 Mon Sep 17 00:00:00 2001
From: Rajas Paranjpe <52586855+ChocolateLoverRaj@users.noreply.github.com>
Date: Wed, 28 Feb 2024 15:07:28 -0800
Subject: [PATCH] Add other vkcube command to Linux docs (#8543)

Add other vkcube command to Linux docs

Release Notes:

- N/A
---
 docs/src/developing_zed__building_zed_linux.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/developing_zed__building_zed_linux.md b/docs/src/developing_zed__building_zed_linux.md
index ae87c49b44..394fe4bd83 100644
--- a/docs/src/developing_zed__building_zed_linux.md
+++ b/docs/src/developing_zed__building_zed_linux.md
@@ -84,6 +84,6 @@ Try `cargo clean` and `cargo build`.
 
 ### Vulkan/GPU issues
 
-If Zed crashes at runtime due to GPU or vulkan issues, you can try running [vkcube](https://github.com/krh/vkcube) (usually available as part of the `vulkaninfo` package on various distributions) to try to troubleshoot where the issue is coming from. Try running in both X11 and wayland modes (`vkcube -m [x11|wayland]`).
+If Zed crashes at runtime due to GPU or vulkan issues, you can try running [vkcube](https://github.com/krh/vkcube) (usually available as part of the `vulkaninfo` package on various distributions) to try to troubleshoot where the issue is coming from. Try running in both X11 and wayland modes by running `vkcube -m [x11|wayland]`. Some versions of `vkcube` use `vkcube` to run in X11 and `vkcube-wayland` to run in wayland.
 
 If you have multiple GPUs, you can also try running Zed on a different one (for example, with [vkdevicechooser](https://github.com/jiriks74/vkdevicechooser)) to figure out where the issue comes from.