Merge pull request #54 from ahippo/typo-fix

Fix typo in docs

README.md

@@ -68,7 +68,7 @@ results. If any test case fails, `bats` exits with a `1` status code.
 
 ## Writing tests
 
-Each Bats test file is evaulated n+1 times, where _n_ is the number of
+Each Bats test file is evaluated n+1 times, where _n_ is the number of
 test cases in the file. The first run counts the number of test cases,
 then iterates over the test cases and executes each one in its own
 process.

man/bats.7

@@ -30,7 +30,7 @@ A Bats test file is a Bash script with special syntax for defining test cases\.
 .IP "" 0
 .
 .P
-Each Bats test file is evaulated n+1 times, where \fIn\fR is the number of test cases in the file\. The first run counts the number of test cases, then iterates over the test cases and executes each one in its own process\.
+Each Bats test file is evaluated n+1 times, where \fIn\fR is the number of test cases in the file\. The first run counts the number of test cases, then iterates over the test cases and executes each one in its own process\.
 .
 .SH "THE RUN HELPER"
 Many Bats tests need to run a command and then make assertions about its exit status and output\. Bats includes a \fBrun\fR helper that invokes its arguments as a command, saves the exit status and output into special global variables, and then returns with a \fB0\fR status code so you can continue to make assertions in your test case\.

man/bats.7.ronn

@@ -22,7 +22,7 @@ description.
     }
 
 
-Each Bats test file is evaulated n+1 times, where _n_ is the number of
+Each Bats test file is evaluated n+1 times, where _n_ is the number of
 test cases in the file. The first run counts the number of test cases,
 then iterates over the test cases and executes each one in its own
 process.