Merge branch 'documentation/create_mission_xml_add_citation' into 'develop'

Added citation to create mission XML

See merge request !66

docs/assets/bibtex/create_mission_xml_literature.bib

+%%% BOOKS %%%
+
+@book{Ple24,
+  title={Air Navigation: Fundamentals, Systems, and Flight Trajectory Management},
+  author={Pleter, Octavian Thor},
+  year={2024},
+  pages = {239-240},
+  publisher={Springer Nature}
+}
+
+%%% JOURNAL ARTICLES %%%
+
+%%% CONFERENCE PAPERS %%%
+
+%%% THESES %%%
+
+%%% TECHNICAL REPORTS %%%
+
+%%% OTHER %%%

docs/documentation/sizing/create_mission_xml/index.md

@@ -9,10 +9,8 @@ In short, a mission contains a handful of so-called segments with which you can
 
 <p align="center">
   <img src="figures/flight_path.png" alt="Flight segments" width="97.5%">
-  <br>
-  <em>Flight segments with typical speeds: IAS (blue), Mach (green), and TAS (violet) [1].</em>
 </p>
-
+*Flight segments with typical speeds: IAS (blue), Mach (green), and TAS (violet)*[@Ple24].
 
 **create_mission_xml** sets the target/end points of these flight segments which will later be connected by [Mission Analysis](../../analysis/mission_analysis/index.md). Those target points are saved into the `mission file` in which they are categorized as `departure_steps`, `cruise_steps` and `approach_steps`. What this `mission_file` contains in detail can be found in the [Getting Started](getting_started.md). 
 

docs/documentation/sizing/create_mission_xml/mission_steps.md

@@ -59,7 +59,7 @@ ICAO-A and ICAO-B should tackle this, but it is not ready yet :construction:
 | cruise               | cruise               | clean   | N/A              | N/A                       | N/A                               |
 | descend to approach  | idle                 | clean   | 10000 ft         | N/A                       | CAS over flight level 100 descend |
 
-After reaching $10\,000\,ft$ the aircraft accelerates to the next higher speed limit `CAS_over_flight_level_100_climb` which is usually $300\,kts$ calibrated airspeed. Again, you can change this in the aircraft XML, but when you want to stick to current regulations, you should keep $300\,kts (= 154.3334 m/s)$. Then the aircraft keeps on climbing until the `initial_cruise_altitude` from where it accelerates to the `initial_cruise_mach_number` without climbing any further. In the table above, only one flight level change is displayed. How many of them will be initiated can be determined in the following way:
+After reaching $10\,000\,ft$ the aircraft accelerates to the next higher speed limit `CAS_over_flight_level_100_climb`. Then the aircraft keeps on climbing until the `initial_cruise_altitude` from where it accelerates to the `initial_cruise_mach_number` without climbing any further. In the table above, only one flight level change is displayed. How many of them will be initiated can be determined in the following way:
 
 - Short Range ($\leq 1\,000\,NM$):
     - 1 cruise climb step