From ea4c5546d8f99e366fc62dd9e462ae86d591edb2 Mon Sep 17 00:00:00 2001
From: CharlesCNorton <135471798+CharlesCNorton@users.noreply.github.com>
Date: Tue, 9 Jul 2024 11:18:37 -0400
Subject: [PATCH] fix: typos in reset context comments (#2453)

Corrected two typos and a grammatical issue in the comments within the reset context code. Specifically:
- Changed "indictate" to "indicate"
- Corrected "me might" to "we might"

Signed-off-by: CharlesCNorton <135471798+CharlesCNorton@users.noreply.github.com>
---
 gpt4all-chat/chat.cpp | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gpt4all-chat/chat.cpp b/gpt4all-chat/chat.cpp
index 5874abe3..e51126ad 100644
--- a/gpt4all-chat/chat.cpp
+++ b/gpt4all-chat/chat.cpp
@@ -90,10 +90,10 @@ void Chat::reset()
     emit resetContextRequested();
     m_id = Network::globalInstance()->generateUniqueId();
     emit idChanged(m_id);
-    // NOTE: We deliberately do no reset the name or creation date to indictate that this was originally
+    // NOTE: We deliberately do no reset the name or creation date to indicate that this was originally
     // an older chat that was reset for another purpose. Resetting this data will lead to the chat
     // name label changing back to 'New Chat' and showing up in the chat model list as a 'New Chat'
-    // further down in the list. This might surprise the user. In the future, we me might get rid of
+    // further down in the list. This might surprise the user. In the future, we might get rid of
     // the "reset context" button in the UI. Right now, by changing the model in the combobox dropdown
     // we effectively do a reset context. We *have* to do this right now when switching between different
     // types of models. The only way to get rid of that would be a very long recalculate where we rebuild