doc: remove app_name

greg-fer · greg-fer · commit 7c5dd88dbad1 · 2026-01-26T15:25:56.000+01:00
Removed app_name snippet from docs.

Signed-off-by: Grzegorz Ferenc &lt;Grzegorz.Ferenc@nordicsemi.no&gt;
diff --git a/doc/docs/index.md b/doc/docs/index.md
@@ -1,10 +1,10 @@
-# {{app_name}}
+# Programmer app
 
-The {{app_name}} in [nRF Connect for Desktop](https://docs.nordicsemi.com/bundle/nrf-connect-desktop/page/index.html) lets you program firmware to Nordic devices. The application allows you to see the memory layout for devices that support programming with J-Link, Nordic Secure DFU, and MCUboot. It also allows you to display content of HEX files and write it to the devices.
+The Programmer app in [nRF Connect for Desktop](https://docs.nordicsemi.com/bundle/nrf-connect-desktop/page/index.html) lets you program firmware to Nordic devices. The application allows you to see the memory layout for devices that support programming with J-Link, Nordic Secure DFU, and MCUboot. It also allows you to display content of HEX files and write it to the devices.
 
 ## Supported hardware
 
-The following table lists the hardware platforms that you can program with the {{app_name}}.
+The following table lists the hardware platforms that you can program with the Programmer app.
 
 | Hardware platform   | Device   | PCA number | Programming with J-Link  | Programming with Nordic Secure DFU  | Programming with MCUboot |
 |---------------------|----------|------------|--------------------------|-------------------------------------|--------------------------|
@@ -32,16 +32,16 @@ Programming with Nordic Secure DFU is **Possible** on some nRF52 Series platform
 
 ### Support for custom hardware
 
-The following criteria apply to programming custom hardware with the {{app_name}}:
+The following criteria apply to programming custom hardware with the Programmer app:
 
 - **Device**: The hardware platform you are programming must use an SoC or SiP from Nordic Semiconductor.
 - **Programming with J-Link**: Possible for all custom hardware that features Nordic SoCs supported by [nRF Util](https://docs.nordicsemi.com/bundle/nrfutil/page/README.html).
-- **Programming with Nordic Secure DFU**: Possible if you implement a bootloader solution that supports Nordic Secure DFU. The {{app_name}} checks the bootloader for Nordic ID to be able to program using this method.
+- **Programming with Nordic Secure DFU**: Possible if you implement a bootloader solution that supports Nordic Secure DFU. The Programmer app checks the bootloader for Nordic ID to be able to program using this method.
 - **Programming with MCUboot**: Only possible using CLI.
 
 ## Deprecated hardware support
 
-The following hardware platforms cannot be programmed with the {{app_name}} anymore.
+The following hardware platforms cannot be programmed with the Programmer app anymore.
 
 | Hardware platform   | Device   | PCA number | Programming with J-Link  | Programming with Nordic Secure DFU  | Programming with MCUboot |
 |---------------------|----------|------------|--------------------------|-------------------------------------|--------------------------|
diff --git a/doc/docs/installing.md b/doc/docs/installing.md
@@ -1,3 +1,3 @@
-# Installing the {{app_name}}
+# Installing the Programmer app
 
 For installation instructions, see [Installing nRF Connect for Desktop apps](https://docs.nordicsemi.com/bundle/nrf-connect-desktop/page/installing_apps.html) in the nRF Connect for Desktop documentation.
diff --git a/doc/docs/overview.md b/doc/docs/overview.md
@@ -1,10 +1,10 @@
 # Overview and user interface
 
-The {{app_name}} main window displays the memory layout of the device and the file you want to work with. It also provides options to program the device and inspect the entire process through the log.
+The Programmer app main window displays the memory layout of the device and the file you want to work with. It also provides options to program the device and inspect the entire process through the log.
 
-When you start the {{app_name}}, the application main window appears with the **Programmer** tab selected by default and the [**File Memory Layout**](#file-memory-layout) and [**Device Memory Layout**](#device-memory-layout) panels empty:
+When you start the Programmer app, the application main window appears with the **Programmer** tab selected by default and the [**File Memory Layout**](#file-memory-layout) and [**Device Memory Layout**](#device-memory-layout) panels empty:
 
-![{{app_name}} default view at startup](./screenshots/programmer_overview.png "{{app_name}} main window")
+![Programmer app default view at startup](./screenshots/programmer_overview.png "Programmer app main window")
 
 ## Select device
 
@@ -56,7 +56,7 @@ When you select a device, the following toggles are available in the J-Link Sett
 
 ### MCUboot Settings
 
-The experimental **Enable MCUBoot** toggle is deprecated and will be removed in a future release of the {{app_name}}.
+The experimental **Enable MCUBoot** toggle is deprecated and will be removed in a future release of the Programmer app.
 
 ## Programmer tab
 
@@ -68,7 +68,7 @@ Both windows display the different sections in the memory with different colors.
 
 ### File Memory Layout
 
-The **File Memory Layout** panel displays the memory layout for files added to the {{app_name}} with the [**Add file**](#file) option. Once added, these files can be programmed onto the device.
+The **File Memory Layout** panel displays the memory layout for files added to the Programmer app with the [**Add file**](#file) option. Once added, these files can be programmed onto the device.
 
 ![File Memory Layout panel](./screenshots/programmer_programmer_tab.png "File Memory Layout panel")
 
@@ -86,7 +86,7 @@ In the **Device Memory Layout**, you can read the name, address range, and size
 
 You can view application information, restore defaults, access source code and documentation. You also can find information on the selected device, access support tools, send feedback, and enable verbose logging.
 
-![{{app_name}} About tab](./screenshots/nRF_Connect_for_Desktop_Prog_about.png "{{app_name}} About tab")
+![Programmer app About tab](./screenshots/nRF_Connect_for_Desktop_Prog_about.png "Programmer app About tab")
 
 ## Log
 
diff --git a/doc/docs/programming_91dk.md b/doc/docs/programming_91dk.md
@@ -37,7 +37,7 @@ To program the nRF91 Series DK, you will also need the following USB cables:
 
 To update the modem firmware, application firmware, or NTN firmware, complete the following steps:
 
-1. Open the {{app_name}}.
+1. Open the Programmer app.
 2. Connect the DK to the computer with a USB cable, and then turn the DK on.
 3. Click **SELECT DEVICE** and select the DK from the drop-down list.<br/>
 
@@ -90,7 +90,7 @@ To update the modem firmware, application firmware, or NTN firmware, complete th
 
 To update the modem or application firmware, complete the following steps:
 
-1. Open the {{app_name}}.
+1. Open the Programmer app.
 2. Make sure the **PROG/DEBUG SW10** switch on the nRF9160 DK is set to **nRF91**.
    On DK v0.9.0 and earlier, this is the **SW5** switch.
 
diff --git a/doc/docs/programming_dk.md b/doc/docs/programming_dk.md
@@ -1,9 +1,9 @@
 # Programming devices
 
-In the {{app_name}}, you can program [supported devices](index.md#supported-hardware) or a custom board with a supported chip that allows for communication with J-Link, Nordic Secure DFU devices, and MCUboot devices.
+In the Programmer app, you can program [supported devices](index.md#supported-hardware) or a custom board with a supported chip that allows for communication with J-Link, Nordic Secure DFU devices, and MCUboot devices.
 
 !!! tip "Tip"
-      If you experience any problems during the programming process, press Ctrl-R (command-R on macOS) to restart the {{app_name}}, and try programming again.
+      If you experience any problems during the programming process, press Ctrl-R (command-R on macOS) to restart the Programmer app, and try programming again.
 
 ## Device-specific procedures
 
@@ -27,7 +27,7 @@ The following devices have specific programming requirements or procedures:
 
 To program a supported development kit, complete the following procedure:
 
-1. Open nRF Connect for Desktop and launch the {{app_name}}.
+1. Open nRF Connect for Desktop and launch the Programmer app.
 2. Connect a development kit to the computer with a USB cable and turn it on.
 3. Click **Select device** and choose the device from the drop-down list.</br>
    The button text changes to the name and serial number of the selected device, and the **Device Memory Layout** section indicates that the device is connected.
diff --git a/doc/docs/programming_nrf52840_dongle.md b/doc/docs/programming_nrf52840_dongle.md
@@ -2,7 +2,7 @@
 
 To program the nRF52840 Dongle, complete the following steps:
 
-1. Open nRF Connect for Desktop and launch the {{app_name}}.
+1. Open nRF Connect for Desktop and launch the Programmer app.
 2. Insert the nRF52840 Dongle into a USB port on the computer.<br/>
    The status light **LD2** turns on solid green, indicating that the dongle is powered up.
 3. Put the dongle into bootloader mode by pressing the **RESET** button.<br/>
@@ -15,7 +15,7 @@ To program the nRF52840 Dongle, complete the following steps:
          - This step is not needed if the currently running application uses the [DFU trigger library](https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/lib_dfu_trigger_usb.html), part of the nRF5 SDK v17.1.0.
          - If this is the first time the dongle is connected, a driver needed for the nRF52840 Nordic Secure DFU feature is also installed as part of this step.
 
-5. In the navigation bar in the {{app_name}}, click **Select device** and choose the serial number of the dongle from the drop-down list.
+5. In the navigation bar in the Programmer app, click **Select device** and choose the serial number of the dongle from the drop-down list.
 6. Drag and drop the HEX file into the **File Memory Layout** section. Alternatively, click **Add file** to add the files you want to program, using one of the following options:
 
     - Select the files you used recently.
@@ -24,4 +24,4 @@ To program the nRF52840 Dongle, complete the following steps:
 7. Select the firmware image file (with the extension HEX) from the file browser that opens up.
 8. Click **Write** to program the firmware onto the dongle.
 
-When the writing process completes, the device resets, and – unless the application uses the [DFU trigger library](https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/lib_dfu_trigger_usb.html) of the nRF5 SDK v17.1.0 – the dongle will no longer show up in the {{app_name}}, as it is no longer in the bootloader mode.
+When the writing process completes, the device resets, and – unless the application uses the [DFU trigger library](https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/lib_dfu_trigger_usb.html) of the nRF5 SDK v17.1.0 – the dongle will no longer show up in the Programmer app, as it is no longer in the bootloader mode.
diff --git a/doc/docs/programming_thingy.md b/doc/docs/programming_thingy.md
@@ -61,7 +61,7 @@ See the following sections for programming Nordic Thingy prototyping platforms u
           1. While holding **SW4** pressed, move the **SW1** power switch to **ON** to power the Thingy:91.<br/>
              The device turns on in the bootloader mode for the nRF52840 SoC.
 
-      1. Open nRF Connect for Desktop and launch the {{app_name}}.
+      1. Open nRF Connect for Desktop and launch the Programmer app.
       1. Click **Select device**.<br/>
 
           ![Programmer - Select device](./screenshots/programmer_click_select_device.png "Programmer - Select device")
@@ -108,7 +108,7 @@ See the following sections for programming Nordic Thingy prototyping platforms u
           1. While holding **SW3** pressed, move the **SW1** power switch to **ON** to power the Thingy:91.<br/>
              The device turns on in the bootloader mode for the nRF9160 SiP.
 
-      1. Open nRF Connect for Desktop and launch the {{app_name}} if it is not already open.
+      1. Open nRF Connect for Desktop and launch the Programmer app if it is not already open.
       1. Click **Select device**.<br/>
 
           ![Programmer - Select device](./screenshots/programmer_click_select_device.png "Programmer - Select device")
@@ -155,7 +155,7 @@ See the following sections for programming Nordic Thingy prototyping platforms u
         1. While holding **SW3** pressed, move the **SW1** power switch to **ON** to power the Thingy:91.<br/>
            The device turns on in the bootloader mode for the nRF9160 SiP.
 
-    1. Open nRF Connect for Desktop and launch the {{app_name}} if it is not already open.
+    1. Open nRF Connect for Desktop and launch the Programmer app if it is not already open.
     1. Click **Select device**.<br/>
 
         ![Programmer - Select device](./screenshots/programmer_click_select_device.png "Programmer - Select device")
@@ -203,7 +203,7 @@ To program Nordic Thingy using the USB connection, complete the following steps:
     1. While holding **SW2** pressed, move the **SW1** power switch to **ON** to power the Thingy:53.<br/>
        The device turns on in the bootloader mode.
 
-1. Open nRF Connect for Desktop and launch the {{app_name}} if it is not already open.
+1. Open nRF Connect for Desktop and launch the Programmer app if it is not already open.
 1. Click **Select device**.<br/>
 
     ![Programmer - Select device](./screenshots/programmer_click_select_device.png "Programmer - Select device")
@@ -253,7 +253,7 @@ Make sure you have the following hardware:
 
     To update the nRF52840 SoC firmware on the Thingy:91 using the nRF9160 DK as an external debug probe, complete the following steps:
 
-     1. Open nRF Connect for Desktop and launch the {{app_name}}.
+     1. Open nRF Connect for Desktop and launch the Programmer app.
      1. Prepare the hardware:
 
         a. Connect the Thingy:91 to the debug out port on a 10-pin external debug probe using a JTAG cable.
@@ -289,7 +289,7 @@ Make sure you have the following hardware:
         See the `CONTENTS.txt` file for information on which file you need.
      1. Select the `thingy91_nrf52_connectivity_bridge_*.hex` file and click **Open**.
      1. In the [**Device** section](overview.md#device), click **Erase & write**.<br/>
-        The update is complete when the animation in the {{app_name}}'s **Device memory layout** window ends.
+        The update is complete when the animation in the Programmer app's **Device memory layout** window ends.
      1. In the [**File** section](overview.md#file), click **Clear files**.
 
     You can now disconnect the external debug probe from Nordic Thingy:91, disconnect Nordic Thingy:91 from the computer, and put the cover back on.
@@ -298,7 +298,7 @@ Make sure you have the following hardware:
 
     To update the modem firmware on the Thingy:91 using an external debug probe, complete the following steps:
 
-     1. Open nRF Connect for Desktop and launch the {{app_name}}.
+     1. Open nRF Connect for Desktop and launch the Programmer app.
      1. Prepare the hardware:
 
         a. Connect the Thingy:91 to the debug out port on a 10-pin external debug probe using a JTAG cable.
@@ -354,7 +354,7 @@ Make sure you have the following hardware:
 
     To program the nRF9160 SiP application firmware on the Thingy:91 using an external debug probe, complete the following steps:
 
-     1. Open nRF Connect for Desktop and launch the {{app_name}}.
+     1. Open nRF Connect for Desktop and launch the Programmer app.
      1. Prepare the hardware:
 
         a. Connect the Thingy:91 to the debug out port on a 10-pin external debug probe using a JTAG cable.
@@ -386,7 +386,7 @@ Make sure you have the following hardware:
      1. Open the `img_app_bl` folder that contains the HEX files for updating using a debugger.
      1. Select the `thingy91_at_client_*.hex` file and click **Open**.
      1. In the [**Device** section](overview.md#device), click **Erase & write**.<br/>
-         The update is complete when the animation in the {{app_name}}'s **Device memory layout** window ends.
+         The update is complete when the animation in the Programmer app's **Device memory layout** window ends.
 
      1. In the [**File** section](overview.md#file), click **Clear files**.
 
@@ -396,7 +396,7 @@ Make sure you have the following hardware:
 
 To program Nordic Thingy:53 using an external debug probe, complete the following steps:
 
-1. Open nRF Connect for Desktop and launch the {{app_name}}.
+1. Open nRF Connect for Desktop and launch the Programmer app.
 1. Prepare the hardware:
 
     a. Open the connector cover on the side of Nordic Thingy:53.
@@ -422,7 +422,7 @@ To program Nordic Thingy:53 using an external debug probe, complete the followin
    You can identify the nRF5340 DK by its PCA number PCA10095 and its ID that is printed on the label sticker on the DK.
 
     !!! note "Note"
-        If the nRF5340 DK does not show up in the drop-down list, press Ctrl-R in Windows or command-R in macOS to restart the {{app_name}}.
+        If the nRF5340 DK does not show up in the drop-down list, press Ctrl-R in Windows or command-R in macOS to restart the Programmer app.
 
 1. In the [**File** section](overview.md#file), click **Add file** and select **Browse**.<br/>
    A file explorer window appears.
@@ -432,7 +432,7 @@ To program Nordic Thingy:53 using an external debug probe, complete the followin
 1. Select the corresponding HEX file to be used with the debug probe and click **Open**.<br/>
    The HEX file appears in the **File memory layout** section.
 1. In the [**Device** section](overview.md#device), click **Erase & write**.<br/>
-   The update is complete when the animation in the {{app_name}}'s **Device memory layout** window ends.
+   The update is complete when the animation in the Programmer app's **Device memory layout** window ends.
 1. In the [**File** section](overview.md#file), click **Clear files**.
 
 You can now disconnect the external debug probe from Nordic Thingy:53, disconnect Nordic Thingy:53 from the computer, and put the connector cover back on.
diff --git a/doc/docs/revision_history.md b/doc/docs/revision_history.md
diff --git a/doc/docs/troubleshooting.md b/doc/docs/troubleshooting.md
diff --git a/doc/mkdocs.yml b/doc/mkdocs.yml

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,3 @@`
`1`		`-# Installing the {{app_name}}`
	`1`	`+# Installing the Programmer app`
`2`	`2`
`3`	`3`	`For installation instructions, see [Installing nRF Connect for Desktop apps](https://docs.nordicsemi.com/bundle/nrf-connect-desktop/page/installing_apps.html) in the nRF Connect for Desktop documentation.`