Apply restyled updates

docs/guides/ti/matter-syscfg/sysconfig-board.md

@@ -2,29 +2,28 @@
 
 ## Table of Contents
 
-* [Reserve Peripherals](#Reserve-Peripherals)
-* [Hardware View](#Hardware-View)
+-   [Reserve Peripherals](#Reserve-Peripherals)
+-   [Hardware View](#Hardware-View)
 
 The board view shows you what pins are available on your board, and what
-peripherals are assigned to what pins. Hover over each pin for more
-information.
+peripherals are assigned to what pins. Hover over each pin for more information.
 
 <div style="text-align: center;">
   <img src="./images/board_view.png" width=20%>
 </div>
 
-Enabled and configured peripherals are displayed with green symbols.
-To add a new peripheral, press the plus sign next to the peripheral
-type. The \"Show generated files\" tab lets you see the files generated
-based on SysConfig. Generated files are dynamically updated every time
-you make a change in SysConfig. When you build your project, the
-generated files are exported into the output folder of your project.
+Enabled and configured peripherals are displayed with green symbols. To add a
+new peripheral, press the plus sign next to the peripheral type. The \"Show
+generated files\" tab lets you see the files generated based on SysConfig.
+Generated files are dynamically updated every time you make a change in
+SysConfig. When you build your project, the generated files are exported into
+the output folder of your project.
 
 <div style="text-align: center;">
   <img src="images/show_generated_files_tab.png">
 </div>
 
-## Reserve Peripherals 
+## Reserve Peripherals
 
 Certain use cases may require preventing SysConfig from generating the
 configuration of specific peripherals.
@@ -34,8 +33,8 @@ Examples of use cases requiring to reserve peripherals are:
 -   dynamic re-configuration of a peripheral
 -   leveraging the Sensor Controller (on devices enabling it)
 -   already handling certain peripherals configuration
--   with hardware constraints preventing to use certain peripherals
-    (typically GPIOs)
+-   with hardware constraints preventing to use certain peripherals (typically
+    `GPIOs`)
 -   peripherals reserved for future use
 
 Below are the steps required to utilize the Reserve Peripherals feature.
@@ -45,31 +44,31 @@ Below are the steps required to utilize the Reserve Peripherals feature.
 2.  Open the panel \"Reserve Peripherals\"
 
     <div style="text-align: center;">
-      <img src="images/syscfg-reserve-peripheral-pannel.png" width=30%>
+      <img src="images/syscfg-reserve-peripheral-panel.png" width=30%>
     </div>
 
 3.  Reserve the resources
 
-    Reserve a peripheral using SysConfig. This image shows how
-    to reserve DIO 15
+    Reserve a peripheral using SysConfig. This image shows how to reserve `DIO`
+    15
 
     <div style="text-align: center;">
       <img src="images/syscfg-reserve-gpio.png" width=30%>
     </div>
 
-
-SysConfig ensures no resource conflict occurs. In case no solution can
-be found, an error is raised.
+SysConfig ensures no resource conflict occurs. In case no solution can be found,
+an error is raised.
 
 ## Hardware View
 
-The Hardware view may be used to add software modules for supporting
-hardware resources on EVMs or LaunchPads. The same capability could be
-done in the Software view by adding a Hardware. However the Hardware
-view provides a hardware-first perspective to show which software could
-be used with hardware resources.
+The Hardware view may be used to add software modules for supporting hardware
+resources on EVMs or LaunchPads. The same capability could be done in the
+Software view by adding a Hardware. However the Hardware view provides a
+hardware-first perspective to show which software could be used with hardware
+resources.
 
 Sysconfig Hardware View:
+
 <div style="text-align: center;">
   <img src="images/syscfg_hardware_view.png" width=30%>
-</div>
+</div>