summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXipmix <576337-xipmix@users.noreply.gitlab.com>2022-04-09 15:00:31 +1000
committerXipmix <576337-xipmix@users.noreply.gitlab.com>2022-04-09 15:23:24 +1000
commit32dd5f713bcf9980273c9e975f4e3d0d2a25af35 (patch)
tree2ded3323b754cc87839a76178d139ec8a4b06b5f
parent6009a09466c10e8f10ee275727baa854183f26a6 (diff)
downloadsubplot-32dd5f713bcf9980273c9e975f4e3d0d2a25af35.tar.gz
Break long sentence
-rw-r--r--subplot.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/subplot.md b/subplot.md
index 5dea8a2..5743def 100644
--- a/subplot.md
+++ b/subplot.md
@@ -468,7 +468,7 @@ the kind of work that is implied by the kind of step it's bound to.
Your subplot scenarios will be best understood when they use the subplot
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
+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).