docs(readme): remove title logo

README.md

@@ -1,13 +1,8 @@
 <!-- DO NOT EDIT THIS FILE; IT WAS GENERATED BY ./tools/update-readme -->
 <!-- EDIT README.md.tpl INSTEAD -->
-<h1 align="center">
-  <a href="" rel="noopener">
- <img width=200px height=150px src="media/icon.png" alt="Project logo"></a>
-</h1>
+# vedv
 
-<p align="center">
-<i>A tool for developing in a secure, issolated and reproducible environment</i>
-</p>
+A tool for developing in a secure, issolated and reproducible environment.
 
 ## Table of Contents
 
@@ -17,9 +12,7 @@ Click on the menu right before `README.md` as shown in the image below.
 
 ## About
 
-A tool for developing applications in a secure, issolated and reproducible environment with virtual machines using a Docker-like workflow.
-
-## Motivation
+This is a tool for developing applications in a secure, issolated and reproducible environment with virtual machines using a Docker-like workflow.
 
 The software we are developing needs to be tested on a system as close as possible to the one where it is going to be executed. Sometimes it is very difficult to satisfy this requirement with docker and we have to use virtual machines missing the docker workflow. This is why I started the development of vedv. I hope you find it useful. Thank you.
 

README.md.tpl

@@ -1,11 +1,6 @@
-<h1 align="center">
-  <a href="" rel="noopener">
- <img width=200px height=150px src="media/icon.png" alt="Project logo"></a>
-</h1>
+# vedv
 
-<p align="center">
-<i>A tool for developing in a secure, issolated and reproducible environment</i>
-</p>
+A tool for developing in a secure, issolated and reproducible environment.
 
 ## Table of Contents
 
@@ -15,9 +10,7 @@ Click on the menu right before `README.md` as shown in the image below.
 
 ## About
 
-A tool for developing applications in a secure, issolated and reproducible environment with virtual machines using a Docker-like workflow.
-
-## Motivation
+This is a tool for developing applications in a secure, issolated and reproducible environment with virtual machines using a Docker-like workflow.
 
 The software we are developing needs to be tested on a system as close as possible to the one where it is going to be executed. Sometimes it is very difficult to satisfy this requirement with docker and we have to use virtual machines missing the docker workflow. This is why I started the development of vedv. I hope you find it useful. Thank you.