Call it a tool

[kconfig-hardened-check.git] / README.md

diff --git a/README.md b/README.md
index e21c85962f0f05ac9487a99adadb9449b3bf66d1..9d557b861f2b44b77ff6d0c3546e1963184137ea 100644 (file)
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# Kconfig hardened check
+# kconfig-hardened-check
 
 ## Motivation
 
@@ -26,7 +26,7 @@ or exploitation techniques.
   - ARM64
   - ARM
 
-## Script output examples
+## Output examples
 
 ### Usage
 ```
@@ -45,7 +45,7 @@ optional arguments:
   --json                print results in JSON format
 ```
 
-### Script output for `Ubuntu 18.04 (Bionic Beaver with HWE)` kernel config
+### Output for `Ubuntu 18.04 (Bionic Beaver with HWE)` kernel config
 ```
 $ ./kconfig-hardened-check.py -c config_files/distros/ubuntu-bionic-generic.config
 [+] Trying to detect architecture in "config_files/distros/ubuntu-bionic-generic.config"...
@@ -201,7 +201,7 @@ So the version of `kconfig-hardened-check` is associated with the corresponding
 
 The version format is: __[major_number].[kernel_version]__
 
-The current version of `kconfig-hardened-check` is __0.5.3__, it's marked with the git tag.
+The current version of `kconfig-hardened-check` is __0.5.5__, it's marked with the git tag.
 
 
 ## Questions and answers
@@ -209,7 +209,7 @@ The current version of `kconfig-hardened-check` is __0.5.3__, it's marked with t
 __Q:__ How disabling `CONFIG_USER_NS` cuts the attack surface? It's needed for containers!
 
 __A:__ Yes, the `CONFIG_USER_NS` option provides some isolation between the userspace programs,
-but the script recommends disabling it to cut the attack surface __of the kernel__.
+but the tool recommends disabling it to cut the attack surface __of the kernel__.
 
 The rationale: