From 2c4157b62fb921ee77e0079fae372d1e94643a08 Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Tue, 24 Oct 2023 14:30:25 -0400
Subject: [PATCH 1/4] Update faq/syllabus.md

---
 faq/syllabus.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/faq/syllabus.md b/faq/syllabus.md
index 4398208..b1c4de9 100644
--- a/faq/syllabus.md
+++ b/faq/syllabus.md
@@ -66,3 +66,17 @@ excerpts or screenshots embedded in it.
 They should be markdown files in your KWL repo.  I recommend myst markdown.
 ```
 
+## Why won't my experience badge workflow contain the new changes after I edit the workflow?
+```{toggle}
+If you find that a workflow you may have made changes to are not properly reflecting your workflow changes is because you may not be running the workflow correctly.
+
+To correctly execute an action in GitHub you should:
+
+1. Make sure you are in the actions tab in your repository
+2. On the left side of the screen the specific workflows should be available to select. 
+3. Select the desired workflow.
+4. At the top of the workflow runs there should be an option to run the workflow.
+5. Select Run Workflow to run the most recent and up to date workflow.
+
+This should help correct the workflow if it was causing issues.
+```
\ No newline at end of file

From 36c4eb5fa5351cd7dd127cee55dc1e131c85c73b Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Tue, 24 Oct 2023 14:34:28 -0400
Subject: [PATCH 2/4] Update faq/syllabus.md

---
 faq/syllabus.md | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/faq/syllabus.md b/faq/syllabus.md
index b1c4de9..4398208 100644
--- a/faq/syllabus.md
+++ b/faq/syllabus.md
@@ -66,17 +66,3 @@ excerpts or screenshots embedded in it.
 They should be markdown files in your KWL repo.  I recommend myst markdown.
 ```
 
-## Why won't my experience badge workflow contain the new changes after I edit the workflow?
-```{toggle}
-If you find that a workflow you may have made changes to are not properly reflecting your workflow changes is because you may not be running the workflow correctly.
-
-To correctly execute an action in GitHub you should:
-
-1. Make sure you are in the actions tab in your repository
-2. On the left side of the screen the specific workflows should be available to select. 
-3. Select the desired workflow.
-4. At the top of the workflow runs there should be an option to run the workflow.
-5. Select Run Workflow to run the most recent and up to date workflow.
-
-This should help correct the workflow if it was causing issues.
-```
\ No newline at end of file

From be4e509286363fea90b8d032e03fe614abb4e6cf Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Tue, 28 Nov 2023 14:18:15 -0500
Subject: [PATCH 3/4] Update 2023-10-19.md

typo
---
 notes/2023-10-19.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/notes/2023-10-19.md b/notes/2023-10-19.md
index ba314df..df64776 100644
--- a/notes/2023-10-19.md
+++ b/notes/2023-10-19.md
@@ -5,7 +5,7 @@ kernelspec:
 ---
 
 
-# Why did we learn the plubming commands?
+# Why did we learn the plumbing commands?
 
 You will not typically use them on a day to day basis, but they are a good way to see what happens at the interim steps and make sure that you have the right understanding of what git does.  
 
@@ -1061,4 +1061,4 @@ save your command history to `2023-10-19-log.txt` and put that file in your KWL
 
 ```{note}
 due to scheduling issues this will be late today
-```
\ No newline at end of file
+```

From c781dbdbd5d6a2906aa3628329663139c724da49 Mon Sep 17 00:00:00 2001
From: Trevor Moy <51927676+trevmoy@users.noreply.github.com>
Date: Thu, 14 Dec 2023 10:25:36 -0500
Subject: [PATCH 4/4] Updated resources/testimonials.md

---
 resources/testimonials.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/resources/testimonials.md b/resources/testimonials.md
index 4429356..6bcb2f0 100644
--- a/resources/testimonials.md
+++ b/resources/testimonials.md
@@ -1,3 +1,5 @@
 # Testimonials from Fall 2023 students
 
 The best way to succeed in this course is to start badges as early as possible. Waiting till the end of the semester to finish up a lot of it creates unnecessary stress and it is something that I regret doing myself. I would also recommend going over the notes after they are posted to reinforce what you learned during the class. All the topics build on each other so this is something I’m glad I did. Do your best to stay on top of the work early to make the end of the semester easier. If you do these you’ll have no trouble passing the class and you’ll definitely finish it being glad you took it.
+
+The best way that you can succeed in CSC 392 is to practice with the course content and get ahead on the badges. Taking the time to complete badges is the best way to do this and the more consistently you can get your badges done, the more practice and skills you're going to improve with this course. Definitely work to get your explore and build badges out of the way early on because they will sneak up out of nowhere and make your life unnecessarily tough. The class is a great preview of what collaboration in an actual workplace might look like so make sure to actively participate to get the full lerning experience.
\ No newline at end of file