From bf13a6db6832da9c8f796f3f2f864d19640d34a6 Mon Sep 17 00:00:00 2001
From: Nathan <2266858+njmartin10@users.noreply.github.com>
Date: Tue, 6 Nov 2018 21:19:15 -0800
Subject: [PATCH] Typo: defintely->definitely

---
 src/static-guarantees/design-contracts.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/static-guarantees/design-contracts.md b/src/static-guarantees/design-contracts.md
index f0df219..4a243be 100644
--- a/src/static-guarantees/design-contracts.md
+++ b/src/static-guarantees/design-contracts.md
@@ -245,7 +245,7 @@ output_pin.set_bit(false);
 // output_pin.into_input_pull_down();
 ```
 
-This is defintely a convenient way to store the state of the pin, but why do it this way? Why is this better than storing the state as an `enum` inside of our `GpioConfig` structure?
+This is definitely a convenient way to store the state of the pin, but why do it this way? Why is this better than storing the state as an `enum` inside of our `GpioConfig` structure?
 
 ## Compile Time Functional Safety