Merge pull request #103 from openaps/bewest-fix-links

Bewest fix links

source/docs/introduction/contribute.md

@@ -4,7 +4,7 @@ OpenAPS doesn't require you to be a formally trained engineer/developer/anything
 
 If you're not sure where to get started, here are some ways to get involved:
 
-* Do a fresh install using this guide and see where you get stuck; if you have to do something off-script, there is a reasonable chance the script is either wrong or your case is "special" and should be accounted for here. [Make edits and submit a pull request](docs/Resources/my-first-pr.md) to change the document and assist others.
+* Do a fresh install using this guide and see where you get stuck; if you have to do something off-script, there is a reasonable chance the script is either wrong or your case is "special" and should be accounted for here. [Make edits and submit a pull request](../Resources/my-first-pr.md) to change the document and assist others.
 * Additionally, this guide needs more work, always. If there is something that is not documented, do one of two things: a) submit a pull request (see above). or b) log an "issue" ([go here to see the open issues](https://github.com/openaps/docs/issues)) about the section or thing that needs more documentation.
 * Ask questions on [gitter]( https://gitter.im/nightscout/intend-to-bolus); if your question wasn't answered in this doc and gets answered there, chances are it should be included here—go ahead and add it to the appropriate section.
 * Test the openaps tools for different use cases and report back with your findings. Logs files and, if you're comfortable, associated device data (CareLink CSV files, for example) are extremely helpful for debugging.

source/docs/introduction/conventions.md

@@ -9,6 +9,6 @@ Some conventions used in this guide:
 * Wherever there are `<bracketed_components>` in the the code, these are meant for you to insert your own information. Most of the time, it doesn't matter what you choose **as long as you stay consistent throughout this guide**. That means if you choose `Barney` as your  `<my_pump_name>`, you must use `Barney` every time you see `<my_pump_name>`. Choose carefully. Do not include the `< >` brackets in your name.
 
 
-Some familiarity with using the terminal will go a long way, so if you aren't comfortable with what `cd` and `ls` do, take a look at some of the Linux Shell / Terminal commands on the [Troubleshooting](docs/Resources/troubleshooting.md) page and the reference links on the [Technical Resources](../Resources/technical-resources.md) page.
+Some familiarity with using the terminal will go a long way, so if you aren't comfortable with what `cd` and `ls` do, take a look at some of the Linux Shell / Terminal commands on the [Troubleshooting](../Resources/troubleshooting.md) page and the reference links on the [Technical Resources](../Resources/technical-resources.md) page.
 
 One helpful thing to do before starting any software work is to log your terminal session. This will allow you to go back and see what you did at a later date. This will also be immensely helpful if you request help from other OpenAPS contributors as you will be able to provide an entire history of the commands you used. To enable this, just run `$ script <filename>` at the beginning of your session. It will inform you that `Script started, file is <filename>`. When you are done, simply `$ exit` and it will announce `Script done, file is <filename>`. At that point, you can review the file as necessary.