diff --git a/proposals/himanshuk.rst b/proposals/himanshuk.rst
index e7fb36a99efde4fea069b5ddd31655dd846c56d2..edbf0b9817ee57da8a4949c534b9310b64692926 100644
--- a/proposals/himanshuk.rst
+++ b/proposals/himanshuk.rst
@@ -106,7 +106,7 @@ How it will be possible, see an example for blink LEDs via device tree ovelay wh
 
 Implementation of device tree 
 
-.. image:: https://devicetree-specification.readthedocs.io/en/stable/_images/graphviz-58c8267ade85edeca7b1b0299af2b1e473987ddc.png
+.. image::https://devicetree-specification.readthedocs.io/en/stable/_images/graphviz-58c8267ade85edeca7b1b0299af2b1e473987ddc.png
     :alt: Device tree Implementation
     :align: centre
 
@@ -119,7 +119,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:: https://devicetree-specification.readthedocs.io/en/stable/_images/graphviz-58c8267ade85edeca7b1b0299af2b1e473987ddc.png
+.. image::https://devicetree-specification.readthedocs.io/en/stable/_images/graphviz-58c8267ade85edeca7b1b0299af2b1e473987ddc.png
     :alt: V-fire Gateware architecture
     :align: centre