Fix misspellings/grammar in README

This commit is contained in:
davertron 2014-02-21 13:57:35 -05:00
parent 3ecece8f67
commit 940f95680d

View File

@ -23,9 +23,9 @@ Neovim is a project that seeks to aggressively refactor vim source code in order
By achieving those goals new developers will soon join the community, consequently improving the editor for all users. By achieving those goals new developers will soon join the community, consequently improving the editor for all users.
It is important to empathise that this is not a project to rewrite vim from the scratch or transform it into an IDE(though the new features provided will enable IDE-like distributions of the editor). The changes implemented here should have little impact on vim's editing model or vimscript in general. Most vimscript plugins should continue to work normally. It is important to emphasize that this is not a project to rewrite vim from scratch or transform it into an IDE (though the new features provided will enable IDE-like distributions of the editor). The changes implemented here should have little impact on vim's editing model or vimscript in general. Most vimscript plugins should continue to work normally.
The following topics contains brief explanations of the major changes(and motivations) that will be performed in the first iteration: The following topics contain brief explanations of the major changes (and motivations) that will be performed in the first iteration:
* <a href="#build"><b>Migrate to a cmake-based build</b></a> * <a href="#build"><b>Migrate to a cmake-based build</b></a>
* <a href="#legacy"><b>Legacy support and compile-time features</b></a> * <a href="#legacy"><b>Legacy support and compile-time features</b></a>
@ -128,7 +128,7 @@ vim -> gui: {"method": "redraw", "params": {"clientId": 1, "lines": {"1": "Hello
This new GUI architecture creates many interesting possibilities: This new GUI architecture creates many interesting possibilities:
- Modern GUIs written in high-level programming languages that integrate better with the operating system. We can have GUIs written using C#/WPF on Windows or Ruby/Cocoa on Mac, for example. - Modern GUIs written in high-level programming languages that integrate better with the operating system. We can have GUIs written using C#/WPF on Windows or Ruby/Cocoa on Mac, for example.
- Plugins will be able emit custom events that may be handled directly by GUIs. This will enable the implementaton of advanced features such as sublime's minimap. - Plugins will be able to emit custom events that may be handled directly by GUIs. This will enable the implementaton of advanced features such as sublime's minimap.
- A multiplexing daemon could keep neovim instances running in a headless server, while multiple remote GUIs could attach/detach to share editing sessions. - A multiplexing daemon could keep neovim instances running in a headless server, while multiple remote GUIs could attach/detach to share editing sessions.
- Simplified headless testing. - Simplified headless testing.
- Embedding the editor into other programs. In fact, a GUI can be seen as a program that embeds neovim. - Embedding the editor into other programs. In fact, a GUI can be seen as a program that embeds neovim.
@ -166,7 +166,7 @@ Here's a list of things that have been done so far:
- Files were processed with [uncrustify](http://uncrustify.sourceforge.net/) to normalize source code formatting. - Files were processed with [uncrustify](http://uncrustify.sourceforge.net/) to normalize source code formatting.
- The autotools build system was replaced by [cmake](http://www.cmake.org/) - The autotools build system was replaced by [cmake](http://www.cmake.org/)
and of what is being currently worked on: and what is currently being worked on:
- Port all IO to libuv - Port all IO to libuv