diff --git a/book/workflows/branches.md b/book/workflows/branches.md
index 4be0eaf..a8ce8d6 100644
--- a/book/workflows/branches.md
+++ b/book/workflows/branches.md
@@ -83,6 +83,7 @@ name: Clone_GitHub
 Clone using SSH
 ```
 
+``````
 ``````{tab-item} ... GitHub through GitHub Desktop
 
 1. Open the repository that you would like to clone. In the top bar on the right, you will a green button called `<> Code`.
diff --git a/book/workflows/edit_book.md b/book/workflows/edit_book.md
index 0dd2e75..b9ae50d 100644
--- a/book/workflows/edit_book.md
+++ b/book/workflows/edit_book.md
@@ -197,17 +197,11 @@ After committing, click the 🔄 button to push our changes to the remote reposi
 
 3. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`.
 
-4. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, the following screen will pop up. Click on `Push Origin`.
+4. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing,  click on `Push origin` in the top bar. 
 
 <figure align="center">
     <img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650">
 </figure>
-
-Alternatively, you can also click on `Push origin` in the top bar. 
-
-<figure align="center">
-    <img src="figures/Push_GitHubDesktop2.PNG" alt="Example Image" width="650">
-</figure>
 ````
 `````
 ``````
@@ -313,18 +307,12 @@ Choose one of the options to resolve the merge conflict. You now have updated yo
 
 5. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`.
 
-6. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, the following screen will pop up. Click on `Push Origin`.
+6. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, click on `Push origin` in the top bar. 
 
 <figure align="center">
     <img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650">
 </figure>
 
-Alternatively, you can also click on `Push origin` in the top bar. 
-
-<figure align="center">
-    <img src="figures/Push_GitHubDesktop2.PNG" alt="Example Image" width="650">
-</figure>
-
 ````
 ````{tab-item} ... using 'VS Code in your browser'
 
@@ -686,16 +674,10 @@ If your book includes interactive element a webserver is required to host the bo
 
 6. Add changes to Git-timeline locally (committing). In the field that says `Summary(Required)`, write a short description of the changes you have made. This message is what is called the *Commit Message*. After we've done this, click the blue button `Commit to repository`.
 
-7. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, the following screen will pop up. Click on `Push Origin`.
+7. Now we need to add changes to GitHub/GitLab. This is called pushing to the local repository. After committing, click on `Push origin` in the top bar. 
 
 <figure align="center">
     <img src="figures/Push_GitHubDesktop.PNG" alt="Example Image" width="650">
-</figure>
-
-Alternatively, you can also click on `Push origin` in the top bar. 
-
-<figure align="center">
-    <img src="figures/Push_GitHubDesktop2.PNG" alt="Example Image" width="650">
 </figure>   
 ````
 ````{tab-item} ... using 'VS Code in your browser'