qmk

Unnamed repository; edit this file 'description' to name the repository.
git clone git://git.z3bra.org/qmk.git
Log | Files | Refs | Submodules | LICENSE

commit b541369c45f13369c16de1b887f6ca5b7e589e6d
parent fc06975fa3ea31049c8a1dc7a42b78b90db1c89b
Author: Pavlos Vinieratos <pvinis@gmail.com>
Date:   Thu, 16 May 2019 17:21:51 +0200

[Docs] Fix typo in Userspace doc (#5871)

* typo

* Update docs/feature_userspace.md

Co-Authored-By: fauxpark <fauxpark@gmail.com>

Diffstat:
docs/feature_userspace.md | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/feature_userspace.md b/docs/feature_userspace.md @@ -110,7 +110,7 @@ QMK has a bunch of [functions](custom_quantum_functions.md) that have [`_quantum However, you can actually add support for keymap version, so that you can use it in both your userspace and your keymap! -For instance, lets looks at the `layer_state_set_user` function. Lets enable the [Tri Layer State](ref_functions.md#olkb-tri-layers) functionalitly to all of our boards, and then still have your `keymap.c` still able to use this functionality. +For instance, let's look at the `layer_state_set_user()` function. You can enable the [Tri Layer State](ref_functions.md#olkb-tri-layers) functionality on all of your boards, while also retaining the Tri Layer functionality in your `keymap.c` files. In your `<name.c>` file, you'd want to add this: ```c