~reykjalin/vscode-kakoune

[PATCH] Fix README typos

Details
Message ID
<20221006055514.1305493-1-jimt@onjapan.net>
DKIM signature
pass
Download raw message
---
 README.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git README.md README.md
index 738258d..33c3d89 100644
--- README.md
+++ README.md
@@ -24,8 +24,8 @@ _Please send bug reports and feature requests to the [mailing list](https://list
 
 # Keymappings
 
-This plugin emulates modal editing, and will start in normal mode.
-You can not type in normal mode, until you [enter insert mode](#enter-insert-mode)
+This plugin emulates modal editing and will start in normal mode.
+You can not type in normal mode until you [enter insert mode](#enter-insert-mode).
 
 ## Enter insert mode
 
@@ -113,7 +113,7 @@ Doing has several benefits:
 1. There is _way_ less code.
 1. There will be fewer bugs.
 
-Of course the downside is that VSCode will be some sort of mish-mash between Kakoune and VSCode functionality, and there **will be inconsitencies**.
+Of course the downside is that VSCode will be some sort of mish-mash between Kakoune and VSCode functionality, and there **will be inconsistencies**.
 
 All of that said I'm very open to implementing some custom functionality if there is a valid reason to do so, e.g. if some very useful Kakoune feature would not work using VSCode functionality.
 
@@ -130,7 +130,7 @@ Just to make it easier to figure out what's actually different, here's a table w
 
 # Motivation
 
-I've been [trying to find a good code editor](https://thorlaksson.com/post/its-2019-why-dont-we-have-good-code-editors) for day to day use and haven't really been able to find one.
+I've been [trying to find a good code editor](https://thorlaksson.com/post/its-2019-why-dont-we-have-good-code-editors) for day-to-day use and haven't really been able to find one.
 VSCode provides the best overall experience, but I want a modal editor so I need to rely on extensions.
 Currently I use the Vim extension for VSCode to simulate Vim, but I like the Kakoune way of doing things so much better.
 Since there's no proper Kakoune mode plugin I decided I might as well just work on it myself!
@@ -142,7 +142,7 @@ Reason allows you to compile OCaml to JavaScript, and Fable compiles F# to JavaS
 Both languages looked like good candidates, and at first I decided to go with F# because I liked the structure and syntax of the language more than OCaml and Reason.
 
 However, after using Fable for a bit, I felt that the documentation was [a bit lacking](https://thorlaksson.com/post/calling-fable-from-typescript), and the JavaScript interoperability—while usable—isn't great.
-So I tried to use Reason, and I find the JavaScript interop much more user friendly and terse.
+So I tried to use Reason, and I find the JavaScript interop much more user-friendly and terse.
 The codebase in Reason is a bit smaller, mostly thanks to less glue code for JavaScript interop.
 
 The Reason tooling is also much better.
@@ -188,6 +188,6 @@ npm run build
 1. (Maybe) Handle pasting the same as Kakoune does.
 1. (Maybe) Handle replace mode the same as Kakoune.
 1. (Maybe) `:` commands, e.g. `:w` for saving, etc.
-   - Show pop up (Ctrl+P like menu) during search and `:` commands.
-     - Show suggestions from the Kakoune clippy in pop up.
+   - Show pop-up (Ctrl+P like menu) during search and `:` commands.
+     - Show suggestions from the Kakoune clippy in pop-up.
 1. (Maybe) Record macros.
-- 
2.34.1
Reply to thread Export thread (mbox)