large files work both on ios and android

src/field/offline-use/index.md

@@ -34,7 +34,7 @@ In general, layers that do not work offline are:
 #### Offline background maps
 Online background maps have to be prepared for offline use by generating **vector or raster tiles**. Detailed steps on how to do it can be found in [Background Maps](../../gis/settingup_background_map/). 
 
-Vector and raster tiles can be packaged in the project. However, as these files can be rather large, it might be impractical to synchronise them trough <MainPlatformNameLink />. [How to work with very large files](../../gis/settingup_background_map/#how-to-work-with-very-large-files-android) will show you how to get them in your mobile device.
+Vector and raster tiles can be packaged in the project. However, as these files can be rather large, it might be impractical to synchronise them trough <MainPlatformNameLink />. [How to work with very large files](../../gis/settingup_background_map/#how-to-work-with-very-large-files) will show you how to get them in your mobile device.
 
 #### Offline PostGIS layers
 If you use online PostGIS layers in your <MainPlatformName /> project and need to do an offline survey in the field, we recommend using [DB Sync](../../dev/dbsync/). DB Sync helps synchronising your PostGIS database and GeoPackage layers that can be edited offline using <MobileAppName />.

src/gis/settingup_background_map/index.md

@@ -61,7 +61,7 @@ Make sure that you:
 - zoomed to your area of interest
 
 To generate an offline copy of the aerial imagery from your map view extent:
-1. In QGIS, select **Processing** > **Toolbox** from the main menu. The **Processing** panel will appear on the right side of QGIS window.
+1. In QGIS, select **Processing** > **Toolbox** from the main menu. The **Processing** panel will appear on the right side of the QGIS window.
 2. In the search section on the top of the **Processing** panel, type *xyz* to display relevant tools.
 3. In **Raster tools**, double-click on **Generate XYZ tiles (MBTiles)**
    ![QGIS generate XYZ tiles MBTiles](./qgis_xyz_gen_mbtiles1.jpg "QGIS generate XYZ tiles MBTiles")
@@ -76,7 +76,7 @@ To generate an offline copy of the aerial imagery from your map view extent:
    ![QGIS generate XYZ tiles MBTiles settings](./qgis_xyz_gen_mbtiles2.jpg "QGIS generate XYZ tiles MBTiles settings")
 
 :::warning
-Depending on the size of your study area and the zoom level, the output file can be very large. See how to [work with large files](#how-to-work-with-very-large-files-android) in <MobileAppName />.
+Depending on the size of your study area and the zoom level, the output file can be very large. See how to [work with large files](#how-to-work-with-very-large-files) in <MobileAppName />.
 :::
 
 ## Vector tiles
@@ -152,7 +152,7 @@ Vector tiles for offline use can be downloaded easily using <QGISPluginName />.
 
    ![QGIS download vector tiles dialog](./qgis-vector-tiles-set-extent.jpg "QGIS download vector tiles dialog")
 
-   MBTiles can be stored in your [<MainPlatformName /> project folder](../../manage/project/#mergin-maps-project-folder) and synchronised to <MainPlatformNameLink /> along with your project. If you find it impractical to synchronise them or if you want to use the same file in multiple projects, follow the steps on [How to work with large files](#how-to-work-with-very-large-files-android) in <MobileAppName />.
+   MBTiles can be stored in your [<MainPlatformName /> project folder](../../manage/project/#mergin-maps-project-folder) and synchronised to <MainPlatformNameLink /> along with your project. If you find it impractical to synchronise them or if you want to use the same file in multiple projects, follow the steps on [How to work with large files](#how-to-work-with-very-large-files) in <MobileAppName />.
 
 4. Click **Run**. After the vector tiles are generated and downloaded successfully, the MBTiles file will be added to the **Layers** panel. You may close the algorithm dialog window.
 
@@ -163,31 +163,26 @@ Before taking your offline tiles to the field, we recommend checking in <MobileA
 :::
 
 
-## How to work with very large files (Android)
-<Badge text="Android only" type="warning"/>
+## How to work with very large files
 
 Raster and vector tiles generated for offline use can be relatively large files, especially when using high resolution data or a large area of interest. It may be impractical to synchronise these large files through <MainPlatformNameLink /> or to have duplicate copies if they are used in multiple projects.
 
-:::tip
+:::tip 
 If you do not need to use your background maps offline, consider creating a WMS or WMTS server for online use.
 :::
 
-QGIS uses relative paths to load the data. If your <MainPlatformName /> project refers to files located in another folder, this project can be loaded just fine on another computer or in <MobileAppName /> - if the folder with the files can be found in its expected location.
+QGIS uses relative paths to load the data. If your <MainPlatformName /> project refers to files located in another folder, this project can be loaded just fine on another computer or in <MobileAppName /> - if the folder with the files can be found in its expected location. Note that multiple projects can refer to the same files.
 
 1. On your computer, create a folder that will contain the large datasets (here: `_rasters`). It should be located in the same directory as your <MainPlatformName /> projects.
    ![File folder storing large data](./bm-folder-large-files.jpg "File folder storing large data")
 2. Open your <MainPlatformName /> project in QGIS. Load the files from the `_rasters` folder to the project. Save and sync.
 
-3. Connect your mobile device to the computer and copy the `_rasters` folder to the app's project folder `Internal storage/Android/data/uk.co.lutraconsulting/files/projects`. 
-
-   See [Manual data transfer (Android)](../../manage/missing-data/#manual-data-transfer-android) for detailed steps.
+3. Connect your mobile device to the computer and copy the `_rasters` folder to the app's project folder
+   - on Android, follow the steps described in [Manual data transfer (Android)](../../manage/missing-data/#manual-data-transfer-android)
+   - on iOS, follow the steps described in [Manual data transfer (iOS)](../../manage/missing-data/#manual-data-transfer-ios)
 
-4. Use the project in <MobileAppName /> as usual. 
-
-:::tip
-Files from the folder can be loaded into multiple <MainPlatformName /> projects.
-:::
+4. Use the project in the <MobileAppNameShort /> as usual. 
 
-:::warning
-Files located in the another folder are not synchronised. This saves your storage on <ServerCloudNameLink />. However, if you want to update or modify these files, you have to connect the mobile device to your computer and do it manually.
+:::warning These files are not synchronised
+Files that are not located directly in the <MainPlatformName /> project folder are not synchronised. This saves your storage on <ServerCloudNameLink />. However, if you want to update or modify these files, you have to connect the mobile device to your computer and do it manually.
 :::

src/manage/project/index.md

@@ -91,5 +91,5 @@ It is best to store all survey layers and relevant datasets in the project's fol
 :::tip
 It is possible to use files that are stored in other folders in <MobileAppName />. However, these folders have to be [manually transferred](../missing-data/#manual-data-transfer-android).
 
-This can be useful when working with [very large datasets](../../gis/settingup_background_map/#how-to-work-with-very-large-files-android) such as large rasters or background maps.
+This can be useful when working with [very large datasets](../../gis/settingup_background_map/#how-to-work-with-very-large-files) such as large rasters or background maps.
 :::

src/manage/selective_sync/index.md

@@ -9,7 +9,7 @@ Selective sync feature adds a possibility to not download specified files on oth
 Selective sync is useful mainly when a project contains a lot of data (for example photos) and these data do not necessarily need to be stored on all devices. Another advantage is a significant reduction of synchronisation time.
 
 :::tip
-If you want to use large files (e.g. background maps) in your <MainPlatformName /> project without synchronisation, see [How to work with very large files](../../gis/settingup_background_map/#how-to-work-with-very-large-files-android).
+If you want to use large files (e.g. background maps) in your <MainPlatformName /> project without synchronisation, see [How to work with very large files](../../gis/settingup_background_map/#how-to-work-with-very-large-files).
 :::
 
 See the example in the picture below. Two surveyors Jim and Susan are capturing features in the field. When it comes to synchronisation, Jim hits the [arrow icon](../plugin/) to synchronise his changes. Features together with photos are now stored on the server. When Susan synchronises the project, synchronisation first downloads Jim's changes (including photos) and after that uploads Susan's changes to the server. However, selective sync can exclude photos from being downloaded.

src/migrate/qfield/index.md

@@ -119,7 +119,7 @@ In our blog <MainDomainNameLink id="blog/qfield-vs-mergin-maps" desc="QField vs.
 
 Here is a non-definitive list of other known differences:
 
-* QField mobile app can work without QFieldCloud (server) via USB transfer of the projects. This is not available in <MainPlatformName />, but you can [manually download](../../manage/missing-data/) your data or [upload large files](../../gis/settingup_background_map/#how-to-work-with-very-large-files-android) to your mobile device if needed.
+* QField mobile app can work without QFieldCloud (server) via USB transfer of the projects. This is not available in <MainPlatformName />, but you can [manually download](../../manage/missing-data/) your data or [upload large files](../../gis/settingup_background_map/#how-to-work-with-very-large-files) to your mobile device if needed.
 * *Organisation teams* in QFieldCloud do not have any equivalent concept in <MainPlatformName />. On <MainPlatformName /> can have different workspaces for different teams.
 * There is no concept of *secrets* in <MainPlatformName />. For `pg_service` configuration, you need to transfer it manually as described [here](../../gis/supported_formats/).
 * There is no concept of *managing ongoing jobs* or *triggers* in <MainPlatformName /> accessible for users. Users see the results when jobs are finished (e.g. map rendering).