Fix readme files

Author: w1th0utnam3

README.md

@@ -18,6 +18,7 @@ Surface reconstruction library and CLI for particle data from SPH simulations, w
     - [VTK](#vtk)
     - [PLY](#ply)
     - [XYZ](#xyz)
+  - [Output file formats](#output-file-formats)
 - [License](#license)
 
 # The `splashsurf` CLI
@@ -158,15 +159,19 @@ With these parameters, a scene with 13353401 particles is reconstructed in nearl
 
 ### VTK
 
-Files with the "`.vtk`" are loaded using [`vtkio`](https://crates.io/crates/vtkio). The VTK file is loaded as a big endian binary file and has to contain an "Unstructured Grid" with either `f32` or `f64` vertex coordinates. Any other data or attributes are ignored. Only the first "Unstructured Grid" is loaded, other entities are ignored.
+Files with the "`.vtk`" extension are loaded using [`vtkio`](https://crates.io/crates/vtkio). The VTK file is loaded as a big endian binary file and has to contain an "Unstructured Grid" with either `f32` or `f64` vertex coordinates. Any other data or attributes are ignored. Only the first "Unstructured Grid" is loaded, other entities are ignored.
 
 ### PLY
 
 Files with the "`.ply`" extension are loaded using [`ply-rs`](https://crates.io/crates/ply-rs). The PLY file has to contain an element called "`vertex`" with the properties `x`, `y` and `z` of type `f32`/["`Property::Float`"](https://docs.rs/ply-rs/0.1.3/ply_rs/ply/enum.Property.html#variant.Float). Any other properties or elements are ignored.
 
 ### XYZ
 
-Files with the "`.xyz`" extension are interpreted as raw bytes of `f32` values in native endianness of the system. Three consecutive `f32`s represent a (x,y,z) coordinate triplet of a fluid particle. 
+Files with the "`.xyz`" extension are interpreted as raw bytes of `f32` values in native endianness of the system. Three consecutive `f32`s represent a (x,y,z) coordinate triplet of a fluid particle.
+
+## Output file formats
+
+Currently, only VTK files are supported for output.
 
 # License