From 075bbb4262a72e58d73f592602de3b413726da00 Mon Sep 17 00:00:00 2001
From: Christopher C Fleming
 <63308959+ChristopherCFleming@users.noreply.github.com>
Date: Thu, 16 Dec 2021 21:51:06 -0500
Subject: [PATCH] docs: Fix typo on line 967 (#17785)

* Line 976 was wakeup, now wake up

* Removed package lock to test environment

* Return original package-lock.json
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3f60532e361ef..3312c51273430 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -964,7 +964,7 @@ You are now ready to attach a debugger to the process. Using VSCode you can conf
 }
 ```
 
-VSCode will not stop on breakpoints right away. We've attached to PID 6 however it does not yet know of any sub-processes. In order to "wakeup" the debugger you need to modify a python file. This will trigger Flask to reload the code and create a new sub-process. This new sub-process will be detected by VSCode and breakpoints will be activated.
+VSCode will not stop on breakpoints right away. We've attached to PID 6 however it does not yet know of any sub-processes. In order to "wake up" the debugger you need to modify a python file. This will trigger Flask to reload the code and create a new sub-process. This new sub-process will be detected by VSCode and breakpoints will be activated.
 
 ### Debugging Server App in Kubernetes Environment