escape refs

Author: cgundogan

RIOT/README.md

@@ -1,12 +1,13 @@
 # RIOT - README
 
 This folder contains several exercises and tasks to get familiar with RIOT, the
-friendly operating system for the Internet of Things (IoT) [1], [2]. RIOT is an
+friendly operating system for the Internet of Things (IoT) \[1\], \[2\]. RIOT is an
 open source project and aims to foster usage of open standards, technologies
 and protocols in the IoT.
 
 The exercises are grouped into folders each covering a certain topic. Not all
 tasks start from scratch, thus they may rely on or reference other tasks.
 
-[1]: http://www.riot-os.org/
-[2]: https://github.com/RIOT-OS/RIOT
+\[1\] [http://www.riot-os.org/](http://www.riot-os.org/)
+
+\[2\] [https://github.com/RIOT-OS/RIOT](https://github.com/RIOT-OS/RIOT)

RIOT/coap/01_coap_server.md

@@ -6,8 +6,8 @@
 ## Description
 
 The objective of this exercise is to implement a simple CoAP server in RIOT.
-CoAP [1] is a HTTP like protocol for constraint network and nodes that allows
-to implement RESTful services [2].
+CoAP \[1\] is a HTTP like protocol for constraint network and nodes that allows
+to implement RESTful services \[2\].
 
 ## Instructions
 
@@ -17,13 +17,15 @@ to implement RESTful services [2].
     - `info/mcu` returns the RIOT MCU name
 3. The tool should print all unicast IPv6 addresses during start.
 4. Compile and start the tool using RIOT native and a tap interface
-5. Use the libcoap client [3] to discover the resources via `.well-known/core`
+5. Use the libcoap client \[3\] to discover the resources via `.well-known/core`
    and retrieve available resources; use one of the IPs output, see above.
 
 Document _all_ your actions and findings. Create an archive with your solution.
 
 ## References
 
-[1]: http://coap.technology/
-[2]: https://en.wikipedia.org/wiki/Representational_state_transfer
-[3]: https://libcoap.net/
+\[1\] [http://coap.technology/](http://coap.technology/)
+
+\[2\] [https://en.wikipedia.org/wiki/Representational_state_transfer](https://en.wikipedia.org/wiki/Representational_state_transfer)
+
+\[3\] [https://libcoap.net/](https://libcoap.net/)

RIOT/coap/02_coap_json_server.md

@@ -10,8 +10,8 @@ JSON as content formats. It extends on the previous task.
 
 ## Instructions
 
-1. Extend the simple CoAP server, implemented as described in [1].
-2. Change the content format of all resources to JSON, use the jsmn package [2].
+1. Extend the simple CoAP server, implemented as described in \[1\].
+2. Change the content format of all resources to JSON, use the jsmn package \[2\].
 3. Create a 3rd resource `print/` that handles CoAP PUT messages and outputs the
    packet content. Packet content format should be JSON: `{ 'msg': '<text>'}`,
    `<text>` should be printed.
@@ -21,5 +21,6 @@ Document _all_ your actions and findings. Create an archive with your solution.
 
 ## References
 
-[1]: https://github.com/smartuni/exercises/RIOT/coap/01_coap_server.md
-[2]: https://github.com/zserge/jsmn
+\[1\]: [https://github.com/RIOT-OS/Exercises/blob/master/RIOT/coap/01_coap_server.md](https://github.com/RIOT-OS/Exercises/blob/master/RIOT/coap/01_coap_server.md)
+
+\[2\]: [https://github.com/zserge/jsmn](https://github.com/zserge/jsmn)

RIOT/documentation/01_tests.md

@@ -6,16 +6,16 @@
 ## Description
 
 The objective of this exercise is to extend existing documentation or add new
-documentation to the tests in
-[RIOT/tests/](https://github.com/RIOT-OS/RIOT/tree/master/tests) in form of
-`README.md` files.
+documentation to the tests in RIOT/tests/ \[1\] in form of `README.md` files.
 
 ## Instructions
 
 1. Inspect current `README.md` files in `RIOT/tests`
 2. If a test does not contain a `README.md`, then this could be a good candidate
 3. Pick a `README.md` that contains vague descriptions and enhance it
-4. Provide a Pull Request to the official
-   [RIOT](https://github.com/RIOT-OS/RIOT) repository.
+4. Provide a Pull Request to the official RIOT \[2\] repository.
 
 ## References
+\[1\] [https://github.com/RIOT-OS/RIOT/tree/master/tests](https://github.com/RIOT-OS/RIOT/tree/master/tests)
+
+\[2\] [https://github.com/RIOT-OS/RIOT](https://github.com/RIOT-OS/RIOT)

RIOT/documentation/02_doxygen.md

@@ -6,14 +6,14 @@
 ## Description
 
 The objective of this exercise is to enhance existing documentation or add new
-documentation to the automatically generated doxygen
-[documentation](http://doc.riot-os.org/)
-
+documentation to the automatically generated doxygen documentation.
 ## Instructions
 
-1. Inspect the doxygen [documentation](http://doc.riot-os.org/)
+1. Inspect the doxygen documentation \[1\]
 2. Search for text blocks that are vague or contain spelling errors
-3. Provide a Pull Request to the official
-   [RIOT](https://github.com/RIOT-OS/RIOT) repository.
+3. Provide a Pull Request to the official RIOT \[2\] repository.
 
 ## References
+\[1\] [http://doc.riot-os.org/](http://doc.riot-os.org/)
+
+\[2\] [https://github.com/RIOT-OS/RIOT](https://github.com/RIOT-OS/RIOT)

RIOT/system/01_shell_command_morse.md

@@ -10,18 +10,21 @@ which parses input strings to Morse signals expressed via LED.
 
 ## Instructions
 
-1. Get familiar with the shell using [1] and the timer module xtimer [2].
-2. Program a shell command handler that parses strings to Morse code [3]. Note
+1. Get familiar with the shell using \[1\] and the timer module xtimer \[2\].
+2. Program a shell command handler that parses strings to Morse code \[3\]. Note
 that you don't necessarily need a board for development. You can also
-develop under native [4] as there is an LED abstraction.
+develop under native \[4\] as there is an LED abstraction.
 3. Generate a new module with your code under *RIOT/drivers* which can be included
 via Makefile.
 
 Document _all_ your actions and findings. Create an archive with your solution.
 
 ## References
 
-[1]: https://github.com/RIOT-OS/RIOT/tree/master/tests/shell
-[2]: https://riot-os.org/api/group__sys__xtimer.html
-[3]: https://en.wikipedia.org/wiki/Morse_code
-[4]: https://github.com/RIOT-OS/RIOT/wiki/Family%3A-native
+\[1\] [https://github.com/RIOT-OS/RIOT/tree/master/tests/shell](https://github.com/RIOT-OS/RIOT/tree/master/tests/shell)
+
+\[2\] [https://riot-os.org/api/group__sys__xtimer.html](https://riot-os.org/api/group__sys__xtimer.html)
+
+\[3\] [https://en.wikipedia.org/wiki/Morse_code](https://en.wikipedia.org/wiki/Morse_code)
+
+\[4\] [https://github.com/RIOT-OS/RIOT/wiki/Family%3A-native](https://github.com/RIOT-OS/RIOT/wiki/Family%3A-native)

RIOT/system/02_network_udp_stats.md

@@ -11,34 +11,43 @@ to write a module that collects minimal statistics on the transport layer.
 ## Instructions
 
 1. Get familiar with networking by using RIOTs default networking
-   example `gnrc_networking` [1] and exchange UDP packets between two instances
-   (either boards or RIOT native [2]) following these steps:
-* Go to the [`gnrc_networking` application](https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking)
-   and have a look in `udp.c` how packets are constructed, send and received
+   example `gnrc_networking` \[1\] and exchange UDP packets between two instances
+   (either boards or RIOT native \[2\]) following these steps:
+* Go to the `gnrc_networking` application \[3\] and have a look in `udp.c` how
+  packets are constructed, send and received
 * Compile, flash, and run on your board `BOARD=samr21-xpro make all flash term`
    or native `make clean all term PORT=tap0` resp. `tap1`
 * Type `help`
 * Start UDP server on port 8888 using `udp server 8888`
 * Get your IPv6 address using `ifconfig`
 * Send your neighbor some messages using `udp send`
-* [Read the Doc](http://doc.riot-os.org/group__net__gnrc.html)
+* Read the Doc \[4\]
 
 2. Now that you've used the whole UDP/IPv6 network stack, have a look inside the
-   implementation of UDP [3]. The goal is to write a software component which collects and prints
+   implementation of UDP \[5\]. The goal is to write a software component which collects and prints
    simple statistics about the amount of UDP packets and data that has been sent and received.
 
 3. There is an existing `netstats` module in RIOT which is used in `gnrc_networking` by default
-   and should be extended. Have a look the the header [4] and implementation for e.g. IPv6 [5]
-   and see how statistics are collected and when they are printed to the console [6]. Note that
+   and should be extended. Have a look the the header \[6\] and implementation for e.g. IPv6 \[7\]
+   and see how statistics are collected and when they are printed to the console \[8\]. Note that
    this tasks requires a certain amount of personal contribution.
 
 Document _all_ your actions and findings. Create an archive with your solution.
 
 ## References
 
-[1]: https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking
-[2]: https://github.com/RIOT-OS/RIOT/wiki/Family%3A-native
-[3]: https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/transport_layer/udp/gnrc_udp.c
-[4]: https://github.com/RIOT-OS/RIOT/blob/master/sys/include/net/netstats.h
-[5]: https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/network_layer/ipv6/gnrc_ipv6.c
-[6]: https://github.com/RIOT-OS/RIOT/blob/master/sys/shell/commands/sc_netif.c
+\[1\] [https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking](https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking)
+
+\[2\] [https://github.com/RIOT-OS/RIOT/wiki/Family%3A-native](https://github.com/RIOT-OS/RIOT/wiki/Family%3A-native)
+
+\[3\] [https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking](https://github.com/RIOT-OS/RIOT/tree/master/examples/gnrc_networking)
+
+\[4\] [http://doc.riot-os.org/group__net__gnrc.html](http://doc.riot-os.org/group__net__gnrc.html)
+
+\[5\] [https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/transport_layer/udp/gnrc_udp.c](https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/transport_layer/udp/gnrc_udp.c)
+
+\[6\] [https://github.com/RIOT-OS/RIOT/blob/master/sys/include/net/netstats.h](https://github.com/RIOT-OS/RIOT/blob/master/sys/include/net/netstats.h)
+
+\[7\] [https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/network_layer/ipv6/gnrc_ipv6.c](https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/network_layer/ipv6/gnrc_ipv6.c)
+
+\[8\] [https://github.com/RIOT-OS/RIOT/blob/master/sys/shell/commands/sc_netif.c](https://github.com/RIOT-OS/RIOT/blob/master/sys/shell/commands/sc_netif.c)