diff options
| author | Joel Challis <git@zvecr.com> | 2025-04-08 03:31:17 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-04-08 12:31:17 +1000 |
| commit | ca84b570429fdacc3211e85a3d1ee0e213bcd8e4 (patch) | |
| tree | bcda6a7a31d1ecf005a1219f019dba6cfe49d036 /docs | |
| parent | 5f222a3e02ec59620b1df54b07e405201448af06 (diff) | |
Remove direct docs.qmk.fm links from docs (#25113)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/hand_wire.md | 2 | ||||
| -rw-r--r-- | docs/license_violations.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/hand_wire.md b/docs/hand_wire.md index 9aeee7512d..be21cf2cc4 100644 --- a/docs/hand_wire.md +++ b/docs/hand_wire.md | |||
| @@ -231,7 +231,7 @@ Once you have confirmed that the keyboard is working, if you have used a seperat | |||
| 231 | 231 | ||
| 232 | If you found this fullfilling you could experiment by adding additional features such as [in switch LEDs](https://geekhack.org/index.php?topic=94258.0), [in switch RGB](https://www.reddit.com/r/MechanicalKeyboards/comments/5s1l5u/photoskeyboard_science_i_made_a_handwired_rgb/), [RGB underglow](https://medium.com/@DavidNZ/hand-wired-custom-keyboard-cdd14429c7b3#.7a1ovebsk) or even an [OLED display!](https://www.reddit.com/r/olkb/comments/5zy7og/adding_ssd1306_oled_display_to_your_build/) | 232 | If you found this fullfilling you could experiment by adding additional features such as [in switch LEDs](https://geekhack.org/index.php?topic=94258.0), [in switch RGB](https://www.reddit.com/r/MechanicalKeyboards/comments/5s1l5u/photoskeyboard_science_i_made_a_handwired_rgb/), [RGB underglow](https://medium.com/@DavidNZ/hand-wired-custom-keyboard-cdd14429c7b3#.7a1ovebsk) or even an [OLED display!](https://www.reddit.com/r/olkb/comments/5zy7og/adding_ssd1306_oled_display_to_your_build/) |
| 233 | 233 | ||
| 234 | There are a lot of possibilities inside the firmware - explore [docs.qmk.fm](https://docs.qmk.fm) for a full feature list, and dive into the different keyboards to see how people use all of them. You can always stop by [the OLKB subreddit](https://reddit.com/r/olkb) or [QMK Discord](https://discord.gg/qmk) for help! | 234 | There are a lot of possibilities inside the firmware - explore [the documentation](/) for a full feature list, and dive into the different keyboards to see how people use all of them. You can always stop by [the OLKB subreddit](https://reddit.com/r/olkb) or [QMK Discord](https://discord.gg/qmk) for help! |
| 235 | 235 | ||
| 236 | ## Links to Other Guides | 236 | ## Links to Other Guides |
| 237 | 237 | ||
diff --git a/docs/license_violations.md b/docs/license_violations.md index cf7850effc..0bc62102ed 100644 --- a/docs/license_violations.md +++ b/docs/license_violations.md | |||
| @@ -85,7 +85,7 @@ Reusing the `VID` and `PID` for multiple boards (such as for two variants, wired | |||
| 85 | 85 | ||
| 86 | If there is sufficient ambiguity about a board, supporting evidence will need to be presented to the QMK team. This may include impartial third parties who can demonstrate a board's existence and can confirm its feature set, such as well-known content producers; popular review sites or notable video creators may be leveraged. If such evidence is unavailable, as a last resort the vendor may be required to ship a fully functional board in full retail packaging to QMK maintainers for verification. Engineering samples will not be accepted, as one-off boards have been deceptively used in the past. | 86 | If there is sufficient ambiguity about a board, supporting evidence will need to be presented to the QMK team. This may include impartial third parties who can demonstrate a board's existence and can confirm its feature set, such as well-known content producers; popular review sites or notable video creators may be leveraged. If such evidence is unavailable, as a last resort the vendor may be required to ship a fully functional board in full retail packaging to QMK maintainers for verification. Engineering samples will not be accepted, as one-off boards have been deceptively used in the past. |
| 87 | 87 | ||
| 88 | PRs submitted to upstream QMK should not expect an instant merge just because source code has been provided -- code from OEMs has historically been of a quality lower than QMK standards, so as per the [PR checklist](https://docs.qmk.fm/pr_checklist) submitters should make the changes as small as possible and be prepared to change their implementation. | 88 | PRs submitted to upstream QMK should not expect an instant merge just because source code has been provided -- code from OEMs has historically been of a quality lower than QMK standards, so as per the [PR checklist](pr_checklist) submitters should make the changes as small as possible and be prepared to change their implementation. |
| 89 | 89 | ||
| 90 | ## Detection | 90 | ## Detection |
| 91 | 91 | ||
