Just some textual improvements

Author: Cies Breijs

LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2015, TBD
+Copyright (c) 2015-2016, TBD
 
 All rights reserved.
 

README.md

@@ -11,39 +11,38 @@
 [license]: https://github.com/haskell/haskell-ide-engine/blob/master/LICENSE
 
 
-This project aims to be the __universal IDE interface__ to __all haskell tools__, proving a __full-featured and easy to query ide-backend__.
+This project aims to be __the universal interface__ to __a growing number of Haskell tools__, proving a __full-featured and easy to query backend__ for editors and IDEs that require Haskell-specific functionality.
 
-Features: (planned)
+Planned features:
 
- - [ ] cabal / stack project `Configuration` and `Compilation`
- - [ ] Errors Checking, Warnings, Linter, Dead code detection
- - [ ] Refactoring tools, Code beautify, Auto-apply suggestion
+ - [ ] Cabal / Stack project configuration and compilation
+ - [ ] Error checking, warnings, linter and dead code detection
+ - [ ] Refactoring tools, code beautification, auto-apply suggestion
  - [ ] Code generation
  - [ ] Run testing Suite, check coverage
  - [ ] Autocompletion
  - [ ] Get type at point
- - [ ] Jump to definition, find Usages, Browse documentation, Generate ctags
+ - [ ] Jump to definition, find usages, browse documentation, generate ctags
  - [ ] REPL
 
 
-### Is this _again_ an other `ghc-mod` or `ide-backend` like project ?
-
-No:
+### This is *not* yet another [`ghc-mod`](https://github.com/kazu-yamamoto/ghc-mod) or [`ide-backend`](https://github.com/fpco/ide-backend) project
 
  > Both the ghc-mod and ide-backend maintainers have agreed to contribute code to this new repository and then rebase the old repos on this. The reason we're using a new repo instead of modifying one of the existing ones is so that the existing projects experience no disruption during this migration process. If this was a new set of people starting a new project without support from existing projects, I'd agree with you. But Alan's reached out to existing players already, which is an important distinction.
 
-This project doesn't start from scratch:
+This project is not started from scratch:
 
 1. See why [we should supersede previous tools](/docs/Challenges.md)
-2. Check the [list of existing tools / features ](/docs/Tools.md)
-3. See more [other tools / ide for inspiration](/docs/Inspirations.md)
+2. Check the [list of existing tools and functionality](/docs/Tools.md)
+3. See more [other tools and IDEs for inspiration](/docs/Inspirations.md)
+
 
-## It's time to join the project !
+## It's time to join the project!
 
-:heart: Haskell tooling dream is near, we need your help ! :heart:
+:heart: Haskell tooling dream is near, we need your help! :heart:
 
- - Register in our [google group mailing list](https://groups.google.com/forum/#!forum/haskell-ide)
- - Join our IRC channel at `#haskell-ide-engine` on `freenode`.
+ - Register in [our google group mailing list](https://groups.google.com/forum/#!forum/haskell-ide).
+ - Join [our IRC channel](http://webchat.freenode.net/?channels=haskell-ide-engine) at `#haskell-ide-engine` on `freenode`.
  - Fork this repo and hack as much as you can.
  - Ask @alanz or @hvr to join the project.
 
@@ -52,43 +51,46 @@ This project doesn't start from scratch:
 
 ## Architecture
 
-1. __BIOS layer__:
+Below you find a short overview of the main architectural layers of `haskell-ide-engine`.
+For more info have a look in [the docs folder](/docs) at the root of this project, especially:
 
-    ghc-mod stays an AGPL project, and is used for its "awesome sauce" in terms of
-    the BIOS functions that it does so well. This interface is
-    [straightforward to use](http://alanz.github.io/haskell%20refactorer/2015/10/02/ghc-mod-for-tooling),
-    and if a license-constrained user wants to do something else it is also easy to
-    replace, if there is strong control of the operating environment.
+ - The [Architecture discussion](/docs/Architecture.md)
+ - The [Protocol discussion](/docs/Protocol.md)
+ - The [Design discussion](/docs/Design.md)
 
-2. __Plugin layer__:
+#### 1. BIOS layer
 
-    A layer providing a point to integrate tools and existing functions, probably
-    including ghci.
+[`ghc-mod`](https://github.com/kazu-yamamoto/ghc-mod) stays an AGPL project,
+and is used for its "awesome sauce" in terms of
+the BIOS functions that it does so well. This interface is
+[straightforward to use](http://alanz.github.io/haskell%20refactorer/2015/10/02/ghc-mod-for-tooling),
+and if a license-constrained user wants to do something else it is also easy to
+replace, if there is strong control of the operating environment.
 
-3. __IDE interfacing layer__:
+#### 2. Plugin layer
 
-    This provides a set of logical channels that can be integrated into standard
-    IDEs. The details still need to be worked out, but I would imagine something
-    like a channel for querying information about a project, one for a ghci session,
-    and whatever others are needed. These logical channels can then run over
-    whatever transport is appropriate to the specific IDE being integrated.
+A layer providing a point to integrate tools and existing functions, probably
+including ghci.
 
-    According to [#2](https://github.com/haskell/haskell-ide-engine/issues/2) it seems the
-    consensus is toward (re) using the Idris protocol, as the languages are similar
-    enough and it offers cross-IDE support already.
+#### 3. IDE interfacing layer
 
-    The Plugin and IDE layers are very fuzzy at this point, and there has been some
-    discussion on IRC around it. These layers may well live in a single repository
-    (this one), as two separate layers or just be a feature of how
-    haskell-ide-engine is built.
+This provides a set of logical channels that can be integrated into standard
+IDEs. The details still need to be worked out, but I would imagine something
+like a channel for querying information about a project, one for a ghci session,
+and whatever others are needed. These logical channels can then run over
+whatever transport is appropriate to the specific IDE being integrated.
 
-You can see more info [in the docs folder](/docs) at the root of the project, especially:
+According to [#2](https://github.com/haskell/haskell-ide-engine/issues/2) it seems the
+consensus is toward (re-)using the Idris protocol, as the languages are similar
+enough and it offers cross-IDE support already.
+
+The __Plugin layer__ and __IDE layer__ are very fuzzy at this point, and there has been some
+discussion on IRC around it. These layers may well live in a single repository
+(this one), as two separate layers or just be a feature of how
+`haskell-ide-engine` is built.
 
- - The [Architecture discussion](/docs/Architecture.md)
- - The [Protocol discussion](/docs/Protocol.md)
- - The [Design discussion](/docs/Design.md)
 
 
 ## Documentation
 
-All the documentation is [in the docs folder](/docs) at the root of the project.
+All the documentation is in [the docs folder](/docs) at the root of this project.

haskell-ide-engine.cabal

@@ -5,7 +5,7 @@ description:         Please see README.md
 homepage:            http://github.com/githubuser/haskell-ide-engine#readme
 license:             BSD3
 license-file:        LICENSE
-author:              Many,TBD when we release
+author:              Many, TBD when we release
 maintainer:          [email protected] (for now)
 copyright:           2015 TBD
 category:            Web