From ea75ffd3e72d56f1d34b8b686b3b69e5f1d22acb Mon Sep 17 00:00:00 2001
From: John Tsichritzis <john.tsichritzis@arm.com>
Date: Fri, 5 Oct 2018 12:02:29 +0100
Subject: [PATCH] docs: Clarify usage of LOG_LEVEL
Change-Id: I1ce771a155e6e83885a00d2f05591bf98cd69854
Signed-off-by: John Tsichritzis <john.tsichritzis@arm.com>
---
docs/user-guide.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/user-guide.rst b/docs/user-guide.rst
index 2632329a2e..f4ef85d2a1 100644
--- a/docs/user-guide.rst
+++ b/docs/user-guide.rst
@@ -521,8 +521,8 @@ Common build options
40 (LOG_LEVEL_INFO)
50 (LOG_LEVEL_VERBOSE)
- All log output up to and including the log level is compiled into the build.
- The default value is 40 in debug builds and 20 in release builds.
+ All log output up to and including the selected log level is compiled into
+ the build. The default value is 40 in debug builds and 20 in release builds.
- ``NON_TRUSTED_WORLD_KEY``: This option is used when ``GENERATE_COT=1``. It
specifies the file that contains the Non-Trusted World private key in PEM
--
GitLab