docs fixtypo

docs/tinyorm/getting-started.mdx

@@ -126,7 +126,7 @@ Let's examine a basic model class and discuss some of TinyORM's key conventions:
 
 ### Table Names
 
-After glancing at the example above, you may have noticed that we did not tell TinyORM which database table corresponds to our `Flight` model. By convention, the "snake case", plural name of the class will be used as the table name unless another name is explicitly specified. So, in this case, TinyOrm will assume the `Flight` model stores records in the `flights` table, while an `AirTrafficOperator` model would store records in an `air_traffic_operators` table.
+After glancing at the example above, you may have noticed that we did not tell TinyORM which database table corresponds to our `Flight` model. By convention, the "snake case", plural name of the class will be used as the table name unless another name is explicitly specified. So, in this case, TinyOrm will assume the `Flight` model stores records in the `flights` table, while an `AirTrafficController` model would store records in an `air_traffic_controllers` table.
 
 If your model's corresponding database table does not fit this convention, you may manually specify the model's table name by defining the private `u_table` data member on the model:
 
@@ -141,7 +141,7 @@ If your model's corresponding database table does not fit this convention, you m
 
     private:
         /*! The table associated with the model. */
-        QString u_table {"torrents"};
+        QString u_table {"flights"};
     };
 
 ### Primary Keys