From dd5eab1631d711a4f097e1ad585bc5fa6086ec87 Mon Sep 17 00:00:00 2001 From: tituspijean Date: Wed, 23 Jun 2021 09:27:58 +0200 Subject: [PATCH] Fix typo in noaccess.md --- .../01.administrate/08.troubleshooting/03.noaccess/noaccess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/01.administrate/08.troubleshooting/03.noaccess/noaccess.md b/pages/01.administrate/08.troubleshooting/03.noaccess/noaccess.md index 172ed93c..d5f145db 100644 --- a/pages/01.administrate/08.troubleshooting/03.noaccess/noaccess.md +++ b/pages/01.administrate/08.troubleshooting/03.noaccess/noaccess.md @@ -120,7 +120,7 @@ If you are in "rescue" mode with `grub`, it may be due a misconfiguration of `gr In that case, access the storage drive from another system (your provider's "rescue" mode, live USB drive, read the SD or drive on another computer) and try to check partitions integrity with `smartctl`, `fsck`, and `mount`. -If disks are corrupted or hard to _miunt_, you have to save your data and maybe reformat, reinstall, and/or change the drive. If you succeed in mounting the drive, you can use `systemd-nspawn` to access its database. +If disks are corrupted or hard to mount, you have to save your data and maybe reformat, reinstall, and/or change the drive. If you succeed in mounting the drive, you can use `systemd-nspawn` to access its database. Otherwise, run `grub-update`, `grub-install` again with `chroot` or with `systemd-nspawn`.