Overview/Tutorial-1:-Get-started-with-verify_pin-analysis.md

@@ -262,7 +262,7 @@ Here, Lazart produces several results tables:
 
 All results are stored inside the analysis folder, named `results` (specified in the `path` field in `read_or_make`). 
 
-**Lazart** will generate an _analysis report_ in the analysis folder. You can find the report of this analysis [here](https://gricad-gitlab.univ-grenoble-alpes.fr/lazart/lazart/-/raw/master/use-cases/examples/get-started/results/report.md).
+**Lazart** will generate an _analysis report_ in the analysis folder. You can find the report of this analysis [here](https://gricad-gitlab.univ-grenoble-alpes.fr/securitytools/lazart/-/raw/master/use-cases/examples/get-started/results/report.md).
 
 The complete results CSV file can be found inside the `res.csv` file in the analysis folder, the `results` binary file contains the `Metric` object for the Analysis. The analysis folder structure is presented [here](Analysis#analysis-folder-structure).
 
@@ -272,7 +272,7 @@ You have done your first analysis with **Lazart**. [Tutorial 2: Symbolic Inputs,
 
 For more information about analysis scripts and Lazart tools and environment, see [this section](Environment).
 
-The **[Python API](/lazart/lazart/-/wikis/Core/Analysis)** contains features for manipulating *analysis*, *traces*, *attacks*, *faults* etc. You can write much more complex scripts and your own analysis.
+The **[Python API](/securitytools/lazart/-/wikis/Core/Analysis)** contains features for manipulating *analysis*, *traces*, *attacks*, *faults* etc. You can write much more complex scripts and your own analysis.
 
 If you want to contribute to this project, please consult the **[corresponding guide](Development-Resources)**.