New Crowdin translations - ko

docs/ko/contribute/code.md

@@ -14,7 +14,7 @@ We try to retain a [linear history through rebases](https://www.atlassian.com/gi
 To contribute new functionality, [sign up for Github](https://docs.github.com/en/get-started/signing-up-for-github/signing-up-for-a-new-github-account), then [fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the repository, [create a new branch](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository), add your [changes as commits](#commits-and-commit-messages), and finally [send a pull request](#pull-requests).
 Changes will be merged when they pass our [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) tests.
 
-All code contributions have to be under the permissive [BSD 3-clause license](https://opensource.org/licenses/BSD-3-Clause) and all code must not impose any further constraints on the use.
+All code contributions have to be under the permissive [BSD 3-clause license](https://opensource.org/license/BSD-3-Clause) and all code must not impose any further constraints on the use.
 
 ## Code Style
 
@@ -114,7 +114,7 @@ Source-code documentation standards are not enforced, and the code is currently
   - Do not add documentation that can trivially be inferred from C++ entity names.
   - ALWAYS specify units of variables, constants, and input/return parameters where they are defined.
   - 일반적으로 특이 사항이나 오류 처리에 대한 정보를 추가할 수 있습니다.
-  - [Doxgyen](http://www.doxygen.nl/) tags should be used if documentation is needed: `@class`, `@file`, `@param`, `@return`, `@brief`, `@var`, `@see`, `@note`.
+  - [Doxgyen](https://www.doxygen.nl/) tags should be used if documentation is needed: `@class`, `@file`, `@param`, `@return`, `@brief`, `@var`, `@see`, `@note`.
     A good example of usage is [src/modules/events/send_event.h](https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/events/send_event.h).
 
 Please avoid "magic numbers", for example, where does this number in the conditional come from? What about the multiplier on yaw stick input?

docs/ko/contribute/dev_call.md

@@ -29,11 +29,11 @@ The Community Q&A call is open to all interested community members.
 
 ## 회의 목적
 
-We publish a forum post per meeting a week before the call on [PX4 Discuss - weekly-dev-call](https://discuss.px4.io/c/weekly-dev-call) and track the agenda write down the discussion for the day. We welcome any topics that you, as a community member may have questions about / want to discuss!
+We publish a forum post per meeting a week before the call on [PX4 Discuss - weekly-dev-call](https://discuss.px4.io/c/weekly-dev-call/14) and track the agenda write down the discussion for the day. We welcome any topics that you, as a community member may have questions about / want to discuss!
 
 Please add your topics for discussion to the agenda before the meeting begins, by replying to the meeting note. This will help you formulate your questions more clearly, and allow us to think about them in advance.
 
 ## 일정
 
-- TIME: Wednesday 17h00 CET ([subscribe to calendar](https://www.dronecode.org/calendar/))
+- TIME: Wednesday 17h00 CET ([subscribe to calendar](https://dronecode.org/calendar/))
 - **Join the call**: [https://discord.gg/BDYmr6FA6Q](https://discord.gg/BDYmr6FA6Q)

docs/ko/contribute/docs.md

@@ -38,7 +38,7 @@ For these kinds of changes we suggest using the same approach as for _code_:
 1. Use the _git_ toolchain to get the PX4 source code onto your local computer.
 2. 필요한 문서를 수정합니다(추가, 변경, 삭제).
 3. _Test_ that it builds properly using Vitepress.
-4. Create a branch for your changes and create a pull request (PR) to pull it back into the [PX4-Autopilot](https://github.com/PX4/PX4-Autopilot.git) repo.
+4. Create a branch for your changes and create a pull request (PR) to pull it back into the [PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) repo.
 
 다음에는 소스 코드를 가져오고, 로컬에서 빌드(테스트용)하고, 코드를 수정하는 방법을 설명합니다.
 
@@ -58,7 +58,7 @@ If you already have a clone of the [PX4-Autopilot](https://github.com/PX4/PX4-Au
 
 1. Download git for your computer from [https://git-scm.com/downloads](https://git-scm.com/downloads)
 
-2. [Sign up](https://github.com/join) for Github if you haven't already
+2. [Sign up](https://github.com/signup) for Github if you haven't already
 
 3. Create a copy (Fork) of the [PX4-Autopilot repo](https://github.com/PX4/PX4-Autopilot) on Github ([instructions here](https://docs.github.com/en/get-started/quickstart/fork-a-repo)).
 
@@ -135,7 +135,6 @@ Within the repository you created above:
   새 분기가 분기된 저장소로 푸시되었다는 메시지가 표시되어야 합니다.
 
 7. 풀 요청(PR) 생성:
-
   - On the right hand side of the "new branch message" (see one step before), you should see a green button saying "Compare & Create Pull Request".
     클릭합니다.
   - 풀 요청 템플릿이 생성됩니다.
@@ -153,7 +152,6 @@ Within the repository you created above:
 로컬에서 라이브러리를 빌드하여, 변경 사항이 제대로 반영되었는 지를 테스트합니다.
 
 1. Install the [Vitepress prerequisites](https://vitepress.dev/guide/getting-started#prerequisites):
-
   - [Nodejs 18+](https://nodejs.org/en)
   - [Yarn classic](https://classic.yarnpkg.com/en/docs/install)
 
@@ -234,7 +232,6 @@ The guide uses the [Vitepress](https://vitepress.dev/) toolchain.
   - 이렇게 하면 다른 페이지와 이미지가 항상 동일한 상대 수준이므로 연결이 더 용이해집니다.
 
 - The _structure_ of the book is defined in `SUMMARY.md`.
-
   - If you add a new page to the guide you must also add an entry to this file!
 
     :::tip
@@ -260,7 +257,6 @@ When you add a new page you must also add it to `en/SUMMARY.md`!
 ## 스타일 가이드
 
 1. 파일/파일명
-
   - Put new markdown files in an appropriate sub-folder of `/en/`, such as `/en/contribute/`.
     폴더를 중첩하지 마십시오.
   - Put new image files in an appropriate nested sub-folder of `/assets/`.
@@ -270,14 +266,12 @@ When you add a new page you must also add it to `en/SUMMARY.md`!
   - Use lower case filenames and separate words using underscores (`_`).
 
 2. 이미지
-
   - 이미지는 최대한 가장 작은 크기와 가장 낮은 해상도를 사용합니다(이렇게 하면 대역폭이 좋지 않은 사용자의 다운로드 비용이 줄어듭니다).
   - New images should be created in a sub-folder of `/assets/` (so they can be shared between translations).
   - SVG files are preferred for diagrams.
     PNG files are preferred over JPG for screenshots.
 
 3. 내용
-
   - Use "style" (**bold**, _emphasis_, etc.) consistently and sparingly (as little as possible).
     - **Bold** for button presses and menu definitions.
     - _Emphasis_ for tool names such as _QGroundControl_ or _prettier_.
@@ -292,7 +286,6 @@ When you add a new page you must also add it to `en/SUMMARY.md`!
   - Format using _prettier_ (_VSCode_ is a has extensions can be used for this).
 
 4. Videos:
-
   - Youtube videos can be added using the format `<lite-youtube videoid="<youtube-video-id>" title="your title"/>` (supported via the [https://www.npmjs.com/package/lite-youtube-embed](https://www.npmjs.com/package/lite-youtube-embed) custom element, which has other parameters you can pass).
     - Use instructional videos sparingly as they date badly, and are hard to maintain.
     - Cool videos of airframes in flight are always welcome.

docs/ko/contribute/git_examples.md

@@ -6,7 +6,7 @@
 
 PX4 기능 추가 절차는 다음과 같습니다. 다음 예제를 따라 PX4에 기여 결과를 공유할 수 있습니다.
 
-- [Sign up](https://github.com/join) for github if you haven't already
+- [Sign up](https://github.com/signup) for github if you haven't already
 
 - Fork the PX4-Autopilot repo (see [here](https://docs.github.com/en/get-started/quickstart/fork-a-repo))
 
@@ -49,7 +49,7 @@ PX4 기능 추가 절차는 다음과 같습니다. 다음 예제를 따라 PX4
   git add <file name>
   ```
 
-  If you prefer having a GUI to add your files see [Gitk](https://git-scm.com/book/en/v2/Git-in-Other-Environments-Graphical-Interfaces) or [`git add -p`](http://nuclearsquid.com/writings/git-add/).
+  If you prefer having a GUI to add your files see [Gitk](https://git-scm.com/book/en/v2/Git-in-Other-Environments-Graphical-Interfaces) or [`git add -p`](https://nuclearsquid.com/writings/git-add/).
 
 - 변경 사항을 설명하는 메시지와 함께 추가된 파일을 커밋합니다.
 
@@ -292,7 +292,7 @@ If a conflict occurs during a `git rebase`, please refer to [this guide](https:/
 
 ### 풀 병합 충돌
 
-If a conflict occurs during a `git pull`, please refer to [this guide](https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/#competing-line-change-merge-conflicts).
+If a conflict occurs during a `git pull`, please refer to [this guide](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line#competing-line-change-merge-conflicts).
 
 ### 오래된 git 태그로 인한 빌드 오류
 

docs/ko/contribute/licenses.md

@@ -1,12 +1,12 @@
 # 라이센스
 
 :::info
-All code contributions must be made under the permissive [BSD 3-clause license](https://opensource.org/licenses/BSD-3-Clause) and must not impose any further constraints on its use.
+All code contributions must be made under the permissive [BSD 3-clause license](https://opensource.org/license/BSD-3-Clause) and must not impose any further constraints on its use.
 :::
 
 시스템의 구성요소들에 대한 라이선스를 문서로 정리합니다.
 
 - [PX4 Flight Stack](https://github.com/PX4/PX4-Autopilot) — BSD
 - [PX4 Middleware](https://github.com/PX4/PX4-Autopilot) — BSD
-- [Pixhawk Hardware](https://github.com/PX4/Hardware) — CC-BY-SA 3.0
+- [Pixhawk Hardware](https://github.com/pixhawk/Hardware) — CC-BY-SA 3.0
 - [PX4 User Guide](https://github.com/PX4/PX4-user_guide) (Documentation) — [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).