Add chapters

2 files changed, 0 insertions, 35 deletions

diff --git a/lessons/src/lesson099_documentation_comments/code.gleam b/lessons/src/lesson099_documentation_comments/code.gleam
deleted file mode 100644
index a84dce6..0000000
--- a/lessons/src/lesson099_documentation_comments/code.gleam
+++ /dev/null
@@ -1,19 +0,0 @@
-//// A module containing some unusual functions and types.
-
-/// A type where the value can never be constructed.
-/// Can you work out why?
-pub type Never {
-  Never(Never)
-}
-
-/// Call a function twice with an initial value.
-///
-pub fn twice(argument: value, function: fn(value) -> value) -> value {
-  function(function(argument))
-}
-
-/// Call a function three times with an initial value.
-///
-pub fn thrice(argument: value, function: fn(value) -> value) -> value {
-  function(function(function(argument)))
-}
diff --git a/lessons/src/lesson099_documentation_comments/text.html b/lessons/src/lesson099_documentation_comments/text.html
deleted file mode 100644
index c27bac6..0000000
--- a/lessons/src/lesson099_documentation_comments/text.html
+++ /dev/null
@@ -1,16 +0,0 @@
-<p>
-  Documentation and comments are important tools for making your code easier to
-  work with and understand.
-</p>
-<p>
-  As well as regular <code>//</code> comments Gleam has <code>///</code> and
-  <code>////</code> comments which are used for attaching documentation to code.
-</p>
-<p>
-  <code>///</code> is used for documenting types and functions, and should be
-  placed immediately before the type or function it is documenting.
-</p>
-<p>
-  <code>////</code> is used for documenting modules, and should be placed
-  at the top of the module.
-</p>