diff --git a/README.md b/README.md
index c47027860736c6e26a512eace7f83c4807144e79..1073f684582ddb9c3e00be3a622c6548a94cf21e 100644
--- a/README.md
+++ b/README.md
@@ -40,9 +40,9 @@ Its features comprise
 * the native port allows to run RIOT as-is on Linux, BSD, and MacOS. Multiple instances of RIOT running on a single machine can also be interconnected via a simple virtual Ethernet bridge
 * Wiselib support (C++ algorithm library, including routing, clustering, timesync, localization, security and more algorithms)
 * IPv6
-* TCP and UDP
+* UDP
 * 6LoWPAN
-* AODVv2, NHDP, RPL
+* NHDP
 
 ## GETTING STARTED
 * You want to start the RIOT? Just follow our [Getting started documentation](https://github.com/RIOT-OS/RIOT/wiki/Introduction)
@@ -58,11 +58,6 @@ There is a shellscript in `RIOT/cpu/native` called `tapsetup.sh` which you can u
 To create a bridge and two (or count at your option) tap interfaces:
 ./tapsetup.sh create [count]
 
-### EXAMPLE APPLICATIONS
-In the `examples` directory you can find some example applications. The `default` application demonstrates all available features for the current platform.
-
-For example, you can use it to the test the native networking by running two instances: `make term PORT=tap0` and `make term PORT=tap1`. Now configure two different addresses for both RIOT instances by typing `addr 1` and `addr 2` respectively and send a text message from one "node" to another by typing `txtsnd 2 hello` on the first "node".
-
 ## CONTRIBUTE
 
 To contribute something to RIOT, please refer to the [development procedures](https://github.com/RIOT-OS/RIOT/wiki/Development-procedures) and read all notes for best practice.