doc: security: fix references to inexistent Kconfig options

Remove or replace them.

Signed-off-by: Tomi Fontanilles <[email protected]>

Author: tomi-font

doc/nrf/app_dev/device_guides/nrf53/logging_nrf5340.rst

@@ -87,7 +87,6 @@ There are several options to get UART output from the secure TF-M:
 * Disable the output for the network core and change the pins used by TF-M.
   The network core usually has a child image.
   To configure logging in an |NCS| image, see :ref:`ug_logging`.
-  To change the pins used by TF-M, set the RXD (:kconfig:option:`CONFIG_TFM_UART1_RXD_PIN`) and TXD (:kconfig:option:`CONFIG_TFM_UART1_TXD_PIN`) Kconfig options in the application image to **P1.00** (32) and **P1.01** (33).
 
 * You can wire the secure and non-secure UART peripherals to the same pins.
   Specifically, physically wire together the pins **P0.25** and **P0.26** to **P0.20** and **P0.22**, respectively.

doc/nrf/security/tfm/tfm_building.rst

@@ -155,7 +155,7 @@ TF-M's Secure Partition Manager (SPM) backend may also be configured, depending
      - With IPC, each Secure Partition processes signals in any order, and can defer responding to a message while continuing to process other signals.
      - Levels 1, 2 and 3
 
-To control the number of logging messages, set the :kconfig:option:`CONFIG_TFM_LOG_LEVEL` Kconfig option.
+To control the number of logging messages, set the :kconfig:option:`CONFIG_TFM_SPM_LOG_LEVEL` Kconfig option.
 To disable logging, set the :kconfig:option:`CONFIG_TFM_LOG_LEVEL_SILENCE` option.
 
 The size of TF-M partitions is affected by multiple configuration options and hardware-related options.