diff --git a/docs/technical-details/reference/components/applications.md b/docs/technical-details/reference/components/applications.md
index 0f8a659e..6b37592a 100644
--- a/docs/technical-details/reference/components/applications.md
+++ b/docs/technical-details/reference/components/applications.md
@@ -24,7 +24,7 @@ The `harperdb dev .` command will automatically watch for file changes within th
 
 The `dev` command will **not** restart the main thread; if this is a requirement, switch to using `run` instead and manually start/stop the process to execute the main thread.
 
-Stop execution for either of these processes by sending a SIGINT (generally CTRL/CMD+C) signal to the process.
+Stop execution for either of these processes by sending a SIGINT (generally CTRL+C) signal to the process.
 
 ### Deploying to a local Harper instance
 
diff --git a/versioned_docs/version-4.4/developers/components/managing.md b/versioned_docs/version-4.4/developers/components/managing.md
index ced912a3..332a6699 100644
--- a/versioned_docs/version-4.4/developers/components/managing.md
+++ b/versioned_docs/version-4.4/developers/components/managing.md
@@ -22,7 +22,7 @@ The `harperdb dev .` command will automatically watch for file changes within th
 
 The `dev` command will **not** restart the main thread; if this is a requirement, switch to using `run` instead and manually start/stop the process to execute the main thread.
 
-Stop execution for either of these processes by sending a SIGINT (generally CTRL/CMD+C) signal to the process.
+Stop execution for either of these processes by sending a SIGINT (generally CTRL+C) signal to the process.
 
 ### Deploying to a local Harper instance
 
diff --git a/versioned_docs/version-4.5/developers/components/managing.md b/versioned_docs/version-4.5/developers/components/managing.md
index ced912a3..332a6699 100644
--- a/versioned_docs/version-4.5/developers/components/managing.md
+++ b/versioned_docs/version-4.5/developers/components/managing.md
@@ -22,7 +22,7 @@ The `harperdb dev .` command will automatically watch for file changes within th
 
 The `dev` command will **not** restart the main thread; if this is a requirement, switch to using `run` instead and manually start/stop the process to execute the main thread.
 
-Stop execution for either of these processes by sending a SIGINT (generally CTRL/CMD+C) signal to the process.
+Stop execution for either of these processes by sending a SIGINT (generally CTRL+C) signal to the process.
 
 ### Deploying to a local Harper instance
 
diff --git a/versioned_docs/version-4.6/technical-details/reference/components/applications.md b/versioned_docs/version-4.6/technical-details/reference/components/applications.md
index 0f8a659e..6b37592a 100644
--- a/versioned_docs/version-4.6/technical-details/reference/components/applications.md
+++ b/versioned_docs/version-4.6/technical-details/reference/components/applications.md
@@ -24,7 +24,7 @@ The `harperdb dev .` command will automatically watch for file changes within th
 
 The `dev` command will **not** restart the main thread; if this is a requirement, switch to using `run` instead and manually start/stop the process to execute the main thread.
 
-Stop execution for either of these processes by sending a SIGINT (generally CTRL/CMD+C) signal to the process.
+Stop execution for either of these processes by sending a SIGINT (generally CTRL+C) signal to the process.
 
 ### Deploying to a local Harper instance