samples: Fix invalid links

Fixes links that are invalid

Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>

samples/boards/stm32/ccm/README.rst

@@ -36,7 +36,7 @@ board's DTS file ``chosen`` section:
 
 For example the olimex STM32 E407 DTS file looks like this:
 
-.. literalinclude:: ../../../../boards/olimex/olimex_stm32_e407/olimex_stm32_e407.dts
+.. literalinclude:: ../../../../boards/olimex/stm32_e407/olimex_stm32_e407.dts
    :linenos:
 
 Building and Running

samples/drivers/led_ws2812/README.rst

@@ -69,7 +69,7 @@ To make sure the sample is set up properly for building, you must:
 For example devicetree configurations for each compatible, see
 :zephyr_file:`samples/drivers/led_ws2812/boards/thingy52_nrf52832.overlay`,
 :zephyr_file:`samples/drivers/led_ws2812/boards/nrf52dk_nrf52832.overlay` and
-:zephyr_file:`samples/drivers/led_ws2812/boards/nrf51dk_nrf51422.overlay`.
+:zephyr_file:`samples/drivers/led_ws2812/boards/nrf51dk_nrf51822.overlay`.
 
 Some boards are already supported out of the box; see the :file:`boards`
 directory for this sample for details.

samples/drivers/uart/native_tty/README.rst

@@ -12,7 +12,7 @@ UART to USB bridge dongles that are wired together, writing demo data to one
 dongle and reading it from the other."
 
 The source code for this sample application can be found at:
-:zephyr_file:`samples/drivers/uart/native-tty`.
+:zephyr_file:`samples/drivers/uart/native_tty`.
 
 You can learn more about the Native TTY UART driver in the
 :ref:`TTY UART <native_tty_uart>` section of the native_sim board

samples/shields/x_nucleo_iks01a2/standard/README.rst

@@ -22,8 +22,8 @@ stacked on a board with an Arduino connector. The board's I2C must be
 configured for the I2C Arduino connector in the devicetree. See for
 example the :ref:`nucleo_f401re_board` board source code:
 
-- :zephyr_file:`boards/arm/nucleo_f401re/nucleo_f401re.dts`
-- :zephyr_file:`boards/arm/nucleo_f401re/arduino_r3_connector.dtsi`
+- :zephyr_file:`boards/st/nucleo_f401re/nucleo_f401re.dts`
+- :zephyr_file:`boards/st/nucleo_f401re/arduino_r3_connector.dtsi`
 
 Please note that this sample can't be used with boards already supporting
 one of the sensors available on the shield (such as disco_l475_iot1) as zephyr

samples/shields/x_nucleo_iks02a1/microphone/README.rst

@@ -52,11 +52,11 @@ To build the sample you can use following command:
    building the sample is the I2S output clock frequency configuration. For example,
    for nucleo_f411re board, we have the following file that configures the I2SPLL and
    have a dependency on HSE/HSI:
-   :zephyr_file:`boards/shields/x_nucleo_iks02a1/boards/nucleo_f411re.defconfig`
+   :zephyr_file:`boards/shields/x_nucleo_iks02a1/boards/nucleo_f411re.overlay`
 
    The user is invited to to verify which osci is configured on the used host board
    defconfig file and calculate the final I2SClk frequency, e.g.
-   :zephyr_file:`boards/arm/nucleo_f411re/nucleo_f411re.dts`
+   :zephyr_file:`boards/st/nucleo_f411re/nucleo_f411re.dts`
 
 
 Sample Output

samples/shields/x_nucleo_iks02a1/sensorhub/README.rst

@@ -31,8 +31,8 @@ configured for the I2C Arduino connector (both for pin muxing
 and devicetree). See for example the :ref:`nucleo_f401re_board` board
 source code:
 
-- :zephyr_file:`boards/arm/nucleo_f401re/nucleo_f401re.dts`
-- :zephyr_file:`boards/arm/nucleo_f401re/pinmux.c`
+- :zephyr_file:`boards/st/nucleo_f401re/nucleo_f401re.dts`
+- :zephyr_file:`boards/st/nucleo_f401re/pinmux.c`
 
 Please note that this sample can't be used with boards already supporting
 one of the sensors available on the shield (such as disco_l475_iot1)