ad

docs/documentation/sizing/propulsion_design/overview.md

@@ -13,7 +13,7 @@ With this the engines are designed one by one with the following approach:
 
 ![](figures/engine_sizing.png){html: width=600}
 
-The outputs are the engine xml file as well as the different deck values as csv files in projects as well as the following xml snippet for each engine:
+The outputs are the engine xml file and the different deck values as csv files. They are saved in thr projects directory. Further output is saved in the aircraft xml because other tools of the UNICADO tool chain need it. An example of this output is shown below.
 
 ![](figures/xml_output.PNG){html: width=1200}
 
@@ -29,5 +29,5 @@ An example is shown in the following figure.
 
 ![](figures/deck_example.PNG)
 
-The data is readout by the engine library which has an efficient parser for the deck values using a linear interpolation between two existing deck values. Penalties, like shaft power offtake or bleed air offtake, are also calculated using the engine library. The scale factor is applied according to the exact scaling mechanism for the value needed.
-The description of the engine library can be found [here](../../../libraries/engine/).
\ No newline at end of file
+The data is readout by the engine library which has an efficient parser for the deck values using a linear interpolation between two existing deck values. Penalties, like shaft power offtake or bleed air offtake, are applied using the engine library. The scale factor is applied according to the exact scaling mechanism for the value needed.
+The description of the engine library can be found [here](../../../libraries/engine/).