From 934d206a2853b6f3377722b13ece10546cb25aef Mon Sep 17 00:00:00 2001
From: Markus Billharz <50644328+MarkusBillharz@users.noreply.github.com>
Date: Tue, 25 Feb 2025 17:57:47 +0100
Subject: [PATCH] replace broken shader url

---
 ...n-anyone-explain-what-this-glsl-fragment-shader-is-doing-.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/webgl/lessons/webgl-qna-can-anyone-explain-what-this-glsl-fragment-shader-is-doing-.md b/webgl/lessons/webgl-qna-can-anyone-explain-what-this-glsl-fragment-shader-is-doing-.md
index b408c305a..48476fe9c 100644
--- a/webgl/lessons/webgl-qna-can-anyone-explain-what-this-glsl-fragment-shader-is-doing-.md
+++ b/webgl/lessons/webgl-qna-can-anyone-explain-what-this-glsl-fragment-shader-is-doing-.md
@@ -4,7 +4,7 @@ TOC: Can anyone explain what this GLSL fragment shader is doing?
 
 ## Question:
 
-I realise this is a math-centric question but... if you look at this webpage (and have a good graphics card) http://mrdoob.github.com/three.js/examples/webgl_shader.html
+I realise this is a math-centric question but... if you look at [this webpage](https://threejs.org/examples/?q=shader#webgl_shader). (and have a good graphics card)
 
 If you look at the source, you'll notice a scary looking fragment shader.