diff options
| author | Lars Wirzenius <liw@liw.fi> | 2022-10-07 08:48:06 +0300 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2022-10-07 09:09:08 +0300 |
| commit | 2e0b7a2223a64c4b95f065b7096c07221c1b79d0 (patch) | |
| tree | f6e13fe1665a3ae92e41ba2b265883eadd3de9e1 | |
| parent | a01b5d05ec0c7af6782ec31c169a0bc1331cf71c (diff) | |
| download | subplot.liw.fi-2e0b7a2223a64c4b95f065b7096c07221c1b79d0.tar.gz | |
docs(tutorial.md): drop trailing space
Sponsored-by: author
| -rw-r--r-- | tutorial.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tutorial.mdwn b/tutorial.mdwn index fc8fb8f..95b7310 100644 --- a/tutorial.mdwn +++ b/tutorial.mdwn @@ -118,7 +118,7 @@ requirements. A scenario has an overall structure of given/when/then: These are embedded in markdown using **fenced code blocks** marked as containing `scenario` text. Subplot extracts these and -generates a test program to execute them. +generates a test program to execute them. The scenario steps need to be formulated in a way that all stakeholders in the project understand. This is crucial. The scenario |