Updated program to application

docs/Troubleshooting/checkinglogs.md

@@ -1,6 +1,6 @@
 # Checking log files
 
-The best way to see what a program is doing is to see what is in the logs for the particular program, by defaul logs are in the `/var/log` directory but they can also be in others as well
+The best way to see what a application is doing is to see what is in the logs for the particular application, by defaul logs are in the `/var/log` directory but they can also be in others as well
 
 ## Common log locations
 
@@ -15,7 +15,7 @@ The best way to see what a program is doing is to see what is in the logs for th
 
 ## Reading logs
 
-You can read the log files using command line programs like `cat` and `less`, cat will just print the file to the terminal where less will open the file up in a [pager](/Commands/pagers), this allows for things like searching without closing the logs
+You can read the log files using command line applications like `cat` and `less`, cat will just print the file to the terminal where less will open the file up in a [pager](/Commands/pagers), this allows for things like searching without closing the logs
 
 You can open a log with something like `less /var/log/mainlog` this will allow you to read over the log and search for the information that you wanted
 
@@ -27,4 +27,4 @@ If you wanted to watch the logs live as you are testing something you can use th
 
 The Archived logs will usually be in a compressed gzip format with the date code and the .gz extenstion.
 
-You can read these logs by either uncompressing them using `gzip -d` or you can use some handy versions of commands like `cat` and `grep` that are built to work with compression, these are `zcat` and `zgrep`
+You can read these logs by either uncompressing them using `gzip -d` or you can use some handy versions of commands like `cat` and `grep` that are built to work with compression, these are `zcat` and `zgrep``