note about input management in run.sh

docs/source/technical_tutorials/dps_tutorial/dps_tutorial_demo.ipynb

@@ -152,7 +152,7 @@
     "- `build-env.sh`: (Generically: the **build script**) is a shell script that is executed before the algorithm is run; it is used to set up any custom programming libraries used in the algorithm (i.e., a custom conda environment)\n",
     "- `environment.yml`: a configuration file used by conda to add any custom libraries; this is used by your build script (build-env.sh)\n",
     "- `gdal_wrapper.py`: a python script that contains the logic of the algorithm\n",
-    "- `run_gdal.sh`: (Generically: the **run script**) a shell script that DPS will execute when a run is requested. It calls any relevant python files with the required inputs. The run script is necessary to run your build script (to set up the runtime environment) and to execute your underlying alogorithm script(s)\n",
+    "- `run_gdal.sh`: (Generically: the **run script**) a shell script that DPS will execute when a run is requested. It calls any relevant python files with the required inputs. The run script is necessary to run your build script (to set up the runtime environment) and to execute your underlying alogorithm script(s). This is where you need to handle the input-file management—-for example passing one file at a time or a set of files at once.\n",
     "\n",
     "![DPS Tutorial Git repository overview](_static/dps_tutorial_git_repo.png)\n"
    ]