Update tcell to include true color fix

[micro.git] / runtime / help / help.md

diff --git a/runtime/help/help.md b/runtime/help/help.md
index 094d588a147234a5a79729d94ec6ef604afc8cca..eb9b0a1a0850067dbd2581bb86d12c9af554583e 100644 (file)
--- a/runtime/help/help.md
+++ b/runtime/help/help.md
@@ -1,39 +1,38 @@
 # Micro help text
 
 # Micro help text
 

-Thank you for downloading and using micro.
-

 Micro is a terminal-based text editor that aims to be easy to use and intuitive, 
 while also taking advantage of the full capabilities of modern terminals.
 
 Micro is a terminal-based text editor that aims to be easy to use and intuitive, 
 while also taking advantage of the full capabilities of modern terminals.
 

-If you want to see all the keybindings press CtrlE and type `help keybindings`.
-
-See the next section for more information about documentation and help.
+To open the command bar, press Ctrl-e. This enables a `>` prompt for typing
+commands. From now on when the documentation says to run a command such as
+`> help`, this means press Ctrl-e and type `help` (and press enter to execute
+the command).

 
 

+For a list of the default keybindings run `> help defaultkeys`.
+For more information on keybindings see `> help keybindings`.

 
 ## Quick-start
 
 
 ## Quick-start
 

-Press CtrlQ to quit, and CtrlS to save. Press CtrlE to start typing commands and
+Press Ctrl-q to quit, and Ctrl-s to save. Press Ctrl-e to start typing commands and

 you can see which commands are available by pressing tab, or by viewing the help
 you can see which commands are available by pressing tab, or by viewing the help

-topic `> help commands`. When I write `> ...` I mean press Ctrl0E and then type
-whatever is there. 
+topic `> help commands`.

 
 

-Move the cursor around with the mouse or the arrow keys. Type
+Move the cursor around with the mouse or the arrow keys. Run

 `> help defaultkeys` to  get a quick, easy overview of the default hotkeys and
 what they do. For more info on rebinding keys, see type `> help keybindings`.
 
 If the colorscheme doesn't look good, you can change it with
 `> set colorscheme ...`. You can press tab to see the available colorschemes, or
 `> help defaultkeys` to  get a quick, easy overview of the default hotkeys and
 what they do. For more info on rebinding keys, see type `> help keybindings`.
 
 If the colorscheme doesn't look good, you can change it with
 `> set colorscheme ...`. You can press tab to see the available colorschemes, or

-see more information with `> help colors`.
+see more information about colorschemes and syntax highlighting with `> help colors`.

 
 

-Press CtrlW to move between splits, and type `> vsplit filename` or
+Press Ctrl-w to move between splits, and type `> vsplit filename` or

 `> hsplit filename` to open a new split.
 
 `> hsplit filename` to open a new split.
 

-

 ## Accessing more help
 
 ## Accessing more help
 

-Micro has a built-in help system much like Vim's (although less extensive).
+Micro has a built-in help system which can be accessed with the `help` command.

 
 

-To use it, press CtrlE to access command mode and type in `help` followed by a
+To use it, press Ctrl-e to access command mode and type in `help` followed by a

 topic. Typing `help` followed by nothing will open this page.
 
 Here are the possible help topics that you can read:
 topic. Typing `help` followed by nothing will open this page.
 
 Here are the possible help topics that you can read:


@@ -51,8 +50,7 @@ Here are the possible help topics that you can read:
 * colors: Explains micro's colorscheme and syntax highlighting engine and how to
   create your own colorschemes or add new languages to the engine
 
 * colors: Explains micro's colorscheme and syntax highlighting engine and how to
   create your own colorschemes or add new languages to the engine
 

-For example, to open the help page on plugins you would press CtrlE and type
-`help plugins`.
+For example, to open the help page on plugins you would run `> help plugins`.

 
 I recommend looking at the `tutorial` help file because it is short for each
 section and gives concrete examples of how to use the various configuration
 
 I recommend looking at the `tutorial` help file because it is short for each
 section and gives concrete examples of how to use the various configuration