Update content for Gleam v1.6.0

src/content/chapter3_data_types/lesson03_record_accessors/code.gleam

@@ -11,5 +11,5 @@ pub fn main() {
 
   io.debug(teacher.name)
   io.debug(student.name)
-  // io.debug(teacher.subject)
+  // io.debug(student.subject)
 }

src/content/chapter3_data_types/lesson03_record_accessors/en.html

@@ -3,16 +3,18 @@
   contained values from a custom type record.
 </p>
 <p>
-  The accessor syntax can only be used for fields with the same name that are in
-  the same position and have the same type for all variants of the custom type.
+  The accessor syntax can always be used for fields with the same name that are
+  in the same position and have the same type for all variants of the custom
+  type. Other fields can only be accessed when the compiler can tell which
+  variant the value is, such after pattern matching in a `case` expression.
 </p>
 <p>
   The <code>name</code> field is in the first position and has type
   <code>String</code> for all variants, so it can be accessed.
 </p>
 <p>
   The <code>subject</code> field is absent on the <code>Student</code> variant,
-  so it cannot be used on any variant of type <code>SchoolPerson</code>.
-  Uncomment the <code>teacher.subject</code> line to see the compile error from
+  so it cannot be used on all values of type <code>SchoolPerson</code>.
+  Uncomment the <code>student.subject</code> line to see the compile error from
   trying to use this accessor.
 </p>

src/content/chapter3_data_types/lesson04_record_pattern_matching/code.gleam

@@ -10,16 +10,20 @@ pub type IceCream {
 }
 
 pub fn main() {
-  let lucy = Starfish("Lucy", "Pink")
-  let favourite_ice_cream = IceCream("strawberry")
+  handle_fish(Starfish("Lucy", "Pink"))
+  handle_ice_cream(IceCream("strawberry"))
+}
 
-  case lucy {
+fn handle_fish(fish: Fish) {
+  case fish {
     Starfish(_, favourite_color) -> io.debug(favourite_color)
     Jellyfish(name, ..) -> io.debug(name)
   }
+}
 
+fn handle_ice_cream(ice_cream: IceCream) {
   // if the custom type has a single variant you can
   // destructure it using `let` instead of a case expression!
-  let IceCream(flavour) = favourite_ice_cream
+  let IceCream(flavour) = ice_cream
   io.debug(flavour)
 }

src/content/chapter3_data_types/lesson04_record_pattern_matching/en.html

@@ -1,12 +1,15 @@
 <p>
-  It is possible to pattern match on a record, this allows for the extraction
-  of multiple field values from a record into distinct variables, similar to matching on a tuple or a list.
+  It is possible to pattern match on a record, this allows for the extraction of
+  multiple field values from a record into distinct variables, similar to
+  matching on a tuple or a list.
 </p>
 <p>
-  The <code>let</code> keyword can only match on single variant custom types. For types with more variants
-  a case expression must be used.
+  The <code>let</code> keyword can only match on single variant custom types, or
+  when the variant is know, such as after pattern matching with a case
+  expression.
 </p>
 <p>
-  It is possible to use underscore <code>_</code> or the spread syntax <code>..</code> to
-  discard fields that are not required.
-</p>
+  It is possible to use underscore <code>_</code> or the spread syntax
+  <code>..</code> to discard fields that are not required.
+</p>
+