GUD is gone

Author: badboy

src/concepts/glean/glean.md

@@ -37,7 +37,7 @@ Because Glean knows more about the individual data, such as its type and the ran
 
 **Provide a consistent base of telemetry**
 
-A baseline of analysis is important for all our products, from counting active users to retention and session times. This is supported out-of-the-box by the SDK, and funnels directly into visualization tools like the [Growth and Usage Dashboard (GUD)](https://gud.telemetry.mozilla.org/).
+A baseline of analysis is important for all our products, from counting active users to retention and session times. This is supported out-of-the-box by the SDK, and funnels directly into visualization tools like the [Growth and Usage Dashboard (GUD)](../../cookbooks/looker/growth_usage_dashboards.md).
 
 Metrics that are common to all products, such as the operating system and architecture, are provided automatically in a consistent way.
 

src/cookbooks/clients_last_seen_bits.md

@@ -111,7 +111,7 @@ when we report a retention value for 2020-01-01, we're talking about what
 portion of clients active on 2020-01-01 are still active some number of days
 later.
 
-In particular, let's consider the "1-Week Retention" measure shown in [GUD](https://gud.telemetry.mozilla.org/)
+In particular, let's consider the "1-Week Retention" measure shown in [GUD]
 which considers a window of 14 days.
 For each client active in "week 0" (days 0 through 6), we determine retention by
 checking if they were also active in "week 1" (days 7 through 13).
@@ -434,7 +434,7 @@ When we define forward-looking windows, however, we always choose a metric date
 some time in the past. How we number the individual bits depends on what
 metric date we choose.
 
-For example, in [GUD](https://gud.telemetry.mozilla.org/), we show a "1-Week Retention" which considers a window of 14 days.
+For example, in [GUD] we show a "1-Week Retention" which considers a window of 14 days.
 For each client active in "week 0" (days 0 through 6), we determine retention by
 checking if they were also active in "week 1" (days 7 through 13).
 
@@ -899,3 +899,5 @@ the standard 1-Week, 2-Week, and 3-Week retention definitions.
 ```sql
 bits28.retention(bits INT64, submission_date DATE)
 ```
+
+[gud]: looker/growth_usage_dashboards.md

src/metrics/index.md

@@ -5,8 +5,6 @@
 This section provides an overview of standard metrics used at Mozilla.
 Here you'll find the definitions and descriptions for each.
 
-For a deep dive into these metrics, see [the GUD documentation](https://mozilla.github.io/gud/).
-
 The [Telemetry Behavior Reference](../concepts/index.md) section also provides
 information related to the definitions below.
 
@@ -49,7 +47,7 @@ specified day, what proportion (out of 1) are active during the following week.
 ## Frequently Asked Questions
 
 - Why isn't "New Users" a metric?
-  - "New Users" is considered a [usage criterion], which means it may be used
+  - "New Users" is considered a usage criterion, which means it may be used
     to filter other metrics, rather than itself being a metric. For example,
     you can compute "New User DAU", which would be the subset of DAU that match
     the "New User" criterion. The exception here is 1-Week New Profile
@@ -62,6 +60,5 @@ specified day, what proportion (out of 1) are active during the following week.
   - For Firefox Desktop, we use the `main` ping to determine activity.
   - For products instrumented using Glean, we use the `baseline` ping.
 
-[usage criterion]: https://mozilla.github.io/gud#data-model
 [submission dates]: https://bugzilla.mozilla.org/show_bug.cgi?id=1422892
 [pings]: ../datasets/pings.md