diff --git a/README.md b/README.md
index 5256046..1843ea0 100644
--- a/README.md
+++ b/README.md
@@ -94,10 +94,10 @@ You can check out the GitHub Explore website [at github.com/explore](https://git
 ## Tasks 
 
 * Fork (copy) this repository under your personal GitHub account by clicking the green `<> Code` button
-  * Invite your mentor or someone in the tech team as a [collaborator](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository) — ask them for their GitHub username if you don't know it
-  * Create a new branch in your fork and and create a new Markdown file. Share what you've learned and what you're still confused about. Experiment with different styles!
-  * Open a pull request and add your mentor as a [reviewer](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) (**note:** they must first accept your collaboration request to be available as a reviewer).  
-* Create your profile README. Let the world know a little bit more about you! What are you interested in learning? What are you working on? What's your favorite hobby? Learn more about creating your profile README in the document, ["Managing Your Profile README"](https://docs.github.com/en/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme).
+  * Invite your mentor or someone in the tech team as a [collaborator](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository) — ask them for their GitHub username if you don't know it ✅
+  * Create a new branch in your fork and and create a new Markdown file. Share what you've learned and what you're still confused about. Experiment with different styles! ✅
+  * Open a pull request and add your mentor as a [reviewer](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) (**note:** they must first accept your collaboration request to be available as a reviewer).  ✅
+* Create your profile README. Let the world know a little bit more about you! What are you interested in learning? What are you working on? What's your favorite hobby? Learn more about creating your profile README in the document, ["Managing Your Profile README"](https://docs.github.com/en/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme). ✅
 * Go to your user dashboard and create a new repository. Experiment with the features within that repository to familiarize yourself with them. 
 * [Let us know what you liked or didn’t like about the content of this course](https://support.github.com/contact/education). What would you like to see more of? What would be interesting or helpful to your learning journey? 
 
diff --git a/github-fundamentals b/github-fundamentals
new file mode 160000
index 0000000..595a0f7
--- /dev/null
+++ b/github-fundamentals
@@ -0,0 +1 @@
+Subproject commit 595a0f7c25db217eebebcdba430205240b5f11fd
diff --git a/markdown.md b/markdown.md
new file mode 100644
index 0000000..c413ce9
--- /dev/null
+++ b/markdown.md
@@ -0,0 +1,10 @@
+# Create a new branch in your fork and and create a new Markdown file. Share what you've learned
+
+I learnt how to fork a repository from git and create a new branch + file within this. 
+
+# what you're still confused about. 
+
+nothing.
+
+new changes added.
+additional changes.
\ No newline at end of file