Fix some typos

Author: ocaisa

docs/eessi-in-ci.md

@@ -12,9 +12,11 @@
 into a shared repository. Each time code is added or updated, automated processes build the application and run tests
 to verify that everything still works correctly. This verification workflow is exactly the process we went through in
 the last episode:
+
 * Prepare the environment
 * Build the application
 * Make sure it works
+
 CI is about automating that workflow to ensure it is carried out whenever we make changes to our
 application...and letting us know when things go wrong!
 
@@ -271,9 +273,9 @@ will become a green tick which indicates that our CI for the commit has passed.
 
 ??? note "What would have our CI looked like in GitLab?"
 
-    There are not so many real differences with how our specific CI would have looked like in CI/CD. The core steps
-    that we need to run are the same, but the structure to get to them is different. Again an LLM is of major
-    assistance when creating our CI file.
+    There are not so many real differences with how our specific CI would have looked like in GitLab CI/CD. The core
+    steps that we need to run are the same, but the structure to get to them is different. Again an LLM is of major
+    assistance when creating our CI file for GitLab.
 
     One major practical difference is where the CI file is stored and what it is called. In the case of GitLab CI/CD,
     the workflow must be stored in a file called

docs/eessi-use-cases.md

@@ -18,7 +18,7 @@ These use cases are discussed in details in our open-access paper, available via
 
 In the rest of this tutorial we will explore aspects of these use cases:
 
-* Using EESSI as base layer for software, and installing additional software on top of EESSI using `EESSI-extend`
+* Using EESSI as base layer for software, and installing additional software on top of EESSI with and without `EESSI-extend`
 * Building user applications with EESSI, and using EESSI in Continuous Integration (CI) environments with GitHub Actions or GitLab CI
 * Discuss some advanced topics including MPI applications, GPU applications, and using other tools (such as Spack) on top of EESSI