diff --git a/readme.md b/readme.md
index 6e495d4382f022ae0272912f54422dbf7f9d526d..682191a16ada0c6daa3b872d10f69b37c0454600 100644
--- a/readme.md
+++ b/readme.md
@@ -10,7 +10,7 @@ Paraview [www.paraview.org](https://www.paraview.org/):
 C++ Compiler:
 * with C++11 support, for example gcc6.3 or Visual C++ 14.0
     
-How to get Virtual Fluids:
+How to get VirtualFluidsCPU:
 ==========================
 
 Option 1: use git
@@ -22,10 +22,15 @@ Option 2: without git
 3. click on VirtualFluids/VirtualFluidsCPU
 4. click on the download symbol on the top right and download zip/tar.gz file
 
-How to build Virtual Fluids:
+How to build VirtualFluidsCPU:
 ============================
 
 1. CMake the project
 2. set the output path in Applications/LidDrivenCavity/LidDrivenCavity.cpp
 3. build the project ("compile")
 4. run the generated executable (usually in <build directory>/Applications/LidDrivenCavity)
+
+VirtualFluidsCPU results files:
+===============================
+
+VirtualFluidsCPU generates a set of multiple output directories in the prescribed output path. The flow fields can be found in the _mq_ directory. To view the flow fields, it is most conveniant to open the _mq_collection.pvd_ file in Paraview. The _bc_ directory contains the boundary condition information, the _geo_ directory contains information on the geometry of the flow domain and the _blocks_ directory contains the block grid.