...

diff --git a/README.txt b/README.txt
index d8902182b1466e94bcd6c76d6af37d2ddb66d202..163318931e682e3e5ae7f5289b8e927686e1b891 100644 (file)
--- a/README.txt
+++ b/README.txt
@@ -147,11 +147,11 @@ Primary problems to tackle:
 Three primary GUI flows need to be created.
 
 First flow is satisfying dependencies:
--automated installing of required packages: jq, mkfs.ext4 (part of the e2fsprogs package), curl (for downloading Bitcoin Core), gpg (for validating Bitcoin Core)
+-automated installing of required packages: jq, curl (for downloading Bitcoin Core), gpg (for validating Bitcoin Core)
 -automated installing and validation of Bitcoin Core
 -once all dependencies setup, shutdown networking and start Bitcoin Core
 
-NOTE: mount/umount have C bindings (see `man mount.2` and `man umount.2`). The functionality of nmcli, shred, eject, base64, and wipefs should be able to be easily extracted from source-code of their respective packages and can be eliminated as dependencies. The rest of the commands used above (echo, tr, cat, dd)  can be eliminated by simple functions.
+NOTE: mount/umount have C bindings (see `man mount.2` and `man umount.2`). The functionality of nmcli, shred, eject, base64, and wipefs should be able to be easily extracted from source-code of their respective packages and can be eliminated as dependencies. mkfs.ext4 is part of the e2fsprogs package and is an essential package in Debian, meaning it must be available and usable (see https://www.debian.org/doc/debian-policy/ch-binary.html#essential-packages for more information). The rest of the commands used above (echo, tr, cat, dd)  can be eliminated by simple functions.
 
 Second flow is creating multi-signature setup:
 -entering passphrase and generating cryptsetup key