Merge pull request #42 from amichai-bd/roman_branch

edditing build_gui and extention *.md

Author: amichai-bd

docs/TFM/projectTool/extensions.md

@@ -133,3 +133,33 @@ This is a code example of `*.json` file, feel free to play with it
 Documentation and example can be found [click here](https://github.com/wavedrom/wavedrom)  
 https://wavedrom.com/tutorial.html  
 <u> extension id </u>: bmpenuelas.waveform-render 
+
+### Git History
+The "Git History" extension for Visual Studio Code is a powerful tool that enhances your Git version control experience within the VSCode environment. This extension provides a seamless way to explore the commit history of your Git-managed files and repositories directly from the code editor.
+
+Key features and functions of the "Git History" extension include:
+
+**File History Viewer:** It allows you to view the history of a specific file, providing a timeline of commits and changes made to that file over time.
+
+**Commit Details:** You can access detailed information about each commit, such as commit messages, authors, timestamps, and the changes made in that commit.
+
+**Comparison:** It enables you to compare different versions of a file, making it easy to see what was added, modified, or removed between commits.
+
+**Search and Filtering:** It provides search and filtering capabilities, allowing you to locate specific commits, authors, or messages within the commit history.
+
+and many more...   
+
+Overall, the "Git History" extension simplifies the process of tracking changes and understanding the history of your codebase, making it an essential tool for developers who rely on Git for version control in their VSCode workflow.
+
+***How to use it?***
+
+suppose you want to see the history of a specific file. 
+1. Open the file you want to see its history.
+2. Press `ctrl+shift+p` and type `Git: View File History` and press enter. Or right click on the file and choose `Git: View File History`.
+
+<u> extension id </u>: donjayamanne.githistory
+
+
+
+
+

docs/build_script/advanced build options.md renamed to docs/build_script/advanced_build_options.md

@@ -1,3 +1,4 @@
+# advanced build options
 If you examine the commands executed in the background during this stage, you will notice various parameters being defined, such as memory length, the crt0.s file, and more. You have the option to modify some of these parameters by using the `-cfg`` flag and providing a configuration.json file.
 In case you don't provide a configuration.json file, the default configuration.json file will be used.
 

docs/build_script/build_gui.md

@@ -17,7 +17,6 @@ Lets assume we want to run the following command:
  all you need to do is to select the relevant options as shown in the figure and click on the `Run Command` button.   
 
 ![gui_build2.png](/snapshots/gui_build2.png)
-
 If you wish to see the commands that runs on the terminal, you can choose the `-cmd` box and than `Run Command`.
 
 

sidebars.js

@@ -131,7 +131,7 @@ MAFIA_Build: [
     },
     {
       type: 'doc',
-      id: 'build_script/advanced build options',
+      id: 'build_script/advanced_build_options',
       label: 'advanced build options',
     },
     {