summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXipmix <576337-xipmix@users.noreply.gitlab.com>2022-04-09 15:10:30 +1000
committerXipmix <576337-xipmix@users.noreply.gitlab.com>2022-04-09 15:23:24 +1000
commit307a37c2269058658a581838c31ab48d762d762c (patch)
tree948e590012b539aba191424244d0571bbca8d99a
parentd3bdc9640bcfbea7a66f605ebd6b34acac5f5632 (diff)
downloadsubplot-307a37c2269058658a581838c31ab48d762d762c.tar.gz
'should be' feels wrong here, 'are' seems a better fit
-rw-r--r--subplot.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/subplot.md b/subplot.md
index dc2499c..5098d74 100644
--- a/subplot.md
+++ b/subplot.md
@@ -497,7 +497,7 @@ to inform the reader that some precondition is met. These statements are often
best along the lines of `given a setup which works` or `given a development enviroment`
or somesuch.
-The `when` statements should be best used to denote **active** steps. These are
+The `when` statements are best used to denote **active** steps. These are
the steps which your putative actors or personae use to achieve their goals.
These often work best in the form `when I do the thing` or
`when the user does the thing`.