Point remaining gist links to this repository

Author: hohn

c++/introduction/session-3/codeql-workshop-cpp-global-data-flow.md

@@ -5,7 +5,11 @@
 
 ## Problem statement
 
-In this workshop, we will use CodeQL to analyze the source code of [dotnet/coreclr](https://github.com/dotnet/coreclr), the runtime for .NET Core. This follows on from the [Introduction to local dataflow](https://gist.github.com/lcartey/db74e6041393062f9deef67456a229d3) workshop, and we recommend completing that workshop first.
+In this workshop, we will use CodeQL to analyze the source code of
+[dotnet/coreclr](https://github.com/dotnet/coreclr), the runtime for .NET
+Core. This follows on from the 
+[Introduction to local dataflow](../session-2/codeql-workshop-cpp-local-data-flow.md)
+workshop, and we recommend completing that workshop first. 
 
 Many security problems can be phrased in terms of _information flow_:
 
@@ -24,7 +28,8 @@ While local data flow is feasible to compute for all functions in a CodeQL datab
 
 The global data flow (and taint tracking) library avoids this problem by requiring that the query author specifies which _sources_ and _sinks_ are applicable. This allows the implementation to compute paths only between the restricted set of nodes, rather than for the full graph.
 
-In this workshop we will try to write a global data flow query to solve the format string problem introduced in the [Introduction to local dataflow](https://gist.github.com/lcartey/db74e6041393062f9deef67456a229d3) workshop.
+In this workshop we will try to write a global data flow query to solve the format
+string problem introduced in the [Introduction to local dataflow](../session-2/codeql-workshop-cpp-local-data-flow.md) 
 
 This workshops will provide:
  - Exploration of global data flow and taint tracking

c++/introduction/session-3/codeql-workshop-cpp-uboot.md

@@ -7,7 +7,12 @@
 
 In this workshop, we will use CodeQL to analyze the source code of [U-Boot loader](https://en.wikipedia.org/wiki/Das_U-Boot), an open source boot loader used in embedded devices.
 
-This workshop assumes you have completed the [CodeQL workshop for C/C++: Introduction to global data flow workshop](https://gist.github.com/lcartey/a53ff1221f4a50aad639d35df8b2e99a). If you have not, or if you prefer a more beginner focused approach to this content, you can use the [CodeQL U-Boot Challenge Learning Lab](https://lab.github.com/githubtraining/codeql-u-boot-challenge-(cc++)) course, which provides a self-guided step-by-step automated workflow.
+This workshop assumes you have completed the 
+[CodeQL workshop for C/C++: Introduction to global data flow workshop](codeql-workshop-cpp-global-data-flow.md). If
+you have not, or if you prefer a more beginner focused approach to this content,
+you can use the 
+[CodeQL U-Boot Challenge Learning Lab](https://lab.github.com/githubtraining/codeql-u-boot-challenge-(cc++)) course,
+which provides a self-guided step-by-step automated workflow. 
 
 The goal for this workshop is to find a set of 9 remote-code-execution vulnerabilities in the U-Boot boot loader. These vulnerabilities were originally discovered by GitHub Security Lab researchers and have since been fixed. An attacker with positioning on the local network, or control of a malicious NFS server, could potentially achieve remote code execution on the U-Boot powered device. This was possible because the code read data from the network (that could be attacker-controlled) and passed it to the length parameter of a call to the memcpy function. When such a length parameter is not properly validated before use, it may lead to exploitable memory corruption vulnerabilities.
 

c++/introduction/session-4/codeql-workshop-cpp-glibc-segv.md

@@ -7,7 +7,8 @@
 
 In this workshop, we will use CodeQL to analyze the source code of the [GNU C Library](https://www.gnu.org/software/libc/) (glibc).
 
-This workshop assumes you have completed the [CodeQL for C/C++: Introduction to global data flow workshop](https://gist.github.com/lcartey/a53ff1221f4a50aad639d35df8b2e99a).
+This workshop assumes you have completed the
+[CodeQL workshop for C/C++: Introduction to global data flow workshop](codeql-workshop-cpp-global-data-flow.md).
 
 The goal of this challenge is to find unsafe uses of `alloca` in glibc. [alloca](http://man7.org/linux/man-pages/man3/alloca.3.html) is used to allocate a buffer on the stack. It is usually implemented by simply subtracting the size parameter from the stack pointer and returning the new value of the stack pointer. This means that it has two important benefits: