diff --git a/docs/_09_development/_develop_guide/_develop_guide/_create_gazebo_assets.rst b/docs/_09_development/_develop_guide/_develop_guide/_create_gazebo_assets.rst
index ed4f2343..d23804d2 100644
--- a/docs/_09_development/_develop_guide/_develop_guide/_create_gazebo_assets.rst
+++ b/docs/_09_development/_develop_guide/_develop_guide/_create_gazebo_assets.rst
@@ -247,7 +247,21 @@ For the quadrotor, this template assumes your model has 4 links, one for each ro
 they are named m1_joint, m2_joint, m3_joint and m4_joint. These names can be changed to match your links names. The '_joint' is, however, necessary (if m1 is changed for YOUR_LINK, then its joint would have to be YOUR_LINK_joint).
 In addition to this, the base link of your quadrotor model must be 'base_link'.
 
-With this template, your model can be renderized to match all the expected naming by Aerostack2 and is ready to fly using the Gazebo Simulator.
+For your model to be properly loaded by Aerostack2, it has to be added as a valid drone type at ``as2_gazebo_assets/src/as2_gazebo_assets/models/drone.py``. This script declares a class ``DroneTypeEnum`` to which your new drone model must be added.
+
+.. code-block:: python
+
+    class DroneTypeEnum(str, Enum):
+        """Valid drone model types."""
+
+        QUADROTOR = 'quadrotor_base'
+        HEXROTOR = 'hexrotor_base'
+        CRAZYFLIE = 'crazyflie'
+        X500 = 'x500'
+        PX4 = 'px4vision'
+        YOUR_MODEL_TYPE = 'your_model_type'
+
+With this and your model added to a directory that has been added to the Gazebo resources path variable (check :ref:`this section <development_tutorials_gazebo_assets_objects>` of the adding Gazebo assets tutorial), your new drone is ready to be loaded by Gazebo and fly using Aerostack2.
 
 .. _development_guide_create_assets_add_sensor: