Add detail on *.result file

Author: Phil-Jensen

articles/azure-netapp-files/azacsnap-troubleshoot.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: troubleshooting
-ms.date: 08/05/2022
+ms.date: 01/16/2023
 ms.author: phjensen
 ms.custom: kr2b-contr-experiment
 ---
@@ -37,7 +37,7 @@ This naming convention allows for multiple configuration files, one per database
 
 ### Result files and syslog
 
-For the `-c backup` command, AzAcSnap writes to a *\*.result* file and to the system log, `/var/log/messages`, by using the `logger` command. The *\*.result* filename has the same base name as the log file, and goes into the same location. The *\*.result* file is a simple one line output file, such as the following example:
+For the `-c backup` command, AzAcSnap writes to a *\*.result* file.  The purpose of the *\*.result* file is to provide high-level confirmation of success/failure.  If the *\*.result* file is empty, then assume failure.  Any output written to the *\*.result* file is also output to the system log (for example, `/var/log/messages`) by using the `logger` command. The *\*.result* filename has the same base name as the log file to allow for matching the result file with the configuration file and the backup log file.  The *\*.result* file goes into the same location as the other log files and is a simple one line output file, such as the following example:
 
 ```output
 Database # 1 (PR1) : completed ok