Skip to content

Commit dc5e004

Browse files
Merge pull request #83 from nmstreethran/proposed-changes
added my name to the list; fixed a couple of typos
2 parents 003e80a + cfd483e commit dc5e004

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

content_development/Task_3.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@ Select the `README` file in the Git window, which should show up automatically i
227227

228228
Here, you have a chance to review your changes, and write a nice commit message. Type in something brief, but informative about the changes that you have made in this version or snapshot of your work. You want this to be enough information so that if you or someone else looks back on it, you'll know why you made this commit and the changes associated with it. These are like safety nets for your project in case you need to fall back for some reason.
229229

230-
> **Pro-tip**: Here, you will see a list of all the changes you have made since your last commit. Older removed lines are in red, and newly added lines are in green. Double check these to make sure that the edits you have made are the ones you intended to make. This is really helpful for spotting typos, stray edits, and any other little mistakes you might have accidentially introduced. Safety first.
230+
> **Pro-tip**: Here, you will see a list of all the changes you have made since your last commit. Older removed lines are in red, and newly added lines are in green. Double check these to make sure that the edits you have made are the ones you intended to make. This is really helpful for spotting typos, stray edits, and any other little mistakes you might have accidentally introduced. Safety first.
231231
232232
**Note** If you are colour-blind and can't see which lines have been added or removed, you can use the line numbers in the two columns on the left of the window as a guide. Here, the number in the first column identifies the older version, and the number in the second column identifies the new version.
233233

@@ -254,7 +254,7 @@ Close that window down, and the next one. Go to your project on GitHub, refresh,
254254

255255
Alright, so you just pushed some content to your first repo, awesome! Now let's put it into practice for a real project. Like, the one you are participating in right now. Let's try this out:
256256

257-
1. Go to the repositors for this project on [GitHub](https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source)
257+
1. Go to the repository for this project on [GitHub](https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source)
258258

259259
2. Fork the repository to your own GitHub account. The URL for this should be: `https://github.com/OpenScienceMOOC/Module-5-Open-Research-Software-and-Open-Source.git`
260260

@@ -320,5 +320,6 @@ Time to take your new GitHub skills for a test-run! All content development prim
320320
* Harin Lee, Goldsmiths, University of London
321321
* Luis Camacho, Catholic University, Perú
322322
* Tom Cridford, Imperial College London
323+
* Nithiya Streethran, University of Stavanger
323324

324325
[![CC0 Public Domain Dedication](https://img.shields.io/badge/License-CC0%201.0-lightgrey.svg)](https://creativecommons.org/publicdomain/zero/1.0/)

0 commit comments

Comments
 (0)