summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAgathe Porte <microjoe@microjoe.org>2020-06-29 18:17:13 +0200
committerAgathe Porte <microjoe@microjoe.org>2020-06-29 18:17:13 +0200
commit741d4d93414100132b37f678990c029847d5159a (patch)
treeeeb9b1d9c9aef34d71288b0d5b4cd1d32558dc86
parent95bc8587dd84a0908e45b0aa8807169338d0c3f5 (diff)
downloadcharlcd-741d4d93414100132b37f678990c029847d5159a.tar.gz
charlcd-741d4d93414100132b37f678990c029847d5159a.zip
README.md: fix small typos
-rw-r--r--README.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/README.md b/README.md
index 007943c..400317b 100644
--- a/README.md
+++ b/README.md
@@ -27,8 +27,8 @@ protocol to interact with the screen over and over.
This approach seems just wrong if you consider what the Linux kernel can
provide in comparison. Indeed, it is the role of device drivers to properly
-abstract the access to the hardware from userspace perspective. For this,
-the Linux kernel uses an absraction mechanism to declare the hardware:
+abstract the access to the hardware from userspace perspective. For this,
+the Linux kernel uses an abstraction mechanism to declare the hardware:
the *device-tree*.
The *device-tree* nodes for a screen behind an I2C GPIO expander would look
@@ -63,7 +63,7 @@ auxdisplay: auxdisplay {
};
```
-Once the device-tree is correctly configured, the `charlcd` driver will
+Once the *device-tree* is correctly configured, the `charlcd` driver will
create a `/dev/lcd` character device.
The role of this library is to provide an astraction over this character
@@ -74,7 +74,7 @@ with the screen — instead of going from scratch and using ioctl over
# Known bugs
The charlcd driver is currently not able to report screen size to userspace.
-This is mitigated in the library by having a look at the device-tree entries
+This is mitigated in the library by having a look at the *device-tree* entries
directly.
# Going further