update vi-first-steps.md

pages/vi/vi-first-steps.md

@@ -49,11 +49,17 @@ There are 3 sections in this step:
 
 1. [Vagrant Tutorial](vi-vagrant.md)
   **Vagrant** is an open-source software product for building and maintaining portable virtual software development environments. In this section, you will learn about how to interact with Vagrant through the command-line interface.
+
+* **Summary of Step 1:**
+    * By the end of this step, you should know how to set up your planet community on the command line/terminal, creating your planet learning account and learning about the different commands that will be used on the terminal for working with vagrant.
 
 ## Step 2 - Planet and Docker
 
 Follow the instructions on the [Docker Tutorial page](vi-docker-tutorial.md). **Docker** is a computer program that performs operating-system-level virtualization also known as containerization. In this section, you will learn the basics of interacting with Docker and Docker Compose through the command-line interface and basic commands for maintaining your Planet installation.
 
+* **Summary of Step 2:**
+    * In this step, you learn the different functionalities of Docker and how you can use it to manually install Planet and also the various commands that are a part of Docker.  
+
 ## Step 3 - Markdown and Fork Tutorial
 
 Follow the instructions on the [GitHub and Markdown page](vi-github-and-markdown.md). Make sure that you've linked to your github.io and your personal .md page on the [Gitter chat](https://gitter.im/open-learning-exchange/chat) (https://YourUserName.github.io and https://raw.githack.com/YourUserName/YourUserName.github.io/YourBranchName/#!pages/vi/profiles/YourUserName.md).
@@ -67,10 +73,16 @@ Follow the instructions on the [GitHub and Markdown page](vi-github-and-markdown
 
 This step includes the [Planet Tutorial](vi-planetapps.md), which explains the features of the application.
 
+* **Summary of Step 4:**
+    * In this step, you learn more about the planet community and all the different features that are included in them. You also get familiar with functions such as uploading resources to the community, updating your community, and taking a course. 
+
 ## Step 5 - Keeping Fork Updated
 
 Follow the directions at [Git Repositories](vi-github-and-repositories.md) to keep your username.github.io and your local repository up to date.
 
+* **Summary of Step 5:**
+    * In this step, you learn the difference between the different levels of heirarchy within GitHub and your local repository, how to create your own local repository, and syncing a fork. 
+
 ## Step 6 - GitHub Issues Tutorial
 
 Follow the tutorial under the [GitHub Issues tab](vi-github-issues.md) to create at least one issue. Post a link in [Gitter](https://gitter.im/open-learning-exchange/chat) whenever you create an issue or when you comment on someone else's issue. You are encouraged to post as many issues as you can for improving the page as well as for personal practice. No issue is too big or too small to be filed and it is OK if you are not sure how to fix it yourself. If you know how to solve an issue, be sure to provide a detailed account of your research and show how to fix it. It is ok to file an issue about minor typos and very small changes, but do not make this the case for all of the issues that you file. You can also work on issues that you didn't create.
@@ -86,6 +98,9 @@ Make sure you have created at least one issue, resolved it, commented on an issu
 
 Follow the directions under the [Nation Planet tab](vi-nation.md).
 
+* **Summary of Step 7:**
+    * In this step you learn about syncing your planet community with nation and also more on how to manage and checking the status of your syncs. 
+
 ## Step 8 - Create Issues and Pull Requests
 
 Create three more issues, add comments to three other issues, and resolve three issues by making the necessary changes in your repo with three separate pull requests. You should resolve three issues created by yourself, and make sure you mention in the issue you are working on, that you are in fact working on it. **Besides, you should make sure someone from the OLE team confirms to make the change that your issue has brought up before you start working on the issue.** You will follow the same steps as in [GitHub Issues](vi-github-issues.md), continuing to improve this Markdown Wiki so that it is educational, yet easy to understand for future interns.