From e77508a919b2d5583548235c4c3a8a5fcbdaaccc Mon Sep 17 00:00:00 2001
From: awokd <34515595+awokd@users.noreply.github.com>
Date: Sat, 14 Sep 2019 09:35:24 +0000
Subject: [PATCH] add another mapbs symptom to title

---
 user/advanced-configuration/uefi-troubleshooting.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/user/advanced-configuration/uefi-troubleshooting.md b/user/advanced-configuration/uefi-troubleshooting.md
index ae5d112a..9f29df1a 100644
--- a/user/advanced-configuration/uefi-troubleshooting.md
+++ b/user/advanced-configuration/uefi-troubleshooting.md
@@ -106,7 +106,7 @@ Consider this approach as a last resort, because it will make every Xen update a
 Whenever there is a kernel or Xen update for Qubes, you will need to follow [these steps](/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing) because your system is using the fallback UEFI bootloader in `[...]/EFI/BOOT` instead of directly booting to the Qubes entry under `[...]/EFI/qubes`.
 
 
-Installation completes successfully but then boot loops at boot device selection
+Installation completes successfully but then boot loops or hangs on black screen
 ---------------------
 
 There is a [common bug in UEFI implementation](http://xen.markmail.org/message/f6lx2ab4o2fch35r) affecting mostly Lenovo systems, but probably some others too.