README.md change only: correct spelling.
The files in here are used internally within u-blox to automate testing of `ubxlib`. They are not supported externally. However, if you find them useful please help yourselves.
# Reading The Jenkins Output
-Since much of the test execution is inside these Python scripts the Jenkins level Groovy script `Jenkinsfile` doesn't do a great deal. To see how testing has gone look in the Jenkins artifacts for files named `summary.log`. There should be one at the top level and another inside the folder for each instance. Check the top level `summary.log` to see how the run went. The `summary.log` file inside each instance folder contains the portion of the summary for that instance but adds no aditional information so, if there is a problem, check the `debug.log` file inside the instance folder for more detailed information.
+Since much of the test execution is inside these Python scripts the Jenkins level Groovy script `Jenkinsfile` doesn't do a great deal. To see how testing has gone look in the Jenkins artifacts for files named `summary.log`. There should be one at the top level and another inside the folder for each instance. Check the top level `summary.log` to see how the run went. The `summary.log` file inside each instance folder contains the portion of the summary for that instance but adds no additional information so, if there is a problem, check the `debug.log` file inside the instance folder for more detailed information.
The best approach to looking for failures is to search for " \*\*\* ", i.e. a space, three asterisks, then a space, in these files. Search first in the top-level summary log file to find any failures or warnings and determine which instance caused them. When you have determined the instance, go to the directory of that instance, open the debug log file there and search for the same string again to find the failure and warning markers within the detailed trace.
