Added link to detailed section

README.md

@@ -16,7 +16,7 @@ Contributing corrections and edits is easy, and can be done directly on GitHub!
 1. On your fork's page, Locate the `.lproj` folder for your language. In there you will see two files: `FoodItems.strings` and `Localizable.strings`.
 2. Click on the `.strings` file you wish to edit to view its contents.
 3. To edit it, Click on the pencil icon in the upper right corner.
-4. Make your changes to the phrase on the right side of the `=`. See [How to edit and format `.strings` files](link) below for more information.
+4. Make your changes to the phrase on the right side of the `=`. See [How to edit and format `.strings` files](#how-to-edit-and-format-strings-files) below for more information.
 5. Commit any changes at the bottom of the screen, explaining what you changed. If you don't commit, your changes won't be saved!
 6. Submit a Pull Request so the changes can be reviewed. A button should be available on your fork's main page after you commit your changes.
 7. Enter a title and description, and click on the button to submit your pull request.
@@ -30,7 +30,7 @@ Contributing a new language is a bit more involved, but is very much appreciated
 3. Locate the `en.lproj` folder and duplicate it, renaming it to the language you are adding. Language codes can be found [here](https://www.ibabbleon.com/iOS-Language-Codes-ISO-639.html).
 	- For example, if you are adding Spanish, then rename the folder to `es.lproj`.
 	- If you are adding variations on Spanish as spoken in Mexico, then rename the folder to `es-MX.lproj`.
-4. You should edit all `.strings` files in your language's `.lproj` folder. You can refer back to the `en.lproj` folder and its contents if you need examples. See [How to edit and format `.strings` files](link) below for more information.
+4. You should edit all `.strings` files in your language's `.lproj` folder. You can refer back to the `en.lproj` folder and its contents if you need examples. See [How to edit and format `.strings` files](#how-to-edit-and-format-strings-files) below for more information.
 5. After saving your changes, use GitHub Desktop to commit those changes by providing a few words explaining what you changed in the Summary text field, then click the commit button underneath it.
 6. Click the Publish (Sometimes seen as Push) button at the top to push any changes back to GitHub.
 7. Click on Create Pull Request in GitHub Desktop, or from your fork's page (there should be a green highlighted section that appears) to submit a **Pull Request**.