relations tip

Author: alex-cit

src/layer/relations/index.md

@@ -1,13 +1,14 @@
 # Relationships
 
+
+It is often the case that you have a set of spatial features and you want to record their status every now and then. For example, there is a GIS layer representing the manholes and the surveyors carry out regular inspections of the manholes using <MainPlatformNameLink />. Instead of duplicating the manhole layer and recording each inspection as a new feature, inspections can be recorded in a non-spatial table that is linked to the spatial layer. This way, multiple records can be linked to one feature.
+
 :::tip Example project available
 You can clone these projects to take a closer look at 1-N relations:
 - Adding multiple **records** to a single feature: <MerginMapsProject id="documentation/forms_one-to-many-relations" />
 - Adding multiple **photos** to a single feature: <MerginMapsProject id="documentation/forms_multiple_photos" />
 :::
 
-It is often the case that you have a set of spatial features and you want to record their status every now and then. For example, there is a GIS layer representing the manholes and the surveyors carry out regular inspections of the manholes using <MainPlatformNameLink />. Instead of duplicating the manhole layer and recording each inspection as a new feature, inspections can be recorded in a non-spatial table that is linked to the spatial layer. This way, multiple records can be linked to one feature.
-
 The image below shows the manhole locations and a form with listed inspections in <MobileAppName />.
 
 ![Multiple inspections linked to one point in Mergin Maps mobile app](./mobile-1-n-relation.jpg "Multiple inspections linked to one point in Mergin Maps mobile app")