Very minor, but interchanged usage of "partition label" and "volume label" can confuse the meaning.
Hope I got the meaning correct with this patch.
---
docs/USAGE.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/USAGE.md b/docs/USAGE.md
index 97a25cb..c0802b7 100644
--- a/docs/USAGE.md
+++ b/docs/USAGE.md
@@ -150,18 +150,18 @@ If you just specify a file name as `--kernelfile`, `efibootguard` loads the
kernel from the same FAT partition as the boot loader binary itself.
To load the kernel from a different FAT partition than `efibootguard`, there are
-two possible mechanisms. One directly uses the label of the FAT partition,
+two possible mechanisms. One directly uses the label of the FAT filesystem,
created with `dosfslabel`:
```
./bg_setenv -u --kernel="L:FATLABEL:kernelfile"
```
-where `FATLABEL` is the label of the FAT partition. On some older UEFI
+where `FATLABEL` is the label of the FAT filesystem. On some older UEFI
implementations, the label is not supported properly and a user defined label
can be created instead, which is a file named `EFILABEL` in the root directory
of the corresponding FAT partition. This file contains an UTF-16le encoded
-partition name and can be used as follows:
+filesystem name and can be used as follows:
```
./bg_setenv -u --kernel="C:USERLABEL:kernelfile"
--
2.54.0