mirror of
https://github.com/zmkfirmware/zmk.git
synced 2026-03-19 20:45:18 -05:00
fix(docs): minor corrections and fix typo (#2443)
* docs(faq): minor corrections * docs: fix typo - `s/Alterative/Alternative` * docs(faq): use Lily58 as an example instead of Corne with revision Co-authored-by: Nicolas Munnich <98408764+Nick-Munnich@users.noreply.github.com> --------- Co-authored-by: Nicolas Munnich <98408764+Nick-Munnich@users.noreply.github.com>
This commit is contained in:
committed by
GitHub
parent
b866ec031f
commit
6946ca8b07
@@ -57,7 +57,7 @@ For keyboards, this is one of two options:
|
|||||||
|
|
||||||
### What is a “shield”?
|
### What is a “shield”?
|
||||||
|
|
||||||
In ZMK, a _shield_ is a _PCB_ or _hardwired set of components_ that when combined with a MCU only [board](#what-is-a-board) like the Proton-C or nice!nano, results in a complete usable keyboard. Examples would be keyboard PCBs like the Kyria or Corne. The _shield_ is usually the big PCB containing all the keys.
|
In ZMK, a _shield_ is a _PCB_ or _hardwired set of components_ that when combined with an MCU-only [board](#what-is-a-board), like the Proton-C or nice!nano, results in a complete usable keyboard. Examples would be keyboard PCBs like the Kyria or Lily58. The _shield_ is usually the big PCB containing all the keys.
|
||||||
|
|
||||||
### Why _boards_ and _shields_? Why not just “keyboard”?
|
### Why _boards_ and _shields_? Why not just “keyboard”?
|
||||||
|
|
||||||
|
|||||||
@@ -149,7 +149,7 @@ When [using GitHub Actions to build ZMK](../user-setup.mdx), once you have obtai
|
|||||||
defaultValue="zmk"
|
defaultValue="zmk"
|
||||||
values={[
|
values={[
|
||||||
{label: 'Default', value: 'zmk'},
|
{label: 'Default', value: 'zmk'},
|
||||||
{label: 'Alterative', value: 'alt'},
|
{label: 'Alternative', value: 'alt'},
|
||||||
]}>
|
]}>
|
||||||
<TabItem value="zmk">
|
<TabItem value="zmk">
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user