diff --git a/fixKnowledge/ssh-connection-errors-deployment.md b/fixKnowledge/ssh-connection-errors-deployment.md
index 968d047..7067924 100644
--- a/fixKnowledge/ssh-connection-errors-deployment.md
+++ b/fixKnowledge/ssh-connection-errors-deployment.md
@@ -16,6 +16,8 @@ mux_client_request_session: send fds failed
 
 These errors appeared at step 5 of the deployment script when checking if Git is initialized on the server.
 
+Additionally, the script could hang indefinitely at step 5 due to command substitution blocking when SSH connections failed or timed out.
+
 ## Impact
 
 - **Severity**: Medium
@@ -39,6 +41,8 @@ The SSH ControlMaster feature creates a persistent connection to avoid multiple
 - Network interruptions can close the master connection
 - The ControlMaster socket file can become stale if the connection dies
 - The script did not detect or handle these cases, leading to cascading failures
+- Command substitution `$()` with SSH commands can block indefinitely if the connection hangs
+- The original logic used `grep` on command output, which required capturing all output and could hang
 
 ## Corrections Applied
 
@@ -67,6 +71,9 @@ The SSH ControlMaster feature creates a persistent connection to avoid multiple
 - Added explicit error detection and recovery mechanism
 - Added automatic retry after connection cleanup
 - Better error messages to distinguish between connection errors and Git initialization needs
+- **Fixed blocking issue**: Removed command substitution `$()` that could hang indefinitely
+- Simplified logic to use direct exit code checking instead of parsing output
+- Improved timeout handling to prevent script from hanging
 
 ## Modifications