diff --git a/common-content/en/module/induction/working-locally/index.md b/common-content/en/module/induction/working-locally/index.md
index 05c7b8481..55e7151a5 100644
--- a/common-content/en/module/induction/working-locally/index.md
+++ b/common-content/en/module/induction/working-locally/index.md
@@ -12,53 +12,53 @@ time ="20"
 
 +++
 
-Here is a diagram representing how the repositories interact after forking and cloning:
+GitHub is an really useful tool for aiding collaboration, but when it comes to writing and updating the code for a project, we tend to want the flexibility that comes with working on our {{<tooltip title="local machines">}}A **machine** in this context is any computer, and your **local machine** is the computer (laptop or desktop) on which you do your work.{{</tooltip>}}. So we need to address the following question:
+
+> How can we get a copy of an existing GitHub repository on our local machine?
+
+In other words, we need to get a {{<tooltip title="local copy">}}A repository on GitHub is said to be **remote**. A repository on our own computer is said to be **local**.{{</tooltip>}} of the repository which is on GitHub.
+
+We call a local copy of a GitHub repository a **clone**. The process of copying a remote repository on to a local machine is called **cloning**. Watch the video below to see instructions on one of the ways you can clone a repo: using the Visual Studio Code interface.
+
+{{<youtube>}}https://www.youtube.com/watch?v=ILJ4dfOL7zs{{</youtube>}}
+
+{{<note type="exercise" title="Exercise">}}
+
+##### 🐑 Clone a Repo
+
+Follow the steps in the above video to make a local copy of the education blog repo that you forked in the previous step.
+
+##### Reminders:
+
+- Use the URL for **your fork** of the `education-blog` repo when you are cloning, not the URL for the original CYF repo
+- When selecting the location to clone your files, choose the `CYF` folder you created in an earlier task
+- If you are working on a library computer, you won't be able to clone the repo so come to class to try cloning out. In the meantime, you can explore the files using dot dev in the same way as you would in Visual Studio Code
+
+{{</note>}}
+
+For a visual reference, here is a diagram representing how the repositories interact after forking and cloning:
 
 ```mermaid
 flowchart TD
     subgraph Remote["Remote (GitHub)"]
         A["CodeYourFuture/education-blog"] -->|fork| B["EagerLearner/education-blog"]
     end
-    
+
     B -->|clone| C
-    
+
     subgraph Local["Local (your computer)"]
         C["YOUR_CYF_FOLDER/education-blog"]
     end
-    
+
     %% Style definitions
     classDef container stroke-dasharray:5 5,fill:#f8f9fa,stroke:#495057
     classDef rounded rx:10,ry:10,fill:#e9ecef,stroke:#495057
     classDef arrow color:#0d6efd,stroke-width:2px
-    
+
     %% Apply styles
     class Remote,Local container
     class A,B,C rounded
     linkStyle 0,1 stroke:#0d6efd,stroke-width:2px
 ```
 
-Sketch this diagram in your notebook. When you inevitably get mixed lost about where your changes are, you can refer back to this diagram to help you understand what's happening.
-
-> [!NOTE]
-> If you're working on a library computer, just fork the repo to your own GitHub account. You can't clone a repo on a library computer, so come to class to try cloning out. You can explore the files using dot dev in the same way as you would in Visual Studio Code.
-
-We can also use Git on our local machine to perform similar tasks as we do on GitHub. So we need to address the following question:
-
-> How can we get a copy of an existing GitHub repository on our local machine?
-
-In other words, we need to get a {{<tooltip title="local copy">}}A repository on GitHub is said to be **remote**. A repository on our own computer is said to be **local**.{{</tooltip>}} of the repository which is on GitHub.
-
-We call a local copy of a GitHub repository a **clone**. The process of copying a remote repository on to a local machine is called **cloning**.
-
-### 🎯 Goal: Clone a remote repository to your local machine
-
-You'll need to clone **your fork** of the education blog repo. Follow through the steps in the video "How to clone a repository from GitHub to Visual Studio Code".
-
-{{<youtube>}}https://www.youtube.com/watch?v=ILJ4dfOL7zs{{</youtube>}}
-
-<hr>
-
-##### 🎗️ Reminder:
-
-- Use the URL for your fork of the `education-blog` repo when you are cloning
-- When selecting the location to clone your files, choose the `CYF` folder you created in the [module prep](/user-data/prep/#create-cyf-folder)
+Sketch this diagram in your notebook. When you inevitably get mixed up or lost about where your changes are, you can refer back to this diagram to help you understand what's happening.
diff --git a/common-theme/assets/styles/04-components/block.scss b/common-theme/assets/styles/04-components/block.scss
index e5e603589..997a7d326 100644
--- a/common-theme/assets/styles/04-components/block.scss
+++ b/common-theme/assets/styles/04-components/block.scss
@@ -50,6 +50,7 @@ ul.c-block, ol.c-block, li.c-block {
     padding: 0;
     border: 0;
     box-shadow: none;
+    margin: var(--theme-spacing--2) 0;
   }
 
   &--pullreq {