Fix README typos (#49)

README.md

@@ -157,8 +157,8 @@ Think of your frontend as a puppet, and the backend as the hand within it — th
 
 Building an application this way has a number of significant advantages:
 
-- you only need to write code in one place to build a new feature — add a new view, change the behavior of an existing view or alter the URL structure
-- deploying the front and backend can be completely decoupled, provided the frontend knows how to render all the components the backend is going to ask it to use, you're good to go
+- You only need to write code in one place to build a new feature — add a new view, change the behavior of an existing view or alter the URL structure
+- Deploying the front and backend can be completely decoupled, provided the frontend knows how to render all the components the backend is going to ask it to use, you're good to go
 - You should be able to reuse a rich set of opensource components, they should end up being better tested and more reliable than anything you could build yourself, this is possible because the components need no context about how they're going to be used (note: since FastUI is brand new, this isn't true yet, hopefully we get there)
 - We can use Pydantic, TypeScript and JSON Schema to provide guarantees that the two sides are communicating with an agreed schema (note: this is not complete yet, see [#18](https://github.com/samuelcolvin/FastUI/issues/18))
 
@@ -170,7 +170,7 @@ Of course, this principle shouldn't be limited to Python and React applications
 
 This could mean:
 
-- implementing web a frontend using another JS framework like Vue — lots of work, limited value IMHO
-- implementing web a frontend using an edge server, so the browser just sees HTML — lots of work but very valuable
-- implementing frontends for other platforms like mobile or IOT — lots of work, no idea if it's actually a good idea?
-- implementing the component models in another language like Rust or Go — since there's actually not that much code in the backend, so this would be a relatively small and mechanical task
+- Implementing a web frontend using another JS framework like Vue — lots of work, limited value IMHO
+- Implementing a web frontend using an edge server, so the browser just sees HTML — lots of work but very valuable
+- Implementing frontends for other platforms like mobile or IOT — lots of work, no idea if it's actually a good idea?
+- Implementing the component models in another language like Rust or Go — since there's actually not that much code in the backend, so this would be a relatively small and mechanical task