standardize punctuation

Author: brianamarie

responses/02_find-vulnerabilities.md

@@ -28,11 +28,11 @@ Use GitHub's security alerts to identify a vulnerable NPM dependency.
 
 ### :keyboard: Activity: Identify the suggested version update
 
-1. Click the **Insights** tab in your repository
-2. On the left hand navigation bar, click **Dependency graph**
-3. Scroll down until you see a yellow bar highlighting the dependency named `debug`, and click on the right hand side of the yellow `debug` section
-4. Take note of the suggested version
-5. Comment in this issue with the suggested update version
+1. Click the **Insights** tab in your repository.
+2. On the left hand navigation bar, click **Dependency graph**.
+3. Scroll down until you see a yellow bar highlighting the dependency named `debug`, and click on the right hand side of the yellow `debug` section.
+4. Take note of the suggested version.
+5. Comment in this issue with the suggested update version.
 
 
 > _**GitHub Enterprise Server only:** This is all possible on GitHub Enterprise through GitHub Connect. It may take up to an hour to refresh the alerts and make them visible. After waiting a reasonable amount of time, if you are still not seeing the yellow bar in the Dependency Graph, you may want to contact your administrator. In the mean time, to move along with the course, we'll give you a hint - the recommended upgraded version is `2.6.9`._

responses/03_good-pr.md

@@ -5,4 +5,4 @@ Great job, @{{ user.username }}, your pull request looks good. Thank you for fix
 _Note: You might notice that this repository has a `package.json` file, but no `package-lock.json` file. We are doing all parts of this activity on GitHub.com. If you work with other repositories, you might notice some differences. Regardless of what dependency files you use, the main concepts of this course still apply._
 
 ### :keyboard: Activity: Merge
-1. Merge this pull request
+1. Merge this pull request.

responses/03_update-dependency.md

@@ -10,7 +10,7 @@ Now that you know the recommended version, it's time to edit the `package.json`
 
 ### :keyboard: Activity: Update the `package.json` file
 
-1. Within this pull request, go to **Files changed**
-1. Click the pencil in the right upper corner to edit the `package.json` file
-1. Fix the vulnerability by updating to the latest version of the dependency that you took note of earlier
-1. Scroll down, and commit your change
+1. Within this pull request, go to **Files changed**.
+1. Click the pencil in the right upper corner to edit the `package.json` file.
+1. Fix the vulnerability by updating to the latest version of the dependency that you took note of earlier.
+1. Scroll down, and commit your change.

responses/04b_add-gitignore.md

@@ -14,10 +14,10 @@ In this pull request, I'm adding a `.gitignore` file. Files ending with `.env` c
 
 ### :keyboard: Activity: Updating the .gitignore file
 
-1. Within this pull request, go to **Files changed**
-1. Click the pencil in the right upper corner to edit the `.gitignore` file
-1. Edit the file by adding `.env` to line 1
-1. Scroll down, and commit your change
+1. Within this pull request, go to **Files changed**.
+1. Click the pencil in the right upper corner to edit the `.gitignore` file.
+1. Edit the file by adding `.env` to line 1.
+1. Scroll down, and commit your change.
 
  > _Note: Even after adding a file to the `.gitignore`, the previous commits that have edited that file still exist. If you accidentally committed sensitive data, first change any tokens or passwords. Then, contact GitHub Support for help correcting your history._
 

responses/05_good-ignore.md

@@ -3,4 +3,4 @@
 This looks great @{{ user.username }}, thanks for adding a `.env` file to the `.gitignore`. Feel free to add any other file or potential sensitive data to the `.gitignore` file.
 
 ### :keyboard: Activity: Merge
-1. Merge this pull request
+1. Merge this pull request.