~ruther/qmk_firmware

028d2c91dc5175904ee57917e2a90028569e0f8f — Chas 4 years ago 9f690c9
Fixed typo in readme.md (#11333)

* Fixed typo in readme.md

censor -> sensor

* Censor -> Sensor in the Ploopy Trackball Readme
2 files changed, 2 insertions(+), 2 deletions(-)

M keyboards/ploopyco/mouse/readme.md
M keyboards/ploopyco/trackball/readme.md
M keyboards/ploopyco/mouse/readme.md => keyboards/ploopyco/mouse/readme.md +1 -1
@@ 19,7 19,7 @@ See the [build environment setup](https://docs.qmk.fm/#/getting_started_build_to

# Customzing your PloopyCo Mouse

While the defaults are designed so that it can be plugged in and used right away, there are a number of things that you may want to change.  Such as adding DPI control, or to use the ball to scroll while holding a button.   To allow for this sort of control, there is a callback for both the scroll wheel and the mouse censor. 
While the defaults are designed so that it can be plugged in and used right away, there are a number of things that you may want to change.  Such as adding DPI control, or to use the ball to scroll while holding a button.   To allow for this sort of control, there is a callback for both the scroll wheel and the mouse sensor. 

The default behavior for this is:


M keyboards/ploopyco/trackball/readme.md => keyboards/ploopyco/trackball/readme.md +1 -1
@@ 27,7 27,7 @@ The PCB should indicate which revision this is.

# Customzing your PloopyCo Trackball

While the defaults are designed so that it can be plugged in and used right away, there are a number of things that you may want to change.  Such as adding DPI control, or to use the ball to scroll while holding a button.   To allow for this sort of control, there is a callback for both the scroll wheel and the mouse censor. 
While the defaults are designed so that it can be plugged in and used right away, there are a number of things that you may want to change.  Such as adding DPI control, or to use the ball to scroll while holding a button.   To allow for this sort of control, there is a callback for both the scroll wheel and the mouse sensor. 

The default behavior for this is: