Update docs/Users_Guide/data_io.rst

Co-authored-by: Dan Adriaansen <[email protected]>

docs/Users_Guide/data_io.rst

@@ -31,7 +31,7 @@ Several MET tools read multiple gridded input data files in a single run. For ex
 
 ASCII file lists consist of a white-space separated list of paths to the input files. While relative paths may work, users are encouraged to provide full paths for more consistent behavior. Note that environment variables can also be used in the file lists.
 
-The file list elements can be separated by spaces, tabs, or newlines, but not commas. Users are encouraged to add the optional **file_list** keyword as the first element of each list to clearly identify it as such. When **file_list** is the first item, no validation logic is applied to the file names. When **file_list** is not present, MET checks whether each input file actually exists on the file system and errors out if it encounters too many missing input files.
+The file list elements can be separated by spaces, tabs, or newlines, but not commas. Users are encouraged to add the optional **file_list** keyword as the first element of each list to clearly identify it as such. When **file_list** is the first item, no validation of the file existence is performed. When **file_list** is not present, MET checks whether each input file actually exists on the file system and errors out if it encounters too many missing input files.
 
 While this validation logic is useful for standard input file formats, it can cause problems when providing a list of arguments for a Python embedding script since those arguments may not actually be the names of files on the file system. Please see the description of :ref:`MET_PYTHON_INPUT_ARG <met-python-input-arg>` for additional details.