Merge pull request #1 from danra/patch-1

Update README.md with mostly some English fixes

README.md

@@ -4,11 +4,11 @@ The context of presenting right now is that we intend to prepare and submit a vi
 
 The problem is that Lamdu is somewhat challenging to present. Paul Chiusano's [article on incrementalism](https://pchiusano.github.io/2017-05-17/incrementalism.html) expands on this topic quite well.
 
-The gist of the problem is that Lamdu is a big and novel project with many aspects to desribe, but it's also essential to keep the presentation focused. We've got to this predicament as we've focused more on coding and less on presenting our research, in contrast to academics, which typically continually update on their advances so at any point there is only the recent new material to present.
+The gist of the problem is that Lamdu is a big and novel project with many aspects to describe, but it's also essential to keep the presentation focused. We got to this predicament as we've focused more on coding and less on presenting our research, in contrast to academics, who typically continually update on their advances so at any given point in time there is only the recent new material to present.
 
 ## Topics/Storylines
 
-Options for the main idea presented -
+Options for the main idea to present -
 
 ### Improvement upon IDEs
 
@@ -21,7 +21,7 @@ Modern programming has become a cooperation between the programmer and the compu
 
 #### Problem
 
-These are very useful, but unfortunately it works in gaps:
+These are very useful, but unfortunately only work intermittently:
 
 * When there are syntax errors the compiler cannot understand the program. No feedback at these states
 * None of the code will run when even a single part of it does not type-check
@@ -33,20 +33,20 @@ These are very useful, but unfortunately it works in gaps:
 
 How do we intend to tackle this goal? Formalize the intermediate and incomplete states of editing a program.
 
-* Feedback should work reliably also when the program is incomplete
+* Feedback should work reliably even when the program is incomplete
 * The model should allow for editing naturally as programmers currently do
 
-For this we have to depart from freely editing text. At first glance that might seem like a big problem, as text editing is a very intuitive and easily learnable interface. It turns out that the [full freedom of text](#Textual-freedom-taken-to-the-absurd) is not necessary, and we can create a text-like WYTIWYS interface that feels very natural.
+For this we have to depart from freely editing text. At first glance this might seem like a big problem, as text editing is a very intuitive and easily learnable interface. It turns out that the [full freedom of text](#Textual-freedom-taken-to-the-absurd) is not necessary, and we can create a text-like WYTIWYS interface that feels very natural.
 
 ## Scenes
 
 Ideas for possible "scenes"/parts which can be used to construct the presentation -
 
 ### Textual freedom taken to the absurd
 
-This shtick's goal is to provide an intuition that the complete freedom of textual editing is not needed.
+This shtick's goal is to provide the intuition for how complete freedom of textual editing is not needed.
 
-* Present animation of code written in random order (With syntax highlighting)
+* Present animation of code written in random order (with syntax highlighting)
 * Narrate that few programmers program this way
 * Extra "funny" video of a finger moving the cursor via the track-bar, then pressing a key, then going back to the track bar etc several times in sequence
 
@@ -68,8 +68,8 @@ Many things have changed since then which make things easier to explain:
 * Records as multiple params sugar makes code look more familiar
 * We display the setting of which annotation mode is currently selected
 * No need to press space to apply a transformation. Can just start typing the operator or function to use
-* In general we've reached the WYTIWYS term/concept, which explains succintly that the interface is simply still just typing text
-* No need to delve into the mechanisms of hole results prioritization as Lamdu has a lot more interesting things to describe now
+* In general we've reached the WYTIWYS term/concept, which explains succinctly that the interface is simply still just typing text
+* No need to delve into the mechanisms of hole results prioritization as Lamdu has a lot of more interesting things to describe now
 * Where the previous video emphasized feedback from types, currently one might get more easily understandable feedback via values
 
 Also some things have progressed in the world as well: