From 23c9c47d606c368a694c2385866fa106033c7387 Mon Sep 17 00:00:00 2001
From: Evan Hemsley <2342303+ehemsley@users.noreply.github.com>
Date: Wed, 12 Jun 2019 11:44:18 -0700
Subject: [PATCH] fix typo

---
 content/pong/move_paddle/decoupling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/pong/move_paddle/decoupling.md b/content/pong/move_paddle/decoupling.md
index ce84981..4987a12 100644
--- a/content/pong/move_paddle/decoupling.md
+++ b/content/pong/move_paddle/decoupling.md
@@ -10,7 +10,7 @@ Really, when we talk about decoupling, we are saying that we don't want the stru
 
 This is a pretty abstract principle, but there is a nice illustration of it in our program as it exists right now.
 
-Right now our InputEngine is sending Messages to our MotionMessage. Is that actually what we want?
+Right now our InputEngine is sending Messages to our MotionEngine. Is that actually what we want?
 
 What I am saying is... can you think of an example where something other than direct input might want to control the movement of a paddle?