From 058b047b53e30434652b486bbb9842dc6a5644e0 Mon Sep 17 00:00:00 2001 From: Krzysztof Taborowski <52448413+ktaborowski@users.noreply.github.com> Date: Wed, 18 Sep 2024 14:42:27 +0200 Subject: [PATCH] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Anna WojdyƂo <104991729+annwoj@users.noreply.github.com> --- doc/samples/sid_end_device.rst | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/samples/sid_end_device.rst b/doc/samples/sid_end_device.rst index d45a53e127..c28561091c 100644 --- a/doc/samples/sid_end_device.rst +++ b/doc/samples/sid_end_device.rst @@ -132,13 +132,12 @@ For example: Secure Key Storage support ========================== -The Sidewalk Platform Abstraction Layer for nRF Connect SDK supports a trusted storage mechanism for non-volatile Sidewalk keys, -ensuring they are stored persistently and confidentially. +The Sidewalk Platform Abstraction Layer for nRF Connect SDK supports a trusted storage mechanism for non-volatile Sidewalk keys, ensuring they are stored persistently and confidentially. The feature is enabled by default with the ``CONFIG_SIDEWALK_CRYPTO_PSA_KEY_STORAGE`` Kconfig option. .. note:: - Once keys are moved to trusted storage, it is impossible to retrieve them back in mfg storage. + Once keys are moved to trusted storage, it is impossible to retrieve them back into MFG storage. Therefore, you must not update your firmware to versions that do not support trusted storage for non-volatile Sidewalk keys. Device Firmware Upgrade support