diff --git a/proposals/himanshuk.rst b/proposals/himanshuk.rst
index d8a7401a556b847ac068114c30f80496348cfcf4..47e6607e0609e9ecb3e31ce591b984e7a5bdd42c 100644
--- a/proposals/himanshuk.rst
+++ b/proposals/himanshuk.rst
@@ -108,7 +108,7 @@ How it will be possible, see an example for blink LEDs via device tree ovelay wh
 
 Implementation of device tree 
 
-.. image:: images_support/Device_tree.png
+.. image:: https://devicetree-specification.readthedocs.io/en/stable/_images/graphviz-58c8267ade85edeca7b1b0299af2b1e473987ddc.png
     :alt: Device tree Implementation
     :align: center
 
@@ -120,7 +120,7 @@ BeagleV-Fire also support the robotic cape with librobotcontrol package and cape
 but as BBB support the librobotcontrol with more functionality and flexible application, beagleV-fire is not capable for librobotcontrol package due to less number of device_tree fragment present in robotic-cape (.dts) file which is pre-installed in V-fire image.
 With help of customization for cape gateware in V-fire which Provide more flexibility to board with cape, librobotcontrol package will support V-fire with robotic cape.
 
-.. image:: images_support/BeaeglV-fire_gateware.png
+.. image:: https://docs.beagle.cc/latest/_images/Gateware-Flow-simplified-overview.png
     :alt: V-fire Gateware architecture
     :align: center