From 745baf3da573db6a57362b539fd44c4f2287de76 Mon Sep 17 00:00:00 2001 From: "Michael B. Sumulong" Date: Tue, 20 Apr 2021 08:59:20 -0400 Subject: [PATCH] Fix typo --- executable-tutorials.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/executable-tutorials.org b/executable-tutorials.org index daff454..fe3874f 100644 --- a/executable-tutorials.org +++ b/executable-tutorials.org @@ -3,7 +3,7 @@ When building a large and complex software project, you'd like to be able to make a change to the code base and be sure that the software still works as intended. Nowadays, folks use automated tests to check that things work after code changes. -Let's say you're working on a long and complex tutorial for building some kind of software application. At some point, you decide to change something in the middle of the tutorial. Now, how do you know that your tutorial still works? Experienced tutorial writers know that one option is to occasionally go throught the entire tutorial again to make sure that the steps still lead to the expected resultant project. Another option is to rely on readers of the tutorial to report issues after any changes are made. +Let's say you're working on a long and complex tutorial for building some kind of software application. At some point, you decide to change something in the middle of the tutorial. Now, how do you know that your tutorial still works? Experienced tutorial writers know that one option is to occasionally go through the entire tutorial again to make sure that the steps still lead to the expected resultant project. Another option is to rely on readers of the tutorial to report issues after any changes are made. Or, you can make your tutorial executable and unit tested.