minor fixes

Author: alex-cit

src/.vitepress/sidebar/.en.js.kate-swp

@@ -92,7 +92,7 @@ export default {
         items: [
 	       { text: 'How to Open a File', link: '/layer/open-file/' },
 	       { text: 'How to Use Hyperlinks', link: '/layer/external-link/' },
-           { text: 'How to Open a Link to a Navigation App ', link: '/layer/link-to-navigation/' },
+           { text: 'How to Open a Link to a Navigation App', link: '/layer/link-to-navigation/' },
            { text: 'How to Link Multiple Records to One Feature (1-N Relations)', link: '/layer/one-to-n-relations/' },
            { text: 'How to Embed an Image', link: '/layer/embed-image/' },
         ] },

src/.vitepress/sidebar/en.js

@@ -39,7 +39,7 @@ You might want to use the checkbox with custom values, such as Yes/No or On/Off.
 
 ![QGIS checkbox field form](./qgis-form-checkbox-string.jpg "QGIS checkbox field form")
 
-Similarly, you could set up checkbox for fields with integer data types and use numerical values, e.g. `0` and `1`, for the *Checked* and for the *Unchecked* state. 
+Similarly, you could set up the checkbox widget for fields with integer data types and use numerical values, e.g. `0` and `1`, for the *Checked* and for the *Unchecked* state. 
 
 In the <MobileAppNameShort />, the checkbox can be easily toggled on/off.
 

src/layer/checkbox/index.md

@@ -11,7 +11,7 @@ You can explore this functionality in <MerginMapsProject id="documentation/form_
 
 Here we will use a line layer named `roads and paths`. It is designed for surveying both roads and paths and most of the fields are relevant for every type of feature in this layer. However, there are some attributes that are specific for roads (e.g. the number of lanes) or for paths (e.g. the visibility of the path). 
 
