Update and correct README

README.md

@@ -1,6 +1,7 @@
 # Anbox
 
-Anbox is container based approach to boot a full Android system.
+Anbox is container based approach to boot a full Android system on a
+regular Linux system like Ubuntu.
 
 ## Overview
 
@@ -8,10 +9,6 @@ Anbox uses Linux namespaces (user, pid, uts, net, mount, ipc) to run a
 full Android system in a container and provide Android applications on
 any platform.
 
-The container itself does not run as root but as a unprivileged user.
-It just need to be able to perform a few operations to setup a
-container like spawning up new namespaces, chroot'ing to a rootfs etc.
-
 Android inside the container has no direct access to any hardware. All
 hardware access is going through the anbox daemon. We're reusing what
 Android has implemented for the Qemu based emulator. The Android system
@@ -33,21 +30,18 @@ Anbox is available as a snap in the public Ubuntu Store. Currently it
 is only available in the edge channel and requires to be installed in
 devmode as we don't have proper confinement for it in place yet.
 
-Additionally you need to manually load the binder and ashmem kernel
-drivers everytime as we build them out-of-tree with a hack as this
-isn't officially supported. Before you start anbox you always need
-to execute
-
-$ cd anbox
-$ scripts/load-kmods.sh
-
 Anbox can be installed from the Ubuntu Store with
 
+```
 $ snap install --edge --devmode anbox
+```
+
 
 Afterwards run it with
 
+```
 $ anbox
+```
 
 After the first installation the container management service needs
 a few minutes to setup the container the first time before it is
@@ -58,6 +52,11 @@ binary. For example
 
 $ anbox launch --package com.android.settings
 
+When installed as snap there will be also a desktop launcher available
+which will directly start the application viewer activity to give
+an overview of available Android applications and allows to start
+them.
+
 ## Build from source
 
 To build the Anbox runtime itself there is nothing special to know