Fixing dead links

Author: beanzmo

documentation/get-started/tutorials/advanced-setup-qfc.en.md

@@ -69,7 +69,7 @@ There are two possible ways, in which the access to the database can be saved an
 1. **Direct Connection:** When connecting to a PostGIS database, you can store all information including the credentials inside the QGIS Project directly.
 2. **Using a PG Service File:** Using a service file that can be saved as a "secret" in QFieldCloud.
 We highly recommend to make use of this option due to data safety.
-Read more on PG Service and Secrets [here](../how-to/pg-service.en.md)<!-- markdown-link-check-disable-line -->
+Read more on PG Service and Secrets [here](../../how-to/project-setup/pg-service.md)
 
 !!! Workflow
 

documentation/how-to/navigation-and-positioning/gnss.en.md

@@ -142,24 +142,24 @@ The formats currently supported are:
 
     :material-tablet: Fieldwork
 
-    1. Copy the `chgeo2004_htrans_LV95.gtx` file to the directory **[App Directory](../get-started/storage.md#5-qfield-app-directory)/QField/proj** on your mobile device.
+    1. Copy the `chgeo2004_htrans_LV95.gtx` file to the directory **[App Directory](../../how-to/project-setup/storage.md#5-qfield-app-directory)/QField/proj** on your mobile device.
 
     2. Open the Site Dashboard
     3. Tap on the three-dots and direct to *Settings* > *Positioning*
 
-        !![](../assets/images/vertical_grid_selection_in_qfield_settings.png,450px)
+        !![](../../assets/images/vertical_grid_selection_in_qfield_settings.png,450px)
 
     4. Enable your GNSS device.
     It will directly center to your current location once the **positioning information** is available.
 
     5. Change to ***edit mode*** and press on the target button - the cross in the center means it is using GNSS positioning.
 
-        !![](../assets/images/gnss_use.webp,250px)
+        !![](../../assets/images/gnss_use.webp,250px)
 
         A long press on the **GNSS button** will show the **positioning menu**.
         Inside the menu you can turn on the **Show position information** which will show the current coordinates that are reprojected into the CRS of your project along with the precision information.
 
-     !![](../assets/images/positioning-menu.png)
+     !![](../../assets/images/positioning-menu.png)
 
     !!! note
         If you see WGS 84 lat/lon information instead of information in your project CRS, you probably have no signal yet.
@@ -214,10 +214,10 @@ It enables you to keep track of the meta data for each vertex like [GNSS quality
 !!! Workflow
 
     1. Add a point layer to the project and attributes configured to store this information.
-        !![](../assets/images/vertex_log1.png)
+        !![](../../assets/images/vertex_log1.png)
     2. Assign the role *digitizing logger* to a point layer.
     3. Go to > *Project* > *Properties...* > *QField*.
-        !![](../assets/images/vertex_log2.png)
+        !![](../../assets/images/vertex_log2.png)
     4. Set default values to the attributes using the positioning variables mentioned above.
 
 ## Using an external GNSS Receiver

documentation/how-to/navigation-and-positioning/tracking.en.md

@@ -47,15 +47,15 @@ If the layer linked to a tracking session supports the M dimension, QField will
     1. Open the Side Dashboard and long-press on the layer which you want to use for tracking.
     2. Tap **Setup tracking** and a new window will appear showing the configuration settings.
 
-        !![](../assets/images/tracking-layer-properties.png,350px)
+        !![](../../assets/images/tracking-layer-properties.png,350px)
 
     3. Tap the **Start tracking** button to begin the tracking.
     4. Enter the attributes for the feature(s) about to be created.
     5. Once finished open the Side Dashboard and long-press on the layer's tracking badge you want to stop.
     6. Tap **Stop tracking** to finish the.
 
 
-    !![](../assets/images/tracking-stop.png)
+    !![](../../assets/images/tracking-stop.png)
 
 
 ## Resume to a Previous Session

documentation/how-to/project-setup/attributes-form.en.md

@@ -275,7 +275,7 @@ This is useful when certain attributes are only required under certain condition
 
     In QField it will look like in the video below.
 
-    !![](../assets/images/conditional_visibility.webp,300px)
+    !![](../../assets/images/conditional_visibility.webp,300px)
 
 
 ## Define Constraints

documentation/how-to/relation-reference-widget.en.md

@@ -48,7 +48,7 @@ Therefore, they must be unique.
     6. (Optional) If you want to filter your children further, you can use additional "expressions".
     7. Once finished click "ok"
 
-    !![](../assets/images/relation_editor_widget_list.png, 400px)
+    !![](..assets/images/relation_editor_widget_list.png, 400px)
 
     **Attribute Form Configuration - Referencing Layer**
 
@@ -71,9 +71,9 @@ It is possible to limit the number of available children for your related layer
     1. Direct to Vector Layer *Properties...* > *QField*.
     2. Under "Relationship Settings" set the "Maximum number of items visible".
 
-    !![Maximum items visible for relation](../../assets/images/setting-maximum-items-visible-in-relation.png)
+    !![Maximum items visible for relation](../assets/images/setting-maximum-items-visible-in-relation.png)
 
-    !![QField Visible items](../../assets/images/maximum-items-visible-in-relation.png,300px)
+    !![QField Visible items](../assets/images/maximum-items-visible-in-relation.png,300px)
 
 ## Many-To-Many relations