Guidance for using & configuring the default CLI text editor

[psokolhessner]

Is your feature request related to a problem? Please describe. The default text editor (vi) for git commit requests is a little opaque/frustrating to use esp. for people who don't use CLI-based text editors very often.

Describe the solution you'd like

• A brief description of how to use vi, as well as a reference to this page, which I personally found helpful: https://www.howtogeek.com/102468/a-beginners-guide-to-editing-text-files-with-vi/
• Guide on how to configure the default text editor to be something more accessible (unsure what are good options here, but I've found pico to be relatively easy/straightforward).
• List of a few recommended CLI text editors w/ a single sentence describing what they're like to work with (i.e. strengths/weaknesses, focused on ease of use).

Additional context It's possible others' default CLI text editor is not vi? In which case the more general solution is preferred here (description of how to configure a personal choice of default CLI text editor; and a listing of some particularly good options)

[aridyckovsky]

Put together a section on vim, plus a quick couple of lines on Atom and Sublime. More importantly, in the "Git: Install & Setup" section, global configurations include setting a default text editor.