From 4cb4732818dc2141da9f8d67dce7e5fcd3ee05c6 Mon Sep 17 00:00:00 2001
From: Cindy Xu <88256581+CIIINDYXUU@users.noreply.github.com>
Date: Wed, 20 Sep 2023 11:50:52 -0400
Subject: [PATCH] Update README.md

---
 README.md | 16 +++++-----------
 1 file changed, 5 insertions(+), 11 deletions(-)

diff --git a/README.md b/README.md
index aa0f112..d6c96ab 100644
--- a/README.md
+++ b/README.md
@@ -1,19 +1,13 @@
 # lab06-debugging
 
+# Submission
+- Did this lab individually
+- Debugged Shadertoy Link: https://www.shadertoy.com/view/Dscyzj
+- found 5/5 bugs :)
+  
 # Setup 
 
 Create a [Shadertoy account](https://www.shadertoy.com/). Either fork this shadertoy, or create a new shadertoy and copy the code from the [Debugging Puzzle](https://www.shadertoy.com/view/flGfRc).
 
 Let's practice debugging! We have a broken shader. It should produce output that looks like this:
 [Unbelievably beautiful shader](https://user-images.githubusercontent.com/1758825/200729570-8e10a37a-345d-4aff-8eff-6baf54a32a40.webm)
-
-It don't do that. Correct THREE of the FIVE bugs that are messing up the output. You are STRONGLY ENCOURAGED to work with a partner and pair program to force you to talk about your debugging thought process out loud.
-
-Extra credit if you can find all FIVE bugs.
-
-# Submission
-- Create a pull request to this repository
-- In the README, include the names of both your team members
-- In the README, create a link to your shader toy solution with the bugs corrected
-- In the README, describe each bug you found and include a sentence about HOW you found it.
-- Make sure all three of your shadertoys are set to UNLISTED or PUBLIC (so we can see them!)