README.md updates (#390)

Corrected a few typos

Author: thephez

README.md

@@ -11,11 +11,11 @@ http://freeopcua.github.io/, https://github.com/FreeOpcUa/python-opcua
 
 OPC UA binary protocol implementation is quasi complete and has been tested against many different OPC UA stacks. API offers both a low level interface to send and receive all UA defined structures and high level classes allowing to write a server or a client in a few lines. It is easy to mix high level objects and low level UA calls in one application.
 
-Most low level code is autogenerated from xml specification, thus adding missing functionnality to client or server is often trivial.
+Most low level code is autogenerated from xml specification, thus adding missing functionality to client or server is often trivial.
 
 Using Python > 3.4 the dependencies are cryptography, dateutil and pytz. If using python 2.7 or pypy < 3 you also need to install enum34, trollius(asyncio), and futures(concurrent.futures), with pip for example.
 
-coveryage.py reports a test coverage of over 90% of code, most of non-tested code is autogenerate code that is not used yet.
+coveryage.py reports a test coverage of over 90% of code, most of non-tested code is autogenerated code that is not used yet.
 
 Some documentation is available at http://python-opcua.readthedocs.org/en/latest/
 
@@ -44,7 +44,7 @@ How to generate certificate: https://github.com/FreeOpcUa/python-opcua/tree/mast
 Client: what works:
 * connection to server, opening channel, session
 * browsing and reading attributes value
-* gettings nodes by path and nodeids
+* getting nodes by path and nodeids
 * creating subscriptions
 * subscribing to items for data change
 * subscribing to events
@@ -67,8 +67,8 @@ Client: what is not implemented yet
 Server: what works:
 * creating channel and sessions
 * read/set attributes and browse
-* gettings nodes by path and nodeids
-* autogenerate addres space from spec
+* getting nodes by path and nodeids
+* autogenerate address space from spec
 * adding nodes to address space
 * datachange events
 * events
@@ -87,12 +87,12 @@ Server: what is not implemented
 * XML protocol
 * views
 * localized text features
-* better securty model with users and password
+* better security model with users and password
 
 
 Server: Running on a Raspberry Pi
 
-Setting up the standard address-space from XML is the most time-consuming step of the startup process which may lead to long startup times on less powerful devices like a Raspberry Pi. By passing a path to a cache-file to the server constructor, a shelve holding the address space will be created during the first startup. All following startups will make use of the cache-file which leads to significantly better startup performance (~3.5 vs 125 seconds on a Raspbery Pi Model B).
+Setting up the standard address-space from XML is the most time-consuming step of the startup process which may lead to long startup times on less powerful devices like a Raspberry Pi. By passing a path to a cache-file to the server constructor, a shelve holding the address space will be created during the first startup. All following startups will make use of the cache-file which leads to significantly better startup performance (~3.5 vs 125 seconds on a Raspberry Pi Model B).
 
 # Development