update implementation details

proposals/suraj-sonawane.rst

@@ -161,6 +161,7 @@ The skeleton of the board YAML file is:
 
 **2. Write device tree:**
 The devicetree file describes your board hardware in the Devicetree Source (DTS) format.
+In general, board-name.dts should look like this:
 
 .. code-block:: dts
 
@@ -217,20 +218,28 @@ Zephyr uses the Kconfig language to configure software features. Your board need
 **4. Add Flash and debug support:**
 Zephyr supports Building, Flashing and Debugging via west extension commands.
 To add west flash and west debug support, we need to create a board.cmake file in board directory. This file’s job is to configure a “runner” for your board. (There’s nothing special you need to do to get west build support for board.)
-    
+West is “pluggable”: you can add your own commands to west without editing its source code. These are called west extension commands, or just “extensions” for short.
+
+- `Adding a West Extension <https://docs.zephyrproject.org/latest/develop/west/extensions.html#west-extensions>`_:
+
+1. Write the code implementing the command. 
+2. Add information about it to a west-commands.yml file.
+3. Make sure the west-commands.yml file is referenced in the west manifest.
+
+
 PART-2. Driver developement:
 ==================
-    **1. Board Files:**
-    Board files are the primary descriptor of the hardware in Zephyr.
+**1. Board Files:**
+Board files are the primary descriptor of the hardware in Zephyr.
 
-    **2. Device tree overlays:**
-    DeviceTree Overlays can be used by the Zephyr application to specify new hardware or re-assign existing hardware described elsewhere in the board files.
+**2. Device tree overlays:**
+DeviceTree Overlays can be used by the Zephyr application to specify new hardware or re-assign existing hardware described elsewhere in the board files.
 
-    **3. Devicetree bindings:**
-    A devicetree binding declares requirements on the contents of nodes, and provides semantic information about the contents of valid nodes. Zephyr devicetree bindings are YAML files in a custom format (Zephyr does not use the dt-schema tools used by the Linux kernel).
+**3. Devicetree bindings:**
+A devicetree binding declares requirements on the contents of nodes, and provides semantic information about the contents of valid nodes. Zephyr devicetree bindings are YAML files in a custom format (Zephyr does not use the dt-schema tools used by the Linux kernel).
 
-    **4. API Definations:**
-    Available under "include/drivers/". Provides a general way of unteracting with driver instances.
+**4. API Definations:**
+Available under "include/drivers/". Provides a general way of unteracting with driver instances.
 
 Software
 =========
@@ -315,11 +324,11 @@ Milestone #1, Introductory YouTube video (June 3rd)
 ===================================================
 - Introductory Video.
 - Add UART support for debug prints in the minimal firmware.
-- Work on the unmerged pull request from a previous year's Google Summer of Code contributor titled `"Add TI J721e R5 and BeagleBone AI64 R5 initial support #59191" <https://github.com/zephyrproject-rtos/zephyr/pull/59191>`_ in order to merge it.
+- Add `west flash support. <https://docs.zephyrproject.org/latest/develop/west/build-flash-debug.html>`_
 
 Milestone #2 (June 10th)
 ==========================
--  Add west flash support.
+-  Work on the unmerged pull request from a previous year's Google Summer of Code contributor titled `"Add TI J721e R5 and BeagleBone AI64 R5 initial support #59191" <https://github.com/zephyrproject-rtos/zephyr/pull/59191>`_ in order to merge it.
 -  Work on the unmerged pull request from a previous year's Google Summer of Code contributor titled `"Add TI J721e DM TIMER support #61020" <https://github.com/zephyrproject-rtos/zephyr/pull/61020>`_ in order to merge it.
 
 Milestone #3 (June 17th)