aboutsummaryrefslogtreecommitdiff
path: root/book/src/from-vim.md
diff options
context:
space:
mode:
authorAlireza Alavi2023-04-09 19:23:57 +0000
committerGitHub2023-04-09 19:23:57 +0000
commit78b516430adcfb68e5a0989c5af6b9a096175674 (patch)
tree57f7e50c3f3bf4903073dd9c2e41d5f06516fe4b /book/src/from-vim.md
parent6dabd36491673db0110e8b78f9489fa9354708c6 (diff)
Fix minor grammar issue in 'from-vim' docs (#6667)
Diffstat (limited to 'book/src/from-vim.md')
-rw-r--r--book/src/from-vim.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/book/src/from-vim.md b/book/src/from-vim.md
index 6ace9102..ffd5addc 100644
--- a/book/src/from-vim.md
+++ b/book/src/from-vim.md
@@ -2,9 +2,9 @@
Helix's editing model is strongly inspired from Vim and Kakoune, and a notable
difference from Vim (and the most striking similarity to Kakoune) is that Helix
-follows the `selection → action` model. This means that the whatever you are
-going to act on (a word, a paragraph, a line, etc) is selected first and the
-action itself (delete, change, yank, etc) comes second. A cursor is simply a
+follows the `selection → action` model. This means that whatever you are
+going to act on (a word, a paragraph, a line, etc.) is selected first and the
+action itself (delete, change, yank, etc.) comes second. A cursor is simply a
single width selection.
See also Kakoune's [Migrating from Vim](https://github.com/mawww/kakoune/wiki/Migrating-from-Vim) and Helix's [Migrating from Vim](https://github.com/helix-editor/helix/wiki/Migrating-from-Vim).