Merge branch 'kc-gitober23-p1' into 'develop'

gitober23 image update

See merge request R3/school/courses!185

2023/2023-10-03_gitober-part1/slides/commit.md

@@ -17,7 +17,7 @@
 <div class="fragment">
 Gitlab:
 <div style="position:absolute">
-<img src="slides/img/commit_GUI_1.png" class="as-is" height="350px"/>
+<img src="slides/img/commit_GUI_1.png" class="as-is" height="250px"/>
 </div>
 </div>
 

2023/2023-10-03_gitober-part1/slides/merge.md

@@ -49,13 +49,13 @@ After *Committing*, the *Create MR* button redirects you to the submission page
 ![bulb](slides/img/bulb.png) Good practice is to select *Delete source branch when merge request is accepted*. Why?
 
 <div style="position:absolute;left:30%;top:1em" class="fragment fade-in-then-out" data-fragment-index="0">
-<img src="slides/img/merge-request_popup.png" width="50%" >
+<img src="slides/img/merge-request_popup.png" width="60%" >
 </div>
 
-<div style="position:absolute;left:30%;top:1em" class="fragment fade-in-then-out" data-fragment-index="3">
-<img src="slides/img/merge-request_branches.png" width="50%" >
+<div style="position:absolute;left:30%;top:10em" class="fragment fade-in-then-out" data-fragment-index="3">
+<img src="slides/img/merge-request_branches.png" width="60%" >
 </div>
 
 <div style="position:absolute;left:20%;top:20em" class="fragment fade-in-then-out" data-fragment-index="5">
-<img src="slides/img/merge-request_delete-source.png" width="50%" >
+<img src="slides/img/merge-request_delete-source.png" width="70%" >
 </div>

2023/2023-10-03_gitober-part1/slides/versioning.md

@@ -6,7 +6,7 @@ Basic features:
 * Ability to recover previous versions
 * Track all changes to a document or code
 
-<div style="position:absolute; left:50%">
+<div style="position:absolute;left:60%;top:1em">
 <img src="slides/img/version-history_OneDrive.png" height="650px">
 </div>