From ed8c00f01f56dd150ea5a8597822cd505a6cbb79 Mon Sep 17 00:00:00 2001
From: Louis Pilfold <louis@lpil.uk>
Date: Tue, 26 Mar 2024 11:40:04 +0000
Subject: Remove link

---
 src/content/chapter0_basics/lesson02_modules/en.html | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

(limited to 'src/content/chapter0_basics/lesson02_modules/en.html')

diff --git a/src/content/chapter0_basics/lesson02_modules/en.html b/src/content/chapter0_basics/lesson02_modules/en.html
index ebfd8bc..0ece645 100644
--- a/src/content/chapter0_basics/lesson02_modules/en.html
+++ b/src/content/chapter0_basics/lesson02_modules/en.html
@@ -1,12 +1,8 @@
 <p>
   Gleam code is organized into units called <em>modules</em>. A module is a
   bunch of definitions (of types, functions, etc.) that seem to belong together.
-  For example, the
-  <a href="https://hexdocs.pm/gleam_stdlib/gleam/io.html">
-    <code>gleam/io</code>
-  </a>
-  module contains a variety of functions for printing, like
-  <code>println</code>.
+  For example, the <code>gleam/io</code> module contains a variety of functions
+  for printing, like <code>println</code>.
 </p>
 <p>
   All gleam code is in <i>some</i> module or other, whose name comes from the
-- 
cgit v1.2.3