author: Bhaskar Chowdhury <unixbhaskar@gmail.com> 2021-01-07 18:26:10 +0530
committer: Jonathan Corbet <corbet@lwn.net> 2021-01-07 14:44:58 -0700
commit: 9d54ee78aef62c29b15ae2f58a70b1d1cd63a8f0
parent: 25942e5ecbac33918ec2f0869ca9a374dbb023f2
Commit Summary:
Diffstat:
1 file changed, 1 insertion, 1 deletion
diff --git a/Documentation/admin-guide/bootconfig.rst b/Documentation/admin-guide/bootconfig.rst
index 9b90efcc3a35..452b7dcd7f6b 100644
--- a/Documentation/admin-guide/bootconfig.rst
+++ b/Documentation/admin-guide/bootconfig.rst
@@ -154,7 +154,7 @@ get the boot configuration data.
Because of this "piggyback" method, there is no need to change or
update the boot loader and the kernel image itself as long as the boot
loader passes the correct initrd file size. If by any chance, the boot
-loader passes a longer size, the kernel feils to find the bootconfig data.
+loader passes a longer size, the kernel fails to find the bootconfig data.
To do this operation, Linux kernel provides "bootconfig" command under
tools/bootconfig, which allows admin to apply or delete the config file