Wrote introduction text, hope it's not too long

README.md

-# Sancus: Lightweight and Open-Source Trusted Computing for the IoT
+# SWP - Sancus: Lightweight and Open-Source Trusted Computing for the IoT
 
-TODO: write a few introduction sentences
+During our software project in WS19/20 we worked with Sancus, a security architecture targeting
+resource-constrained embedded devices, which often times don't have dedicated memory protection
+mechanisms like an MPU or an MMU. 
 
+By utilizing newly created processor instructions and a small modification to the memory
+access logic of the processor, Sancus provides isolation for software modules, remote
+attestation of their states and secure communication between the modules/ those who provided
+them, and all of that without trusing _any_ software on the processor.
+([Read more about Sancus](docs/README.md))
 
-## Repository overview
-
-Here is a small overview about our repository structure, to brief which files you can find in the folders:
+During our software project, our goal was to run a Sancus-enabled system on an FPGA. Since
+the board used by the original prototype is outdated and unavailable, we tried to deploy Sancus
+on a recent FPGA board, the DE10-Standard by Altera.
 
-- docker
+Unfortunately, we didn't quite reach this goal. Becaus of that, our project is two-fold:
+On the one hand, despite not being able to finish the project, we came quite close to get
+OpenMSP430 (the processor implementation that Sancus extended) running. We hope that our
+insights can be used by others to finish what we started.
+On the other hand, we looked into compiling and simulating Sancus-enabled projects, wrote our
+own examples and wrote detailed documentation.
 
-  directory for building the toolchain using _Docker_
 
-- docs
+## Repository overview
 
-  all (external) documentations and user manuals
+Here is a small overview about our repository structure, to brief which files you can find in the folders:
 
-- presentation
+- _docker/_ - directory for building the toolchain using _Docker_
 
-  our results for the presentation of this project
+- _docs/_ - all (external) documentations and user manuals 
 
-- Repos
+- _presentation/_ - our results for the presentation of this project 
 
-  directory for all repositories from [Sancus](https://github.com/sancus-pma "Sancus repositories").
+- _Repos/_ - directory for all repositories from [Sancus](https://github.com/sancus-pma "Sancus repositories").
   
   There are also installation instructions for building the Sancus toolchain on your host system. 
 
-- src
-
-  directory for our source code, i. e. software modules to deploy
-
-- tools
-
-  external tools needed for this project, i. e. the CD contents from our development board
+- _src/_ - directory for our source code, i. e. software modules to deploy 
 
-- wiki
+- _tools/_ - external tools needed for this project, i. e. the CD contents from our development board 
 
-  wiki for further documentation, i. e. Sancus architecture overview, Sancus repositories overview, ...
+- _wiki/_ - wiki for further documentation, i. e. Sancus architecture overview, Sancus repositories overview, ...
 
 ## Installing the toolchain
 
@@ -48,7 +53,7 @@ For ArchLinux see [build_documentation_arch.md](Repos/build_documentation_arch.m
 
 ## TODO for README.md / Wiki
 
-- [ ] introduction sentences for this README.md / Repo
+- [X] introduction sentences for this README.md / Repo
 - [X] own repo structure/overview in wiki or README.md
 - [X] reference from README.md to docker/README.md at docker installation section
 - [X] update (or remove) 'from source' section from README.md (reference to Repos/README.md or Wiki or so..)