doc: nrf: templates: Use FOO for sample Kconfig

Uses a name which is already in the allow list

Signed-off-by: Jamie McCrae <[email protected]>

Author: nordicjm

doc/nrf/app_dev/config_and_build/sysbuild/sysbuild_images.rst

@@ -162,7 +162,7 @@ This can be handled using the following approach:
           # This will set a bool Kconfig option in the image (note: sysbuild forces this setting, it cannot be overwritten by changing the application configuration)
           set_config_bool(${SB_CONFIG_NETCORE_IMAGE_NAME} CONFIG_MY_CUSTOM_CONFIG y)
           # This will set a string (or numeric) Kconfig option in the image (note: sysbuild forces this setting, it cannot be overwritten by changing the application configuration)
-          set_property(TARGET ${SB_CONFIG_NETCORE_IMAGE_NAME} APPEND_STRING PROPERTY CONFIG "CONFIG_CUSTOM_STRING=my_custom_value\n")
+          set_property(TARGET ${SB_CONFIG_NETCORE_IMAGE_NAME} APPEND_STRING PROPERTY CONFIG "CONFIG_FOO=my_custom_value\n")
         endif()
 
 .. _sysbuild_images_adding_custom_firmware_loader_images:
@@ -223,7 +223,7 @@ This can be handled using the following approach:
           # This will set a bool Kconfig option in the image (note: sysbuild forces this setting, it cannot be overwritten by changing the application configuration)
           set_config_bool(${SB_CONFIG_FIRMWARE_LOADER_IMAGE_NAME} CONFIG_MY_CUSTOM_CONFIG y)
           # This will set a string (or numeric) Kconfig option in the image (note: sysbuild forces this setting, it cannot be overwritten by changing the application configuration)
-          set_property(TARGET ${SB_CONFIG_FIRMWARE_LOADER_IMAGE_NAME} APPEND_STRING PROPERTY CONFIG "CONFIG_CUSTOM_STRING=my_custom_value\n")
+          set_property(TARGET ${SB_CONFIG_FIRMWARE_LOADER_IMAGE_NAME} APPEND_STRING PROPERTY CONFIG "CONFIG_FOO=my_custom_value\n")
         endif()
 
 .. _sysbuild_images_adding_to_a_single_board:

doc/nrf/templates/application_README.rst

@@ -128,7 +128,7 @@ Additional configuration*
 
 .. note::
    * Add this section to describe and link to any library configuration options that might be important to run this application.
-     You can link to options with ``:kconfig:option:`CONFIG_XXX```.
+     You can link to options with ``:kconfig:option:`CONFIG_FOO```.
    * You need not list all possible configuration options, but only the ones that are relevant.
 
 Check and configure the following library options that are used by the application:

doc/nrf/templates/sample_README.rst

@@ -151,7 +151,7 @@ Additional configuration*
 
 .. note::
    * Add this section to describe and link to any library configuration options that might be important to run this sample.
-     You can link to options with ``:kconfig:option:`CONFIG_XXX```.
+     You can link to options with ``:kconfig:option:`CONFIG_FOO```.
    * You do not need to list all possible configuration options, but only the ones that are relevant.
 
 Check and configure the following library options that are used by the sample:

include/util/util_macro.h

@@ -80,9 +80,9 @@ extern "C" {
  *
  * Example:
  *
- *     IF_ENABLED_ALL((CONFIG_FLAG_A, CONFIG_FLAG_B), uint32_t foo;)
+ *     IF_ENABLED_ALL((CONFIG_FOO, CONFIG_BAR), uint32_t foo;)
  *
- * If @p CONFIG_FLAG_A and @p CONFIG_FLAG_B are defined to 1, this expands to:
+ * If @p CONFIG_FOO and @p CONFIG_BAR are defined to 1, this expands to:
  *
  *     uint32_t foo;
  *
@@ -102,9 +102,9 @@ extern "C" {
  *
  * Example:
  *
- *     IF_ENABLED_ANY((CONFIG_FLAG_A, CONFIG_FLAG_B), uint32_t foo;)
+ *     IF_ENABLED_ANY((CONFIG_FOO, CONFIG_BAR), uint32_t foo;)
  *
- * If @p CONFIG_FLAG_A or @p CONFIG_FLAG_B defined to 1, this expands to:
+ * If @p CONFIG_FOO or @p CONFIG_BAR defined to 1, this expands to:
  *
  *     uint32_t foo;
  *