updated readme

readme.md

@@ -4,7 +4,7 @@
 
 This is a plugin which enforces `alt-ijkl` navigation shortcuts on currently open keymap, tool windows and popups. The idea is that these shortcuts are more ergonomic for navigation/editing than using keyboard arrows so you can stop using arrows in IDE editor.
 
-These shortcuts are inspired by Vim, [gaming keyboard layouts](https://en.wikipedia.org/wiki/Arrow_keys#IJKL_keys) and common sense.
+These shortcuts are inspired by Vim and [gaming keyboard layouts](https://en.wikipedia.org/wiki/Arrow_keys#IJKL_keys).
 
 
 ## Shortcuts
@@ -29,8 +29,8 @@ Editor text modification:
  - `alt-y` - remove line
  - `alt-ctrl-shift-ik` - move statement up/down
  - `alt-ctrl-shift-jl` - move element left/right
- - `alt-cmd-shift-ik` (OSX) - move statement up/down
- - `alt-cmd-shift-jl` (OSX) - move element left/right
+ - `alt-cmd-shift-ik` (macOS) - move statement up/down
+ - `alt-cmd-shift-jl` (macOS) - move element left/right
  - `alt-/` - cyclic expand word (aka hippie completion)
  - `alt-'` - code completion
  - `alt-l` - choose lookup item and replace
@@ -52,41 +52,37 @@ Search and navigation between files:
 
 ## Why editor navigation shortcuts?
 
-Because existing key layouts are inefficient and painful to use. 
-
-Below you can find reasons for choosing particular keys.
+Because existing key layouts are inefficient and painful to use.
+See the reasons for choosing particular keys below.
 
 ### IJKL
 When touch typing you would normally position your index fingers on letters `f` and `j`. This is fine for writing a lot of text sequentially. The problem is that writing/editing code is never linear and requires a lot of navigation even for simplest tasks. Navigation with standard key layouts makes you move right hand from `j` letter to arrows and back to `j`. This takes a lot of effort.
 
-Ideally, we would just move arrows into the are with letters and use them as before. This is what `ijkl` mapped to `up/left/down/right` is trying to achieve (note that both `ijkl` and arrows are used with right hand).
+It would be great move the arrow eys into the area with letters. This is what `ijkl` mapped to `up/left/down/right` is trying to achieve.
 
 ### Alt
 There are several options how to make `ijkl` work for navigation.
 
-One option could be something like vim command/insert modes, i.e. "command mode" in which `ijkl` keys work as arrows and "insert mode" in which all keys work as in traditional editors. It might be a good idea to test this on practice over a long period of time. Although not many text editors have replicated vim modes so may be this is a sign.
+One option could be something like Vim command/insert modes, i.e. "command mode" in which `ijkl` keys work as arrows and "insert mode" in which all keys work as in traditional editors.
 
-Another option is to use modifier keys to change behaviour of `ijkl` letters (or you might think about it as enabling "command mode" only when modifier key is pressed). In general, this option is much easier to implement in various editors/IDEs. And among modifier keys, `alt` was the least used in existing IDE keymaps so the left `alt` was chosen.
+Another option is to use modifier keys to change behaviour of `ijkl` letters (or you might think about it as enabling "command mode" only when modifier key is pressed). In general, this option is easier to implement in various editors/IDEs. And among modifier keys, `alt` (the left one) was the least used in existing IDE keymaps.
 
 ### MN and move to next/previous word 
-Three is a problem with arrow navigation that left/right arrows jump only one character at a time. You can use `ctrl-left/right` (or `alt-left/right` on OSX) to jump between words. This is more useful and, arguably, should be default navigation for arrows. That's why in `alt-jl` moves caret to previous/next word. Single character navigation is still useful sometimes, so it's mapped to `alt-nm`. There is no particular reason for these letters except that they are located not too far from `ijkl`.
+Three is a problem with arrow navigation that left/right arrows jump only one character at a time. You can use `ctrl-left/right` (or `alt-left/right` on macOS) to jump between words. This is more useful and, arguably, should be the default navigation for arrows. That's why in `alt-jl` moves caret to previous/next word. Single character navigation is still useful sometimes, so it's mapped to `alt-nm`. There is no particular reason for these letters except that they are located not too far from `ijkl`.
 
 ### UO
-Moving to the start/end of line is another important part of navigation, so ideally it should mapped to keys not far from `ijkl`. For this reason `u` and `o` seem like a great choice.
+Moving to the start/end of line is another important part of navigation, so ideally it should be mapped to keys not far from `ijkl`. For this reason `u` and `o` seem like a great choice.
 
-Moving to the start of line is `u` because it is close to `j` and essentially also means moving caret left. And `o` is mapped to the end of line because it's about moving right, similar to `l` (there is an implicit assumption here that you're writing code left to right in English).
+Moving to the start of line is `u` because it is close to `j` and essentially also means moving caret left. And `o` is mapped to the end of line because it's about moving right, similar to `l` (there is an implicit assumption here that you're writing code left to right).
+
 
 ### FW
 The choice of `fw` letters mapped to page down/up was copied from [less](https://en.wikipedia.org/wiki/Less_(Unix)) and admittedly is somewhat arbitrary.
 
 
-## Conflicts with existing keymaps
-TBD
-
+## MacOS Caveats
 
-## OSX Caveats
-
-There are couple issues when using alt-ijkl shortcuts with built-in OSX keyboard layouts:
+There are few issues when using alt-ijkl shortcuts with built-in macOS keyboard layouts:
 1. dead keys cannot be used as IDE shortcuts (e.g. `alt-i` in US layout)
 2. if `alt-ik` are mapped to some character, then `Navigate to Class` action handles `alt-ik` shortcuts as both navigation up/down and entering a character.
 3. keys with certain output, when held down, trigger IDE action only once (e.g. `alt-i` with 'ˆ' output in US layout).
@@ -96,15 +92,15 @@ The first two issues can be solved by adding keyboard input source which doesn't
 To solve the third issue you can disable sticky keys feature by executing in shell `defaults write -g ApplePressAndHoldEnabled -bool false`. 
 
 
-## How to install OSX input source
+## How to install macOS input source
 
 On IDE startup the plugin will suggest to add keyboard input sources. In practice, this means that plugin will create `~/Library/Keyboard Layouts/ijkl-keys.bundle` directory with a bunch of files.
 
-After input sources were installed, open OSX `System Preferences -> Keyboard -> Input Sources` and click on `+` to add input sources.
+After input sources were installed, open macOS `System Preferences -> Keyboard -> Input Sources` and click on `+` to add input sources.
 
 Choose `U.S. - IJKL` or `British - IJKL` input source from English category and click `Add` button. (If you don't see these inputs, you might need to log out / log in or restart.)
 
-Now you can switch to new input source in IDE and use `alt-ijkl` shortcuts.
+Now you can switch to the new input source in IDE and use `alt-ijkl` shortcuts.
 
 
 ## How to hide "default" input source
@@ -116,4 +112,3 @@ If you're happy with custom layout and want to hide built-in layout from input s
  - remove the input source or input sources you want to disable from the `AppleEnabledInputSources` dictionary; 
    if there is an `AppleDefaultAsciiInputSource` key, remove it
  - restart
-