diff --git a/1.png b/1.png
new file mode 100644
index 00000000..82414edb
Binary files /dev/null and b/1.png differ
diff --git a/2.png b/2.png
new file mode 100644
index 00000000..16047820
Binary files /dev/null and b/2.png differ
diff --git a/3.png b/3.png
new file mode 100644
index 00000000..3d0a9ca9
Binary files /dev/null and b/3.png differ
diff --git a/4.png b/4.png
new file mode 100644
index 00000000..eb0c3d3e
Binary files /dev/null and b/4.png differ
diff --git a/README.md b/README.md
index 985c7e33..927000e8 100644
--- a/README.md
+++ b/README.md
@@ -237,7 +237,7 @@ These are the default shortcuts. See `man foot.ini` and the example
   under the pointer up to, and until, the next space characters.
 
 <kbd>left</kbd> - **triple-click**
-: Selects the everything between enclosing quotes, or the entire row
+: Selects everything between enclosing quotes, or the entire row
   if not inside a quote.
 
 <kbd>left</kbd> - **quad-click**
@@ -416,7 +416,7 @@ to XTerm's `metaSendsEscape` option set to `true`.
 This can be disabled programmatically with `\E[?1036l` (and enabled
 again with `\E[?1036h`).
 
-When disabled, foot will instead set the 8:th bit of meta character
+When disabled, foot will instead set the 8th bit of meta character
 and then UTF-8 encode it. This corresponds to XTerm's `eightBitMeta`
 option set to `true`.
 
@@ -486,7 +486,7 @@ are expected to behave, foot >= 1.15 will default to scaling fonts
 using the compositor's scaling factor, and **not** the monitor
 DPI.
 
-This means the (assuming the monitors are at the same viewing
+This means that (assuming the monitors are at the same viewing
 distance) the font size will appear to change when you move the foot
 window across different monitors, **unless** you have configured the
 monitors' scaling factors correctly in the compositor.
diff --git a/report_ex2.md b/report_ex2.md
new file mode 100644
index 00000000..74f99bb8
--- /dev/null
+++ b/report_ex2.md
@@ -0,0 +1,11 @@
+##Exercise 2: Forking
+![-](1.png)
+![-](2.png)
+![-](3.png)
+![-](4.png)
+Regularly syncing a fork with upstream is crucial to ensure your local copy doesn't fall behind the original project. This prevents complex merge conflicts and ensures that any new features you develop are built on top of the most current version of the code.
+
+#3
+origin	https://codeberg.org/faxilion/foot.git (fetch)
+origin	https://codeberg.org/faxilion/foot.git (push)
+