diff options
author | Xipmix <576337-xipmix@users.noreply.gitlab.com> | 2022-04-09 14:55:36 +1000 |
---|---|---|
committer | Xipmix <576337-xipmix@users.noreply.gitlab.com> | 2022-04-09 15:22:36 +1000 |
commit | 6009a09466c10e8f10ee275727baa854183f26a6 (patch) | |
tree | 41b61fa3e2d1a5b3011c7e37237b05db9b245853 | |
parent | 513f2daa9a3767d9535911276ffec772ab38b046 (diff) | |
download | subplot-6009a09466c10e8f10ee275727baa854183f26a6.tar.gz |
Reword opening sentence and tidy up related text
On a first reading, this sentence seemed circular to me.
After many, many rereadings, the only way I could interpret it
was as shown here.
Since the second paragraph is now repeating the first, prune it
and rearrange the line break in the second sentence.
-rw-r--r-- | subplot.md | 7 |
1 files changed, 3 insertions, 4 deletions
@@ -466,15 +466,14 @@ the kind of work that is implied by the kind of step it's bound to. ### Using Subplot's language effectively Your subplot scenarios will be best understood when they use the subplot -language in a fashion consistent with all subplot scenarios in your project(s). +language in a consistent fashion, within and even across *different* projects. As with programming languages, it's possible to place your own style on your subplots, indeed there is no inherent internal implementation difference between how `given`, `when` and `then` steps are processed (other than that `given` steps often also have cleanup functions associated with them). -There is, however, value in having consistency between -the subplot scenarios in *different* projects. Here is how we recommend you use -the Subplot language, and indeed how we use it in Subplot and related projects… +Here is how we recommend you use the Subplot language, +and indeed how we use it in Subplot and related projects… When you are formulating your scenarios, it is common to try and use phraseology along the lines of _if this happens then that is the case_ but this is not |