diff --git a/docs/silabs/general/ARTIFACTS.md b/docs/silabs/general/ARTIFACTS.md
index ce7067c122f874..cbaaa636525367 100644
--- a/docs/silabs/general/ARTIFACTS.md
+++ b/docs/silabs/general/ARTIFACTS.md
@@ -24,7 +24,7 @@ used with a Raspberry Pi to allow the Raspberry Pi's Open Thread Border Router
 to access the Thread network. Radio Co-Processor (RCP) images are available in
 the Assets section of this page:
 
-https://github.com/SiliconLabs/matter/releases/tag/v0.1.0
+https://github.com/SiliconLabs/matter/releases/tag/v0.2.0
 
 <br>
 
@@ -34,28 +34,25 @@ The Matter Accessory Device Images are used to turn an EFR into a Matter device.
 These are pre-built binary images for the Matter Demo. Matter Accessory Device
 Images are located in the Assets section of this page:
 
-https://github.com/SiliconLabs/matter/releases/tag/v0.1.0
+https://github.com/SiliconLabs/matter/releases/tag/v0.2.0
 
 <br>
 
-<!--
-## Matter Chip Tool Android APK
-Matter Chip Tool .apk file is located here: http://silabs.com
+## Matter Bootloader Binaries
+
+If you are using the OTA functionality and especially if you are using an EFR32MG2x device you will need to flash a bootloader binary on your device along with the application image. Bootloader binaries for all of the Matter supported devices are available here:
+
+https://github.com/SiliconLabs/matter/releases/tag/v0.2.0
 
-<br>
--->
 
 ## RS9116 Firmware
 
 The RS9116 firmware is used to update the RS9116 - it can be found in the
 repository you have cloned, at the following relative path from the
-`/connectedhomeip` directory:
+`/matter` directory:
 
 > $ /third_party/silabs/wiseconnect-wifi-bt-sdk/firmware
 
-<!-- The RS9116 firmware is used to update the RS9116, and is located in GitHub here:
-
-https://github.com/SiliconLabs/wiseconnect-wifi-bt-sdk/tree/2.5.0/firmware -->
 
 <br>
 
diff --git a/docs/silabs/general/OTA_BOOTLOADER.md b/docs/silabs/general/OTA_BOOTLOADER.md
index 05936e29ea7cc1..c0b0d28be6d1bf 100644
--- a/docs/silabs/general/OTA_BOOTLOADER.md
+++ b/docs/silabs/general/OTA_BOOTLOADER.md
@@ -60,7 +60,7 @@ Build the GBL file for the update image and note its size
            451176 Jul 19 16:39 out/lighting-app/BRD4186A/chip-efr32-lighting-example.gbl
 
 
--   Flash the application image, bootloader (pre-built BRD4186C bootloader binary from https://github.com/SiliconLabs/sdk_support/tree/main/matter/efr32/bootloader_binaries), erase the flash.
+-   Flash the application image, bootloader (pre-built BRD4186C bootloader binary from the [Matter Artifacts page](./ARTIFACTS.md). Erase the flash.
 
 ![Erase Flash](./images/ApplicationUploadEraseFlash.png)
 
diff --git a/docs/silabs/general/OTA_SOFTWARE_UPDATE.md b/docs/silabs/general/OTA_SOFTWARE_UPDATE.md
index 6de026c4fda0cd..c33d16d96ebb56 100644
--- a/docs/silabs/general/OTA_SOFTWARE_UPDATE.md
+++ b/docs/silabs/general/OTA_SOFTWARE_UPDATE.md
@@ -23,9 +23,8 @@ is controlled by the `chip_enable_ota_requestor` compile flag.
     using the external flash select the "external SPI" bootloader type
     configured with a single slot of at least 1000 KB. For the bootloader using
     the internal flash see the Internal Storage Bootloader section below.
-    Pre-built binaries for some configurations are available here:
-    [bootloader_binaries](https://github.com/SiliconLabs/sdk_support/tree/main/matter/efr32/bootloader_binaries)
-
+    Pre-built binaries for some configurations are available on the [Matter Artifacts page](./ARTIFACTS.md).
+ 
 -   Using the commander tool, upload the bootloader to the device running the
     application.
 
diff --git a/docs/silabs/thread/THREAD_PREREQS.md b/docs/silabs/thread/THREAD_PREREQS.md
index 8c756339e180fb..88a0e0ed294772 100644
--- a/docs/silabs/thread/THREAD_PREREQS.md
+++ b/docs/silabs/thread/THREAD_PREREQS.md
@@ -19,6 +19,7 @@
     > Make sure Git is installed on the local machine that will be used to flash
     > the devices so that the necessary repositories can be cloned locally and
     > used as needed.
+1. If you are using an EFR32MG2x device you will require a bootloader to run the demo applications. When you flash your application image be sure to include a bootloader as well (if one is not already present). Bootloader images are provided on the [Matter Artifacts page](../general/ARTIFACTS.md).
 
 <br>
 
diff --git a/docs/silabs/wifi/WIFI_PREREQS.md b/docs/silabs/wifi/WIFI_PREREQS.md
index 2c85d4c412a4c0..de0182835a1a1e 100644
--- a/docs/silabs/wifi/WIFI_PREREQS.md
+++ b/docs/silabs/wifi/WIFI_PREREQS.md
@@ -64,6 +64,7 @@ follows:
 -   Raspberry Pi imager tool (optional): To flash an operating system or Raspberry Pi image on the SD card of the Raspberry Pi if you are using one to run the ChipTool.  Note: The ChipTool may also be compiled and run on a Linux machine or Mac. [Download](https://www.raspberrypi.com/software/)
 -   Upgrade firmware on RS9116 EVK:
     [Reference](http://draft-docs.suds.silabs.net/rs9116-wiseconnect/2.5/wifibt-wc-getting-started-with-pc/update-evk-firmware)
+- If you are using an EFR32MG2x device you will require a bootloader to run the demo applications. When you flash your application image be sure to include a bootloader as well (if one is not already present). Bootloader images are provided on the [Matter Artifacts page](../general/ARTIFACTS.md).
 
 <br>