encrypted-storage: use luks as the feature name for current implementation

encrypted-storage layer will include more security features about encrypted
storage so the term "encrypted-storage" won't be used to specify a dedicated
technology term such as "LUKS".

Signed-off-by: Jia Zhang <lans.zhang2008@gmail.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/meta-integrity/README.md b/meta-integrity/README.md
index 82db535..8ffd484 100644
--- a/meta-integrity/README.md
+++ b/meta-integrity/README.md
@@ -170,9 +170,9 @@ The following best practices should be applied with using IMA.
 
 - The default IMA rules provides the ability of measuring the boot components
   and calculating the aggregate integrity value for attesting. However, this
-  function conflicts with encrypted-storage feature which employs PCR policy
-  session to retrieve the passphrase in a safe way. If both of them are
-  enabled, the default IMA rules will be not used.
+  function conflicts with the luks feature which employs PCR policy session to
+  retrieve the passphrase in a safe way. If both of them are enabled, the
+  default IMA rules will be not used.
 
 ### Reference
 [Official IMA wiki page](https://sourceforge.net/p/linux-ima/wiki/Home/)