New Crowdin translations - ko (#26037)

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

docs/ko/dev_setup/dev_env_linux_ubuntu.md

@@ -33,24 +33,24 @@ The script is intended to be run on _clean_ Ubuntu LTS installations, and may no
 
 1. [Download PX4 Source Code](../dev_setup/building_px4.md):
 
-  ```sh
-  git clone https://github.com/PX4/PX4-Autopilot.git --recursive
-  ```
+   ```sh
+   git clone https://github.com/PX4/PX4-Autopilot.git --recursive
+   ```
 
-  ::: info
-  The environment setup scripts in the source usually work for recent PX4 releases.
-  If working with an older version of PX4 you may need to [get the source code specific to your release](../contribute/git_examples.md#get-a-specific-release).
+   ::: info
+   The environment setup scripts in the source usually work for recent PX4 releases.
+   If working with an older version of PX4 you may need to [get the source code specific to your release](../contribute/git_examples.md#get-a-specific-release).
 
 :::
 
 2. Run the **ubuntu.sh** with no arguments (in a bash shell) to install everything:
 
-  ```sh
-  bash ./PX4-Autopilot/Tools/setup/ubuntu.sh
-  ```
+   ```sh
+   bash ./PX4-Autopilot/Tools/setup/ubuntu.sh
+   ```
 
-  - 스크립트가 진행되는 동안 모든 프롬프트를 확인합니다.
-  - You can use the `--no-nuttx` and `--no-sim-tools` options to omit the NuttX and/or simulation tools.
+   - 스크립트가 진행되는 동안 모든 프롬프트를 확인합니다.
+   - You can use the `--no-nuttx` and `--no-sim-tools` options to omit the NuttX and/or simulation tools.
 
 3. If you need Gazebo Classic (Ubuntu 22.04 only) then you can manually remove Gazebo and install it by following the instructions in [Gazebo Classic > Installation](../sim_gazebo_classic/index.md#installation).
 

docs/ko/dev_setup/dev_env_windows_cygwin_packager_setup.md

@@ -135,31 +135,31 @@ The toolchain gets maintained and hence these instructions might not cover every
 
 10. Download [**Apache Ant**](https://ant.apache.org/bindownload.cgi) as zip archive of the binaries for Windows and unpack the content to the folder `C:\PX4\toolchain\apache-ant`.
 
-   :::tip
-   Make sure you don't have an additional folder layer from the folder which is inside the downloaded archive.
+    :::tip
+    Make sure you don't have an additional folder layer from the folder which is inside the downloaded archive.
 
 :::
 
-   ::: info
-   This is what the toolchain does in: [apache-ant/install-apache-ant.bat](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/apache-ant/install-apache-ant.bat).
+    ::: info
+    This is what the toolchain does in: [apache-ant/install-apache-ant.bat](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/apache-ant/install-apache-ant.bat).
 
 :::
 
 11. Download, build and add _genromfs_ to the path:
-   - Clone the source code to the folder **C:\PX4\toolchain\genromfs\genromfs-src** with
+    - Clone the source code to the folder **C:\PX4\toolchain\genromfs\genromfs-src** with
 
       ```sh
       cd /c/toolchain/genromfs
       git clone https://github.com/chexum/genromfs.git genromfs-src
       ```
 
-   - Compile it with:
+    - Compile it with:
 
       ```sh
       cd genromfs-src
       make all
       ```
 
-   - Copy the resulting binary **genromfs.exe** one folder level out to: **C:\PX4\toolchain\genromfs**
+    - Copy the resulting binary **genromfs.exe** one folder level out to: **C:\PX4\toolchain\genromfs**
 
 12. Make sure all the binary folders of all the installed components are correctly listed in the `PATH` variable configured by [**setup-environment.bat**](https://github.com/PX4/PX4-windows-toolchain/blob/master/toolchain/scripts/setup-environment.bat).

docs/ko/dev_setup/dev_env_windows_vm.md

@@ -57,12 +57,12 @@ VMWare performance is acceptable for basic usage (building Firmware) but not for
    모든 설정은 호스트 운영 체제에서 사용하기 위한 것이므로, 네트워크 공격의 위험을 증가시키지 않는 화면 보호기 및 로컬 워크스테이션 보안 기능을 비활성화할 수 있습니다.
 
 10. Once the new VM is booted up make sure you install _VMWare tools drivers and tools extension_ inside your guest system.
-   이렇게 하면 다음과 같은 VM 사용의 성능과 유용성들이 향상됩니다.
-   - 크게 향상된 그래픽 성능
-   - Proper support for hardware device usage like USB port allocation (important for target upload), proper mouse wheel scrolling, sound support
-   - 창 크기에 따른 게스트 디스플레이 해상도 조정
-   - 호스트 시스템 클립보드 공유
-   - 호스트 시스템 파일 공유
+    이렇게 하면 다음과 같은 VM 사용의 성능과 유용성들이 향상됩니다.
+    - 크게 향상된 그래픽 성능
+    - Proper support for hardware device usage like USB port allocation (important for target upload), proper mouse wheel scrolling, sound support
+    - 창 크기에 따른 게스트 디스플레이 해상도 조정
+    - 호스트 시스템 클립보드 공유
+    - 호스트 시스템 파일 공유
 
 11. Continue with [PX4 environment setup for Linux](../dev_setup/dev_env_linux.md)
 
@@ -96,11 +96,11 @@ To allow this, you need to configure USB passthrough settings:
 
 4. Add USB filters for the bootloader in VM: **VirtualBox > Settings > USB > Add new USB filter**.
    - Open the menu and plug in the USB cable connected to your autopilot.
-      Select the `...Bootloader` device when it appears in the UI.
+     Select the `...Bootloader` device when it appears in the UI.
 
-      ::: info
-      The bootloader device only appears for a few seconds after connecting USB.
-      If it disappears before you can select it, disconnect and then reconnect USB.
+     ::: info
+     The bootloader device only appears for a few seconds after connecting USB.
+     If it disappears before you can select it, disconnect and then reconnect USB.
 
 :::
 

docs/ko/dev_setup/vscode.md

@@ -27,10 +27,10 @@ You must already have installed the command line [PX4 developer environment](../
 
    - Select _Open folder ..._ option on the welcome page (or using the menu: **File > Open Folder**):
 
-      ![Open Folder](../../assets/toolchain/vscode/welcome_open_folder.jpg)
+     ![Open Folder](../../assets/toolchain/vscode/welcome_open_folder.jpg)
 
    - A file selection dialog will appear.
-      Select the **PX4-Autopilot** directory and then press **OK**.
+     Select the **PX4-Autopilot** directory and then press **OK**.
 
    The project files and configuration will then load into _VSCode_.
 
@@ -49,9 +49,9 @@ You must already have installed the command line [PX4 developer environment](../
 :::
 
    - If prompted to install a new version of _cmake_:
-      - Say **No** (the right version is installed with the [PX4 developer environment](../dev_setup/dev_env.md)).
+     - Say **No** (the right version is installed with the [PX4 developer environment](../dev_setup/dev_env.md)).
    - If prompted to sign into _github.com_ and add your credentials:
-      - 이것은 당신에게 달려 있습니다! Github와 IDE 간의 긴밀한 통합을 제공하여 워크플로를 단순화할 수 있습니다.
+     - 이것은 당신에게 달려 있습니다! Github와 IDE 간의 긴밀한 통합을 제공하여 워크플로를 단순화할 수 있습니다.
    - Other prompts are optional, and may be installed if they seem useful. <!-- perhaps add screenshot of these prompts -->
 
 <a id="building"></a>
@@ -63,21 +63,21 @@ You must already have installed the command line [PX4 developer environment](../
 1. Select your build target ("cmake build config"):
 
    - The current _cmake build target_ is shown on the blue _config_ bar at the bottom (if this is already your desired target, skip to next step).
-      ![Select Cmake build target](../../assets/toolchain/vscode/cmake_build_config.jpg)
+     ![Select Cmake build target](../../assets/toolchain/vscode/cmake_build_config.jpg)
 
-      ::: info
-      The cmake target you select affects the targets offered for when [building/debugging](#debugging) (i.e. for hardware debugging you must select a hardware target like `px4_fmu-v6`).
+     ::: info
+     The cmake target you select affects the targets offered for when [building/debugging](#debugging) (i.e. for hardware debugging you must select a hardware target like `px4_fmu-v6`).
 
 :::
 
    - Click the target on the config bar to display other options, and select the one you want (this will replace any selected target).
 
    - _Cmake_ will then configure your project (see notification in bottom right).
-      ![Cmake config project](../../assets/toolchain/vscode/cmake_configuring_project.jpg)
+     ![Cmake config project](../../assets/toolchain/vscode/cmake_configuring_project.jpg)
 
    - Wait until configuration completes.
-      When this is done the notification will disappear and you'll be shown the build location:
-      ![Cmake config project](../../assets/toolchain/vscode/cmake_configuring_project_done.jpg).
+     When this is done the notification will disappear and you'll be shown the build location:
+     ![Cmake config project](../../assets/toolchain/vscode/cmake_configuring_project_done.jpg).
 
 2. You can then kick off a build from the config bar (select either **Build** or **Debug**).
    ![Run debug or build](../../assets/toolchain/vscode/run_debug_build.jpg)