From 3496d0df2e4a741d54a386d7355dd301ba259ab8 Mon Sep 17 00:00:00 2001
From: mkcisse <45665262+mkcisse@users.noreply.github.com>
Date: Mon, 25 Feb 2019 11:29:14 +0100
Subject: [PATCH] Evaulate -> Evaluate

---
 07_2_Running_a_Bitcoin_Script.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/07_2_Running_a_Bitcoin_Script.md b/07_2_Running_a_Bitcoin_Script.md
index 47b6250..3e3a53b 100644
--- a/07_2_Running_a_Bitcoin_Script.md
+++ b/07_2_Running_a_Bitcoin_Script.md
@@ -222,7 +222,7 @@ As we've seen, every input for a Bitcoin transaction contains a `scriptSig` that
 
 So, presume that a UTXO were locked with a `scriptPubKey` that read `OP_ADD 99 OP_EQUAL`, requiring as input two numbers that add up to ninety-nine, and presume that the `scriptSig` of `1 98` were run to unlock it. The two scripts would effectively be run in order as `1 98 OP_ADD 99 OP_EQUAL`.
 
-Evaulate the result:
+Evaluate the result:
 ```
 Script: 1 98 OP_ADD 99 OP_EQUAL
 Stack: []