[PATCH 4/9] doc: bootchooser: don't recommend NV backend

[Bastian Krause <bst@pengutronix.de>]

The NV storage backend for bootchooser variables is featured rather
prominently, but in fact it should not be used for anything else than
maybe evaluation.

This matches the reasoning of commit 48091deb4b9 ("bootchooser: warn if
NV is used instead of barebox-state").

Signed-off-by: Bastian Krause <bst@pengutronix.de>
---
 Documentation/user/bootchooser.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/user/bootchooser.rst b/Documentation/user/bootchooser.rst
index f9763a1fe14..b54e6873bc8 100644
--- a/Documentation/user/bootchooser.rst
+++ b/Documentation/user/bootchooser.rst
@@ -13,8 +13,9 @@ and implements an algorithm which selects the highest priority target to boot.
 
 Making *bootchooser* work requires a fixed set of configuration parameters
 and a storage backend for saving status information.
-Currently supported storage backends are either nv variables or the
-barebox *state* framework.
+Currently supported storage backends are either the barebox *state* framework
+or nv variables (fallback only, not meant for production, because it's not
+power-fail safe).
 
 *Bootchooser* itself is executed as a normal barebox boot target, i.e. one
 can start it via::
-- 
2.39.5