-The form uses the value of the `type` field to display the relevant set of attributes. The `type` field is set up as [value map](../value-select/#value-map) with defined values `road` and `path`.
+The form uses the value of the `type` field to display the relevant set of attributes. The `type` field is set up as a [value map](../value-select/#value-map) with defined values `road` and `path`.
 
 ![QGIS form value map](./qgis-form-value-map-roads.jpg "QGIS form value map")
 

src/layer/conditional-visibility/index.md

@@ -28,7 +28,7 @@ There are some commonly used default values that can be useful in your field sur
 
 - It is convenient to know when a feature was created and when it was last updated. Use fields with **Date** or **Date&Time** data types with the `now()` function to record this information. You can change the formatting using the [Date/Time](../date-time/) widget.
 
-- The name of the <MainPlatformName /> user who created or modified the feature can be recorded using the `@mergin_username` variable. These fields should use **Text (string)** data type. 
+- The name of the <MainPlatformName /> user who created or modified the feature can be recorded using the `@mm_username` variable. These fields should use **Text (string)** data type. 
   There are also other [project and user variables](../variables/#project-and-user-variables) related to your <MainPlatformName /> account or service that can be used as default values.
 
 - The coordinates of a point feature can be recorded as well using the `$x` and `$y` function in QGIS. To record the coordinate accurately, these fields should have the **Decimal number (real)** data type.  If the coordinates are in metres, values can be rounded to, say, 2-3 decimal places. When working with geographic coordinates that use degrees, you may want to round the coordinates to 8 decimal places. Use the *apply default value on update* option so that you have correct values when the position of the point feature changes.
@@ -44,8 +44,8 @@ Here are some examples:
 | `uuid()`          | `{9d0150eb-a36f-40f1-a768-540db8a36f7c}`                      | **no**  | Generates <QGISHelp ver="latest" link="user_manual/expressions/functions_list.html#uuid" text="UUID" /> (Universally Unique Identifier).|
 | `@now`          | `2024-06-30 10:00:00`                      | **no**  | The timestamp of when the feature was created. |
 | `@now`          | `2024-06-30 10:30:00`                     | **yes**  | The timestamp of when the feature was last **updated**. |
-| `@mergin_username`          | `sarah`                      | **no**  | Name of the user who created this feature.|
-| `@mergin_username`          | `jack`                      | **yes**  | Name of the user who **updated** this feature last.|
+| `@mm_username`          | `sarah`                      | **no**  | Name of the user who created this feature.|
+| `@mm_username`          | `jack`                      | **yes**  | Name of the user who **updated** this feature last.|
 | `round($x,2)`          | `1898789.92`                      | **yes**  | The X coordinate of a point feature, rounded to 2 decimal places.|
 | `$length`          | `123.45`                      | **yes**  | The length of a line feature.|
 | `$area`          | `1234.56`                      | **yes**  | The area of a polygon feature.|
@@ -55,14 +55,14 @@ Here are some examples:
 Let's set up an attributes to record the <MainPlatformName /> username of the surveyor who *created* a feature:
 1. Right-click on a layer, select **Properties** and go to the **Attributes form** tab.
 2. In the list of **Available Widgets** select the text field you want to use (here: `inserted_by`)
-3. In the **Defaults** tab, define the **Default value** as `@mergin_username`. 
+3. In the **Defaults** tab, define the **Default value** as `@mm_username`. 
    Do not check the **Apply default value on update** option :white_large_square:.
 
 ![QGIS attributes form Mergin Maps username default value](./qgis-form-default-inserted-by.jpg "QGIS attributes form Mergin Maps username default value")
 
 To save the <MainPlatformName /> username of the surveyor who *modified* this feature, the steps are similar:
 1. In the list of **Available Widgets** select the text field you want to use (here: `updated_by`)
-2. In the **Defaults** tab, define the **Default value** as `@mergin_username`. 
+2. In the **Defaults** tab, define the **Default value** as `@mm_username`. 
    Check the **Apply default value on update** option :heavy_check_mark:. The field will be updated anytime the feature is modified, saving the name of the surveyor who made the changes.
 
 ![QGIS attributes form Mergin Maps username default value](./qgis-form-default-updated-by.jpg "QGIS attributes form Mergin Maps username default value")

src/layer/default-values/index.md

@@ -7,15 +7,13 @@ description: HTML and Text widgets are not connected to a specific field of the
 
 <QGISHelp ver="latest" link="/user_manual/working_with_vector/vector_properties.html#other-widgets" text="QGIS" /> also offers widgets that can be added to the form to display values or text, but are not connected to a specific field of the layer, such as the Text or HTML widget. These widgets are also supported by <MainPlatformName />. 
 
-HTML and Text widgets can be used, e.g., to [display instructions](../display-instructions/) in the form. The HTML widget supports various [HTML tags](https://doc.qt.io/qt-6/richtext-html-subset.html#supported-tags), so it can also be used, for instance, to display [online images](../embed-image/) or [open local files](../open-file/).
+HTML and Text widgets can be used, e.g., to [display instructions](../display-instructions/) in the form. They can include [expressions and field values](#using-expressions-in-text-and-html-widgets) as well. The HTML widget supports various [HTML tags](https://doc.qt.io/qt-6/richtext-html-subset.html#supported-tags), so it can also be used, for instance, to display [online images](../embed-image/) or [open local files](../open-file/).
 
 |<div style="width:150px"> Widget </div> |Preview in the <MobileAppNameShort />|
 |:---:|:---:|
 Text | ![Mergin Maps mobile app Text widget in attributes form](./mobile-text-widget-preview.webp "Mergin Maps mobile app Text widget in attributes form")  |
 HTML Widget | ![Mergin Maps mobile app HTML widget in attributes form](../form-widgets/mobile-form-info-widgets.webp "Mergin Maps mobile app HTML widget in attributes form")  |
 
-The **Text** and **HTML widgets** provide an option to display instructions or tips for surveyors in your attributes forms. They can include [expressions and field values](#using-expressions-in-text-and-html-widgets) as well. 
-
 These widgets can be found in **Available Widgets** in the **Other Widgets** section when using the [Drag and Drop Designer](../form-layout/#qgis-drag-and-drop-designer). Simply add them to the form layout and double click to configure them as needed.
 
 ![QGIS HTML and Text Widget](./qgis-form-html-text-widget.jpg "QGIS HTML and Text Widget")

src/layer/info-widgets/index.md

@@ -4,7 +4,7 @@ description: A field in the form can be set up for QR code scanning. Scan QR cod
 
 # QR code
 
-You can scan QR codes with your mobile device to fill in a field in the form. The field data type should match the desired input, so if you want to scan say a link, you need a field with `Text (string)` data type.
+You can scan QR codes with your mobile device to fill in a field in the form. The field data type should match the desired input: if you want to scan, say, a link, you need a field with `Text (string)` data type.
 
 |<div style="width:150px"> Widget </div> |Preview in the <MobileAppNameShort />|
 |:---:|:---:|

src/layer/qr-code/index.md

@@ -6,4 +6,9 @@ description: Our step-by-step guides provide detailed descriptions accompanied b
 
 Here you can find some common use cases that can help you deal with specific scenarios. 
 
-Our step-by-step guides provide detailed descriptions accompanied by public <MainPlatformNameLink /> projects you can clone and explore in more detail.
+Our step-by-step guides provide detailed descriptions accompanied by public <MainPlatformNameLink /> projects you can clone and explore in more detail:
+- [How to Open a File](../open-file/) from within the form using the HTML widget or default values
+- [How to Use Hyperlinks](../external-link/) in the form
+- [How to Open a Link to a Navigation App](../link-to-navigation/) from within the form
+- [How to Link Multiple Records to One Feature](../one-to-n-relations/)
+- [How to Embed an Image](../embed-image/) in the form

src/layer/use-cases/index.md

@@ -50,7 +50,7 @@ Following variables are supported:
  - `@position_magnetic_variation` - The angle between the horizontal component of the magnetic field and true north, in degrees. Also known as magnetic declination. A positive value indicates a clockwise direction from true north and a negative value indicates a counter-clockwise direction.
  - `@position_horizontal_accuracy` - The accuracy of the provided latitude-longitude value, in meters.
  - `@position_vertical_accuracy` - The accuracy of the provided altitude value, in meters.
- - `@position_from_gps` - True, if recorder/edited feature's geometry correspond with current user's position (Position marker has the same location as the crosshairs marker).
+ - `@position_from_gps` - True, if recorded/edited feature's geometry corresponds with current user's position (Position marker has the same location as the crosshairs marker).
  - `@position_satellites_visible` - Number of visible satellites.
  - `@position_satellites_used` - Number of satellites used to calculate the position.
  - `@position_gps_fix` - GPS fix, e.g. "RTK float"