Fix links in readme

README.md

@@ -16,12 +16,12 @@ It was designed with programmers in mind, so that tools and APIs supporting it c
 
 We believe that you should use CityJSON because: 
 
-  1. its simplicity means that it is already supported by [several software]({{ "/software/" | prepend: site.baseurl }}) 
-  2. you can in one-click convert CityGML files to CityJSON files, and vice versa, with the open-source tool [citygml-tools](https://github.com/citygml4j/citygml-tools); we even have a [tutorial]({{ "/tutorials/conversion/" | prepend: site.baseurl }})
+  1. its simplicity means that it is already supported by several software
+  2. you can in one-click convert CityGML files to CityJSON files, and vice versa, with the open-source tool [citygml-tools](https://github.com/citygml4j/citygml-tools)
   3. files are on average [6X more compact](https://github.com/tudelft3d/cityjson/wiki/Compression-factor-for-a-few-open-CityGML-datasets) than their CityGML equivalent
   4. there is a [web-viewer](https://tudelft3d.github.io/CityJSON-viewer) where you can drag-and-drop a file
   5. you can easily manipulate files with [cjio](https://github.com/tudelft3d/cjio), you can for instance merge files, remove/filter objects, change the CRS, manage the textures, etc.
-  6. you can *easily* define [Extensions]({{ "/extensions/" | prepend: site.baseurl }}) to the core model (akin to ADEs) 
+  6. you can *easily* define Extensions to the core model (akin to ADEs) 
   7. its development is [open on GitHub](https://github.com/tudelft3d/cityjson/issues/), it is supported by a vibrant community, and everyone is welcome to contribute