Fix links

Ester · web-flow · commit 8a3487910da1 · 2019-02-23T16:38:34.000Z
diff --git a/README.md b/README.md
@@ -39,17 +39,17 @@ Made by @alesssia, @estramcar & @feiphoon.
 #### [Creating issues (everyone)](/workshop/03-creating-issues)
 6. Create an issue based on a question (from a provided list).
 
-#### [Responding to issues (everyone)](/workshop/04-making-commits)
+#### [Responding to issues (everyone)](/workshop/04-responding-to-issues)
 7. Pick an issue to resolve, by assigning it to yourself and leaving a nice comment telling others you'll own it.
 8. Create a branch to address your assigned issue.
 9. Create a folder and file (with path instructions)
 10. Commit your new file to your branch.
 
-#### [Asking for a review (everyone)](/workshop/05-making-commits)
+#### [Asking for a review (everyone)](/workshop/05-asking-for-a-review)
 11. Use compare on your own branch to look at your own changes, and open a pull request. Link to the issue in the pull request description.
 12. Catch-up point/timecheck (how many groups have at least one pull request open, 5min).
 
-#### [Reviewing changes (everyone)](/workshop/06-making-commits)
+#### [Reviewing changes (everyone)](/workshop/06-reviewing-changes)
 13. Look at the pull request you were assigned to review. View the file diff in the pull request to see what was changed.
 14. Make a comment on any line in the file in the pull request (submit it with "Add a single comment").
 15. Change to the pull request's branch and learn to find/navigate files.
