From 91bc8ca296d1d5c10122ce5cc5e96905145902a2 Mon Sep 17 00:00:00 2001
From: 2c4f8a60907bbc0eda50d04c61d31fba
 <2c4f8a60907bbc0eda50d04c61d31fba@app-learninglab.inria.fr>
Date: Fri, 13 Jun 2025 14:06:28 +0000
Subject: [PATCH] Update Gackowski_logbook

---
 journal/Gackowski_logbook | 33 ++++++++++++++++++++++-----------
 1 file changed, 22 insertions(+), 11 deletions(-)

diff --git a/journal/Gackowski_logbook b/journal/Gackowski_logbook
index 587aa8c..eabf3cd 100644
--- a/journal/Gackowski_logbook
+++ b/journal/Gackowski_logbook
@@ -2,10 +2,14 @@
 
 ## Exercise 01-1 – GitLab Search and Git History
 
-- I explored how to search for information located inside a specific file using the search function at the top right corner of GitLab ("Search or jump to...").
-- After typing a specific keyword, I was able to locate documents containing that phrase.
-- In the second part of the exercise, I found the file `module1/exo2/readme.md` using the **Find file** search tool.
-- Using the **Blame** function, I tracked the change that introduced the title “Helloworld Python”.
+- I explored how to search for information located inside a specific file using 
+the search function at the top right corner of GitLab ("Search or jump to...").
+- After typing a specific keyword, I was able to locate documents containing 
+that phrase.
+- In the second part of the exercise, I found the file `module1/exo2/readme.md` 
+using the **Find file** search tool.
+- Using the **Blame** function, I tracked the change that introduced the title 
+“Helloworld Python”.
 - This change was made by **Arnaud Legrand**, with the commit hash: `505c4e26`.
 - The information was successfully located and identified as correct.
 
@@ -14,14 +18,19 @@
 ### Part A: Creating the Markdown File
 
 - I accessed my personal GitLab space.
-- Created a new directory named `exo2` using the `+` button and selecting **New directory**.
-- Inside this directory, I created a new file named `fichier-markdown.md` using **New file**.
-- I followed the instructions from the PDF *"Introduction to Markdown"* and typed the content accordingly:
+- Created a new directory named `exo2` using the `+` button and selecting 
+**New directory**.
+- Inside this directory, I created a new file named `fichier-markdown.md` 
+using **New file**.
+- I followed the instructions from the PDF *"Introduction to Markdown"* and 
+typed the content accordingly:
   - Used `#` to create titles and headings.
   - Used `*italic*`, `**bold**` for text formatting.
   - Used `-` for unordered lists, and `1.` for ordered lists.
-  - Used backticks and syntax highlighting (e.g., ```python```) to include code blocks.
-- I saved the file with the name `fichier-markdown.md` and added a **Commit message**: `commit changes`.
+  - Used backticks and syntax highlighting (e.g., ```python```) to include 
+  code blocks.
+- I saved the file with the name `fichier-markdown.md` and added a 
+**Commit message**: `commit changes`.
 
 ### Part B: Comparing With the Solution
 
@@ -32,9 +41,11 @@
 
 ## Exercise 01-3 – Writing the Logbook
 
-- I documented all steps taken during the session, including search methods, file creation, and use of markdown syntax.
+- I documented all steps taken during the session, including search methods, 
+file creation, and use of markdown syntax.
 - I now better understand how to structure and format a Markdown file.
-- I improved my ability to navigate GitLab, especially using tools like **Blame**, **Find file**, and making commits.
+- I improved my ability to navigate GitLab, especially using tools like 
+**Blame**, **Find file**, and making commits.
 
 ---
 
-- 
2.18.1