New Crowdin translations - ko

docs/ko/concept/architecture.md

@@ -3,7 +3,7 @@
 PX4 consists of two main layers: the [flight stack](#flight-stack) is an estimation and flight control system,
 and the [middleware](#middleware) is a general robotics layer that can support any type of autonomous robot, providing internal/external communications and hardware integration.
 
-All PX4 [airframes](../airframes/index.md) share a single codebase (this includes other robotic systems like boats, rovers, submarines etc.). The complete system design is [reactive](http://www.reactivemanifesto.org), which means that:
+All PX4 [airframes](../airframes/index.md) share a single codebase (this includes other robotic systems like boats, rovers, submarines etc.). The complete system design is [reactive](https://www.reactivemanifesto.org), which means that:
 
 - 모든 기능은 대체 가능한 구성 요소와 재사용 가능한 구성 요소로 나누어 집니다.
 - 통신은 비동기 메시지 전달에 의해 수행됩니다.

docs/ko/concept/control_allocation.md

@@ -42,7 +42,7 @@ Overview of the mixing pipeline in terms of modules and uORB topics (press to sh
   - publishes the servo trims separately so they can be added as an offset when [testing actuators](../config/actuators.md#actuator-testing) (using the test sliders).
 - the output drivers:
   - handle the hardware initialization and update
-  - use a shared library [src/libs/mixer_module](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/mixer_module/).
+  - use a shared library [src/libs/mixer_module](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/mixer_module).
     The driver defines a parameter prefix, e.g. `PWM_MAIN` that the library then uses for configuration.
     Its main task is to select from the input topics and assign the right data to the outputs based on the user set `<param_prefix>_FUNCx` parameter values.
     For example if `PWM_MAIN_FUNC3` is set to **Motor 2**, the 3rd output is set to the 2nd motor from `actuator_motors`.

docs/ko/concept/events_interface.md

@@ -78,7 +78,6 @@ Explanations and requirements:
     This means as long as the event name stays the same, so will the ID.
 
 - **Log Level**:
-
   - valid log levels are the same as used in the MAVLink [MAV_SEVERITY](https://mavlink.io/en/messages/common.html#MAV_SEVERITY) enum.
     In order of descending importance these are:
 
@@ -117,7 +116,7 @@ Valid types: `uint8_t`, `int8_t`, `uint16_t`, `int16_t`, `uint32_t`, `int32_t`,
 You can also use enumerations as arguments:
 
 - PX4-specific/custom enumerations for events should be defined in [src/lib/events/enums.json](https://github.com/PX4/PX4-Autopilot/blob/main/src/lib/events/enums.json), and can then be used as event argument in the form of `events::send<events::px4::enums::my_enum_t>(...)`.
-- MAVLink "common" events are defined in [mavlink/libevents/events/common.json](https://github.com/mavlink/libevents/blob/master/events/common.json) and can be used as event argument in the form of `events::send<events::common::enums::my_enum_t>(...)`.
+- MAVLink "common" events are defined in [mavlink/libevents/events/common.json](https://github.com/mavlink/libevents/blob/main/events/common.json) and can be used as event argument in the form of `events::send<events::common::enums::my_enum_t>(...)`.
 
 #### Text format
 
@@ -128,7 +127,6 @@ Text format for event message description:
   These have to be escaped: '\\\\', '\\<', '\\{'.
 
 - supported tags:
-
   - Profiles: `<profile name="[!]NAME">CONTENT</profile>`
 
     `CONTENT` will only be shown if the name matches the configured profile.
@@ -142,7 +140,6 @@ Text format for event message description:
   - no nested tags of the same type are allowed
 
 - arguments: template placeholders that follow python syntax, with 1-based indexing (instead of 0)
-
   - general form: `{ARG_IDX[:.NUM_DECIMAL_DIGITS][UNIT]}`
 
     UNIT:

docs/ko/concept/system_startup.md

@@ -5,7 +5,7 @@ On NuttX they reside in the [ROMFS/px4fmu_common/init.d](https://github.com/PX4/
 The scripts that are only used on Posix are located in [ROMFS/px4fmu_common/init.d-posix](https://github.com/PX4/PX4-Autopilot/tree/main/ROMFS/px4fmu_common/init.d-posix).
 
 All files starting with a number and underscore (e.g. `10000_airplane`) are predefined airframe configurations.
-They are exported at build-time into an `airframes.xml` file which is parsed by [QGroundControl](http://qgroundcontrol.com) for the airframe selection UI.
+They are exported at build-time into an `airframes.xml` file which is parsed by [QGroundControl](https://qgroundcontrol.com) for the airframe selection UI.
 Adding a new configuration is covered [here](../dev_airframes/adding_a_new_frame.md).
 
 나머지 파일은 공통 시작 로직의 일부입니다.
@@ -33,7 +33,7 @@ Posix에서 시스템 셸은 스크립트 인터프리터로 사용됩니다(예
 
 - 쉘은 각 모듈을 새로운(클라이언트) 프로세스로 시작합니다.
   각 클라이언트 프로세스는 실제 모듈이 스레드로 실행되는 px4(서버)의 기본 인스턴스와 통신합니다.
-  This is done through a [UNIX socket](http://man7.org/linux/man-pages/man7/unix.7.html).
+  This is done through a [UNIX socket](https://man7.org/linux/man-pages/man7/unix.7.html).
   서버는 클라이언트가 연결하고 명령을 보낼 수 있는 소켓으로 수신 대기합니다.
   그런 다음 서버는 출력과 반환 코드를 다시 클라이언트로 전송합니다.