From 0b2ea793298356ab6772f37dc8fe5e5610bb53e8 Mon Sep 17 00:00:00 2001 From: Michael Miller Date: Wed, 31 Mar 2021 16:07:01 -0600 Subject: [PATCH] Grammar --- src/spectator.cr | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/spectator.cr b/src/spectator.cr index 3dff022..4a31964 100644 --- a/src/spectator.cr +++ b/src/spectator.cr @@ -20,18 +20,18 @@ module Spectator # One of those is testing Spectator. class_property? autorun = true - # All tests are ran just before the executable exits. + # All tests run just before the executable exits. # Tests will be skipped, however, if `#autorun?` is set to false. # There are a couple of reasons for this. # # First is that we want a clean interface for the end-user. # They shouldn't need to call a "run" method. - # That adds the burden on the developer to ensure the tests are run after they are created. + # That adds burden on the developer to ensure the tests run after they are created. # And that gets complicated when there are multiple files that could run in any order. # # Second is to allow all of the tests and framework to be constructed. # We know that all of the instances and DSL builders have finished - # after the main part of the executable has run. + # after the main part of the executable has completed. # # By doing this, we provide a clean interface and safely run after everything is constructed. # The downside, if something bad happens, like an exception is raised,