From b51a4faca2f7180f3353417a52fe004f2a301f5d Mon Sep 17 00:00:00 2001
From: Himanshu kohale <hkohale22@gmail.com>
Date: Sun, 31 Mar 2024 20:09:23 -0400
Subject: [PATCH] proposal changes, fix description, timeline

---
 proposals/himanshuk.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/proposals/himanshuk.rst b/proposals/himanshuk.rst
index e7fb36a..edbf0b9 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
 
-- 
GitLab