From 80a340e4649bff9aff4466fbd61a076a04624e4c Mon Sep 17 00:00:00 2001
From: Lars Kappert <lars@webpro.nl>
Date: Fri, 26 Apr 2024 15:19:15 +0200
Subject: Increase consistency and readability a tiny bit

---
 src/content/chapter0_basics/lesson03_unqualified_imports/en.html | 6 +++---
 src/content/chapter0_basics/lesson14_type_imports/en.html        | 2 +-
 src/content/chapter0_basics/lesson15_type_aliases/en.html        | 2 +-
 src/content/chapter0_basics/lesson17_lists/en.html               | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

(limited to 'src/content/chapter0_basics')

diff --git a/src/content/chapter0_basics/lesson03_unqualified_imports/en.html b/src/content/chapter0_basics/lesson03_unqualified_imports/en.html
index 35ea10f..3f15f58 100644
--- a/src/content/chapter0_basics/lesson03_unqualified_imports/en.html
+++ b/src/content/chapter0_basics/lesson03_unqualified_imports/en.html
@@ -7,11 +7,11 @@
   </a>.
 </p>
 <p>
-  It is also possible to specify a list of functions to import from a module in
+  it's also possible to specify a list of functions to import from a module in
   an <em>unqualified</em> fashion, meaning the function name can be used without
   the module <em>qualifier</em> (the name and the dot) before it.
 </p>
 <p>
-  Generally it is best to use qualified imports, as this makes it clear where
-  the function is defined, making the code easier to read.
+  Generally it's best to use qualified imports, as this makes it clear where the
+  function is defined, making the code easier to read.
 </p>
diff --git a/src/content/chapter0_basics/lesson14_type_imports/en.html b/src/content/chapter0_basics/lesson14_type_imports/en.html
index 0f362e5..243bd61 100644
--- a/src/content/chapter0_basics/lesson14_type_imports/en.html
+++ b/src/content/chapter0_basics/lesson14_type_imports/en.html
@@ -17,6 +17,6 @@
   the import statement with the word <code>type</code> before the type name.
 </p>
 <p>
-  It is more common in Gleam code for types to be imported in an unqualified way
+  It's more common in Gleam code for types to be imported in an unqualified way
   than it is for functions to be imported in an unqualified way.
 </p>
diff --git a/src/content/chapter0_basics/lesson15_type_aliases/en.html b/src/content/chapter0_basics/lesson15_type_aliases/en.html
index 9fddd70..9d5cef9 100644
--- a/src/content/chapter0_basics/lesson15_type_aliases/en.html
+++ b/src/content/chapter0_basics/lesson15_type_aliases/en.html
@@ -1,6 +1,6 @@
 <p>
   A type alias can be used to refer to a type by a different name. Giving a type
-  an alias doesn't make a new type, it is still the same type.
+  an alias doesn't make a new type, it's still the same type.
 </p>
 <p>
   A type's name always starts with a capital letter, contrasting to variables
diff --git a/src/content/chapter0_basics/lesson17_lists/en.html b/src/content/chapter0_basics/lesson17_lists/en.html
index 84f88f3..5db7c11 100644
--- a/src/content/chapter0_basics/lesson17_lists/en.html
+++ b/src/content/chapter0_basics/lesson17_lists/en.html
@@ -15,7 +15,7 @@
 </p>
 <p>
   Counting the length of a list or getting elements from other positions in the
-  list is expensive and rarely done. It is rare to write algorithms that index
+  list is expensive and rarely done. It's rare to write algorithms that index
   into sequences in Gleam, but when they are written a list is not the right
   choice of data structure.
 </p>
-- 
cgit v1.2.3