summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2019-05-04 14:21:11 +0300
committerLars Wirzenius <liw@liw.fi>2019-05-04 14:21:11 +0300
commit4868d6c6eaf997160e92c07c1e9b763af98f6e38 (patch)
tree2b5103b01973c6df487911c7b95df72433bddd62
parentb53ee5e6d5efa6b84cb2cea04b5e16dc1586b18f (diff)
downloadsaga-poc-4868d6c6eaf997160e92c07c1e9b763af98f6e38.tar.gz
Fix: typos and spellos
-rw-r--r--saga.yarn8
1 files changed, 4 insertions, 4 deletions
diff --git a/saga.yarn b/saga.yarn
index 70263e4..29cc8b6 100644
--- a/saga.yarn
+++ b/saga.yarn
@@ -23,7 +23,7 @@ abstract: |
Saga is a tool for acceptance testing of software. This means it helps
software developers and teams to make sure their software fulfils the
-acceptance criterita for the software. Such criteria may come from
+acceptance criteria for the software. Such criteria may come from
users, the developers, their employers, or other elsewhere.
Saga is specifically mean for automated acceptance testing. It takes a
@@ -34,7 +34,7 @@ automated tests for non-technical stakeholders.
More concretely, Saga helps developers implement and document their
automated acceptance tests in a way that, at the same time, helps the
-developers automatically test their software, and write documention
+developers automatically test their software, and write documentation
for the tests in way that doesn't require programming knowledge to
understand.
@@ -70,7 +70,7 @@ in which a sequence of actions are taken, and then the results are
checked. If the checks fail, the scenario fails.
Saga runs the scenarios concurrently (but see the USING keyword),
-within the constraings of hardware resources. If Saga determines it
+within the constrains of hardware resources. If Saga determines it
doesn't have all the CPU and RAM to run all scenarios at once, it will
run fewer, but randomly chosen scenarios concurrently, to more likely
to detect unintentional dependencies between scenarios.
@@ -138,7 +138,7 @@ The language understood by Saga has the following general structure:
* each logical line starts with a keyword at the beginning of the line
* logical lines may be broken into physical lines, by starting the
continuation lines with one or more space or TAB characters; the
- physical line break and whitespace characters are preserved
+ physical line break and white space characters are preserved
* logical lines define steps in a test scenario
* the meaning and implementation of the steps are defined by other
Saga input files