From 49963f6e5598e4fc819eba84b7fbe7f5ee6b8c98 Mon Sep 17 00:00:00 2001
From: Enjeck Cleopatra <32180937+PROTechThor@users.noreply.github.com>
Date: Sat, 10 Oct 2020 09:55:22 +0100
Subject: [PATCH] Minor word change

---
 user/troubleshooting/resume-suspend-troubleshooting.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/user/troubleshooting/resume-suspend-troubleshooting.md b/user/troubleshooting/resume-suspend-troubleshooting.md
index 124465d3..4844ccae 100644
--- a/user/troubleshooting/resume-suspend-troubleshooting.md
+++ b/user/troubleshooting/resume-suspend-troubleshooting.md
@@ -9,7 +9,7 @@ redirect_from:
 
 # Troubleshooting problems relating to suspend/resume #
 
-## Network-Manager says “Device not ready” after suspend/resume ##
+## Network-Manager says “Device not ready” on suspend/resume ##
 
 These instructions may help with suspend/resume issues for more devices than just wireless cards, that is just the (unfortunately not uncommon) example used here.
 
@@ -118,7 +118,7 @@ iwlmvm
 iwlwifi
 ~~~
 
-## Power consumption increases after suspend/resume ##
+## Power consumption increases on suspend/resume ##
 
 This problem is related to the software method used to disable sibling threads and how it interacts with suspend/resume. 
 To solve the problem, disable hyperthreading in the BIOS. This [external guide](https://www.pcmag.com/news/how-to-disable-hyperthreading) explains how to disable hyperthreading.