diff --git a/README.md b/README.md
index fc7863a..0578243 100644
--- a/README.md
+++ b/README.md
@@ -1,19 +1,10 @@
+link to shadertoy: https://www.shadertoy.com/view/4XlyDj
 # lab02-debugging
+Name: Jinxiang Wang
+Bugs found: 
+1. Compiler error vec uv2;
+2. Change vec uv2 to uv;
+3. Change vec2 uv = fragCoord.xy/iResolution.xy to uv = fragCoord.xy/iResolution.y; 
+4. In march() change iteration from 64 to 256;
+5. In sdf3D() change reflect(eye, nor) to reflect(dir, nor);
 
-# 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!)