diff --git a/docs/acquisition.md b/docs/acquisition.md
index 0e4fdb9..4f5b28e 100644
--- a/docs/acquisition.md
+++ b/docs/acquisition.md
@@ -53,6 +53,9 @@ The user should assemble the calibration structure in the middle of the capturin
 After calibrating the system, the user should synchronize the devices with the main workstation (see the [Synchronization](../synchronization) section).
 Additionally, it is a good practice to reset the `Exposure` and the `Color Gain` settings for all the devices, in order to get consistent results betweeen the devices.
 
+<a name="issue30"/>
+<a name="issue25"/>
+
 <p align="center">
      <img src="../../assets/images/data_acq/4xk4a_prep_n_rec.gif">
 </p>
@@ -63,6 +66,8 @@ It is also possible to connect and calibrate `K` devices, with `N >= 3`. Just fo
 
 <iframe width="560" height="315" src="https://www.youtube.com/embed/A7pOEdZ11nQ" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
+<a name="issue29"/>
+
 <!--
 <p align="center">
      <img src="../../assets/images/data_acq/3k4a_set1.gif">
@@ -107,4 +112,6 @@ These folders contain the corresponding data, with the `group_id`, `device_name`
 
 Here we show the **calibrated** merged views of **colored** `pointclouds`, as exported by `volsnap.exe`.
 
+<a name="issue33"/>
+
 <img src="../../assets/images/volsnap/colored_pcloud_result.png" width="900"/>
\ No newline at end of file
diff --git a/docs/configure.md b/docs/configure.md
index 27b29bf..ece00d2 100644
--- a/docs/configure.md
+++ b/docs/configure.md
@@ -58,6 +58,7 @@ Options:
   -p,--path TEXT=.                              Directory where to store device_repository.json" file.
   -c,--cam_type UINT                            0 for Microsoft Kinect 4 Azure, 1 for Intel RealSense 2.0 D415
 ```
+<a name="issue22"/>
 
 The supported functionalities are:
 * **Adding** a device to the repository.
@@ -72,6 +73,8 @@ In order to add a device to the repository, one just need to connect **a single*
 > **Note:** If `device_repository.json` does not exist in the path specified (defaulted to the `./Resources` directory), it with create one in the `./Resources` directory. 
 If device_name already exists, the error with be logged to the console.
 
+<a name="issue21"/>
+
 * **Renaming** a device in the repository.
 In order to change the name of the device simply execute: