From 587d1b9a6205ee2dd904bc7102fabd0a124ab116 Mon Sep 17 00:00:00 2001
From: Eric Nielsen <4120606+ericbn@users.noreply.github.com>
Date: Mon, 17 Jun 2024 20:18:25 -0500
Subject: [PATCH] Updated Troubleshooting (markdown)

---
 Troubleshooting.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/Troubleshooting.md b/Troubleshooting.md
index 6cbd7ef..64c10b3 100644
--- a/Troubleshooting.md
+++ b/Troubleshooting.md
@@ -2,16 +2,15 @@
 
 If you are using the `completion` module, there can be a conflict if other scripts are running `compinit` too.
 
-If you're getting a "warning: compinit being called again after completion module at ..." message in the terminal, then remove the `compinit` call from the mentioned file.
+In case you're getting a "warning: compinit being called again after completion module at ..." message in the terminal, then remove the `compinit` call from the mentioned file.
 
-If you're getting a "warning: completion was already initialized before completion module." message in the terminal, then follow
+In case you're getting a "warning: completion was already initialized before completion module." message in the terminal, then follow
 these steps to check further:
 
 1. Run the following code in your terminal, which will add lines to your `~/.zshenv` file:
    ```zsh
    >>! ~/.zshenv <<\END
    autoload -Uz +X compinit
-   functions[_original_compinit]=${functions[compinit]}
    functions[compinit]=$'print -u2 \'compinit being called at \'${funcfiletrace[1]}
    '${functions[compinit]}
    END