examples: rename ng_networking to gnrc_networking

examples/gnrc_networking/Makefile

@@ -1,5 +1,5 @@
 # name of your application
-APPLICATION = ng_networking
+APPLICATION = gnrc_networking
 
 # If no BOARD is found in the environment, use this default:
 BOARD ?= native

examples/gnrc_networking/README.md

@@ -1,4 +1,4 @@
-# ng_networking example
+# gnrc_networking example
 
 ## Connecting RIOT native and the Linux host
 
@@ -15,8 +15,8 @@ First, create a tap interface (to which RIOT will connect) and a bridge (to whic
     sudo ip tuntap add tap0 mode tap user ${USER}
     sudo ip link set tap0 up
 
-Now you can start the `ng_networking` example by invoking `make term`. This should automatically connect to the `tap0` interface. If
-this doesn't work for some reason, run `make` without any arguments, and then run the binary manually like so (assuming you are in the `examples/ng_networking` directory):
+Now you can start the `gnrc_networking` example by invoking `make term`. This should automatically connect to the `tap0` interface. If
+this doesn't work for some reason, run `make` without any arguments, and then run the binary manually like so (assuming you are in the `examples/gnrc_networking` directory):
 
 To verify that there is connectivity between RIOT and Linux, go to the RIOT console and run `ifconfig`:
 
@@ -63,4 +63,3 @@ Now, on the RIOT side, send a UDP packet using:
     udp send fe80::4049:5fff:fe17:b3ae 8808 testmessage
 
 You should see `testmessage` appear in netcat. Instead of using netcat, you can of course write your own software, but you may have to bind the socket to a specific interface (tap0 in this case). For an example that shows how to do so, see [here](https://gist.github.com/backenklee/dad5e80b764b3b3d0d3e).
-