New Crowdin translations - ko (#24547)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>

docs/ko/advanced/gimbal_control.md

@@ -129,7 +129,7 @@ The on-screen gimbal control can be used to move/test a connected MAVLink camera
 
 2. Open QGroundControl and enable the on-screen camera control (Application settings).
 
-   ![Quadrotor(x500) with gimbal (Front-facing) in Gazebo](../../assets/qgc/fly/gimbal_control_x500gz.png)
+  ![Quadrotor(x500) with gimbal (Front-facing) in Gazebo](../../assets/qgc/fly/gimbal_control_x500gz.png)
 
 3. Make sure the vehicle is armed and flying, e.g. by entering with `commander takeoff`.
 

docs/ko/advanced/parameters_and_configurations.md

@@ -128,21 +128,21 @@ You add some "boilerplate" code to regularly listen for changes in the [uORB Top
 
 - **px4_platform_common/module_params.h** to get the `DEFINE_PARAMETERS` macro:
 
-  ```cpp
-  #include <px4_platform_common/module_params.h>
-  ```
+ ```cpp
+ #include <px4_platform_common/module_params.h>
+ ```
 
 - **parameter_update.h** to access the uORB `parameter_update` message:
 
-  ```cpp
-  #include <uORB/topics/parameter_update.h>
-  ```
+ ```cpp
+ #include <uORB/topics/parameter_update.h>
+ ```
 
 - **Subscription.hpp** for the uORB C++ subscription API:
 
-  ```cpp
-  #include <uORB/Subscription.hpp>
-  ```
+ ```cpp
+ #include <uORB/Subscription.hpp>
+ ```
 
 Derive your class from `ModuleParams`, and use `DEFINE_PARAMETERS` to specify a list of parameters and their associated parameter attributes.
 매개변수의 이름은 매개변수 메타데이터 정의와 동일하여야 합니다.
@@ -194,7 +194,7 @@ void Module::parameters_update()
 - `_parameter_update_sub.updated()` tells us if there is _any_ update to the `param_update` uORB message (but not what parameter is affected).
 - If there has been "some" parameter updated, we copy the update into a `parameter_update_s` (`param_update`), to clear the pending update.
 - Then we call `ModuleParams::updateParams()`.
-  This "under the hood" updates all parameter attributes listed in our `DEFINE_PARAMETERS` list.
+ This "under the hood" updates all parameter attributes listed in our `DEFINE_PARAMETERS` list.
 
 The parameter attributes (`_sys_autostart` and `_att_bias_max` in this case) can then be used to represent the parameters, and will be updated whenever the parameter value changes.
 
@@ -267,12 +267,12 @@ YAML meta data is intended as a full replacement for the **.c** definitions.
 - An example of YAML definitions being used can be found in the MAVLink parameter definitions: [/src/modules/mavlink/module.yaml](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/mavlink/module.yaml).
 - YAML 파일은 다음을 추가하여 cmake 빌드 시스템에 등록됩니다.
 
-  ```cmake
-  MODULE_CONFIG
-  	module.yaml
-  ```
+ ```cmake
+ MODULE_CONFIG
+ 	module.yaml
+ ```
 
-  to the `px4_add_module` section of the `CMakeLists.txt` file of that module.
+ to the `px4_add_module` section of the `CMakeLists.txt` file of that module.
 
 #### 다중 인스턴스(템플릿) YAML 메타 데이터
 

docs/ko/advanced/system_tunes.md

@@ -52,7 +52,7 @@ On Windows, one option is to use _Melody Master_ within _Dosbox_.
 7. 음악을 저장할 준비가 끝나면:
    - Press **F2** to give the tune a name and save it in the _/Music_ sub folder of your Melody Master installation.
    - Press **F7**, the scroll down the list of output formats on the right to get to ANSI.
-     The file will be exported to the _root_ of the Melody Master directory (with the same name and a file-type specific extension).
+      The file will be exported to the _root_ of the Melody Master directory (with the same name and a file-type specific extension).
 
 8. 파일을 여십시오.
    출력 내용은 다음과 같습니다: