From 24838b70b05fedc6affaee338910e67d1eeb95bd Mon Sep 17 00:00:00 2001
From: Julie Kirsch <julie.kirsch@pt.lu>
Date: Tue, 10 Dec 2024 20:28:15 +0100
Subject: [PATCH] fixing figures

---
 book/features/custom-launch-button.md      | 2 +-
 book/workflows/github_dev.md               | 4 ----
 book/workflows/stage_commit_push_vscode.md | 7 +++++++
 book/workflows/user45_check_changes.md     | 2 +-
 4 files changed, 9 insertions(+), 6 deletions(-)

diff --git a/book/features/custom-launch-button.md b/book/features/custom-launch-button.md
index 8df830b..b935a7c 100644
--- a/book/features/custom-launch-button.md
+++ b/book/features/custom-launch-button.md
@@ -96,7 +96,7 @@ The code in the above cell is the `_launch_buttons.yml` file of a repository cal
 ```{figure} figures/language_button.PNG
 ---
 width: 50%
-name:language_button
+name: language_button
 ---
 Custom Button
 ```
diff --git a/book/workflows/github_dev.md b/book/workflows/github_dev.md
index 92933f7..60f8d9d 100644
--- a/book/workflows/github_dev.md
+++ b/book/workflows/github_dev.md
@@ -5,7 +5,6 @@
 
 ```{figure} figures/Online_VS0.PNG
 ---
-name: New File
 width: 50%
 align: center
 ---
@@ -16,7 +15,6 @@ New File
 
 ```{figure} figures/Online_VS1.PNG
 ---
-name: VS Code in Browser
 width: 70%
 align: center
 ---
@@ -29,7 +27,6 @@ In the bottom left you can see the branch you are working in.
 
 ```{figure} figures/Online_VS2.PNG
 ---
-name: GitHub Actions
 width: 70%
 align: center
 ---
@@ -39,7 +36,6 @@ You will see the latest commit you just did (in this case text). After the pipel
 
 ```{figure} figures/Online_VS3.PNG
 ---
-name: Deployed Branches
 width: 60%
 align: center
 ---
diff --git a/book/workflows/stage_commit_push_vscode.md b/book/workflows/stage_commit_push_vscode.md
index d917fa9..0bf888e 100644
--- a/book/workflows/stage_commit_push_vscode.md
+++ b/book/workflows/stage_commit_push_vscode.md
@@ -3,6 +3,8 @@
 For demonstration purposes, we have created a new Markdown file called `new-chapter.md`, which we want to add to the book. Since this is a new file, Git has no knowledge about its existence yet. I.e., the file is *untracked*. To add new files to our repository, we need to *stage* and *commit* them. To do this, open the Source Control menu in the left side bar. Our new file should appear in this menu:
 
 ```{figure} ../images/git-new-file.png
+---
+width: 100%
 
 ---
 The new file appears in the Source Control menu.
@@ -14,6 +16,8 @@ Notice that there is a green letter U placed besides the file, meaning that our
 Next, in the field that says "Message", write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, the menu should now look something like this:
 
 ```{figure} ../images/git-file-added.png
+---
+width: 100%
 
 ---
 The new file has been staged, and we've written a Commit Message.
@@ -26,6 +30,9 @@ Now, we are ready to add the changes to the repository. This is done by *committ
 In the bottom left corner, next to the branch name, click the "Synchronize Changes" button (the one that looks like this: 🔄, highlighted in the image below) to push the changes to GitLab/GitHub.
 
 ```{figure} ../images/git-push.png
+---
+width: 100%
+
 ---
 After committing, click the 🔄 button to push our changes to the remote repository.
 ```
\ No newline at end of file
diff --git a/book/workflows/user45_check_changes.md b/book/workflows/user45_check_changes.md
index 4b2377c..bd8b79d 100644
--- a/book/workflows/user45_check_changes.md
+++ b/book/workflows/user45_check_changes.md
@@ -25,7 +25,7 @@ Note: use `--all` for the jupyter-book whenever building a book to make sure the
 Where book is the name of the folder containing all the files that make up your book. After `teachbooks` is done running you will get the following:
 
 ```{figure} ../figures/buildbook.PNG
----
+
 Output
 ```
 Paste the last line into your browser to see the updated changes.