From 37735a7065d08579985d596e34a891c5ff9e1ec7 Mon Sep 17 00:00:00 2001 From: Andrey Mazo Date: Tue, 20 May 2014 11:59:30 -0400 Subject: [PATCH] Fix typo in docs --- README.md | 2 +- man/bats.7 | 2 +- man/bats.7.ronn | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index a863264..4518573 100644 --- a/README.md +++ b/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. diff --git a/man/bats.7 b/man/bats.7 index 47836ef..d0836e5 100644 --- a/man/bats.7 +++ b/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\. diff --git a/man/bats.7.ronn b/man/bats.7.ronn index e5377a4..7f6dd18 100644 --- a/man/bats.7.ronn +++ b/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.