diff --git a/proposals/himanshuk.rst b/proposals/himanshuk.rst
index b5885d6fdae7eee1f43f9b985f99c4ca76d80445..f407acec56ac26e78be7b716adc3b1df9eac9494 100644
--- a/proposals/himanshuk.rst
+++ b/proposals/himanshuk.rst
@@ -58,7 +58,7 @@ BeaglBboneBlack support robotic-cape cape with librobotcontrol package due to cr
 as below is simple dts example for accesing GPIO's for blink LED's.
 since P9_12 supports the GPIO's functinoality as output signal. 
 
-.. code :: dts 
+.. code-block :: dts 
     /{
         compatible = "ti,BeaglBbone-Black";
         part-number = "DM-GPIO-TEST";
@@ -91,7 +91,7 @@ As in librobotcontrol there is no robotic cape dtb support for beaglebone-AI64 w
 
 How it will be possible, see an example for blink LEDs via device tree ovelay which is for GPIO's.
 
-.. code :: dts
+.. code-block :: dts
          &{/chosen} {
 	overlays {
 		BONE-LED_P8_03 = __TIMESTAMP__;
@@ -110,7 +110,7 @@ How it will be possible, see an example for blink LEDs via device tree ovelay wh
 
 Implementation of device tree :
 
-.. image :: ..image_support/Device_tree.png
+.. image :: https://devicetree-specification.readthedocs.io/en/stable/_images/graphviz-58c8267ade85edeca7b1b0299af2b1e473987ddc.png
     :alt: Device tree Implementation
     :align: center
 
@@ -124,7 +124,7 @@ With help of customization for cape gateware in V-fire which Provide more flexib
 
 V-fire Gateware architecture:
 
-.. image :: ..image_support/Beaglev-fire_gateware.png
+.. image :: https://docs.beagleboard.org/latest/_images/Gateware-Flow-simplified-overview.png
     :alt: V-fire Gateware architecture
     :align: center