From 09c5eab1570c521aa1236ac2f3aab0a6469550bf Mon Sep 17 00:00:00 2001
From: Oleg Hahm <oleg@hobbykeller.org>
Date: Thu, 3 Sep 2015 16:30:59 +0200
Subject: [PATCH] doc: minor update of mainpage.txt

---
 doc/doxygen/src/mainpage.txt | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/doc/doxygen/src/mainpage.txt b/doc/doxygen/src/mainpage.txt
index 894136541d..66505b344b 100644
--- a/doc/doxygen/src/mainpage.txt
+++ b/doc/doxygen/src/mainpage.txt
@@ -9,7 +9,8 @@
  * provides a microkernel, utilities like cryptographic libraries, data structures
  * (bloom filters, hash tables, priority queues), or a shell, different network
  * stacks, and support for various microcontrollers, radio drivers, sensors, and
- * configurations for entire platforms, e.g. TelosB or STM32 Discovery Boards.
+ * configurations for entire platforms, e.g. Zolertia Z1 or STM32 Discovery
+ * Boards.
  *
  * The microkernel itself comprises thread management, a priority-based scheduler,
  * a powerful API for inter-process communication (IPC), a system timer, and
@@ -84,7 +85,7 @@
  * by invoking make like this:
  *
  * \code
- * make BOARD=telosb
+ * make BOARD=iotlab-m3
  * \endcode
  *
  * Besides typical targets like `clean`, `all`, or `doc`, RIOT provides the special
@@ -100,6 +101,9 @@
  * variables like `INCLUDES`, setting the include paths. `Makefile.dep` serves to
  * define dependencies.
  *
+ * Learn more about the build system in the
+ * [Wiki](https://github.com/RIOT-OS/RIOT/wiki/The-Make-Build-System)
+ *
  * ####Including modules
  *
  * By default a RIOT application comprises only the applications' code itself, the kernel,
@@ -110,7 +114,7 @@
  * these lines:
  * \code
  * USEMODULE += sht11
- * USEMODULE += sixlowpan
+ * USEMODULE += gnrc_udp
  * \endcode
  * To contribute a new module to RIOT, your module's Makefile needs to set the
  * variable `MODULE` to a unique name. If the module depends on other modules, this