Checks & cleanups

packages/rpc-provider/README.md

@@ -4,9 +4,9 @@ Generic transport providers to handle the transport of method calls to and from
 
 ## Provider Selection
 
-There are two flavours of the providers provided, one allowing for using HTTP as a transport machanism, the other using WebSockets. It is generally recommended to use the [[WsProvider]] since in addition to standard calls, it allows for subscriptions where nes changes can be pushed from the node to the client.
+There are two flavours of the providers provided, one allowing for using HTTP as a transport machanism, the other using WebSockets. It is generally recommended to use the [[WsProvider]] since in addition to standard calls, it allows for subscriptions where all changes to state can be pushed from the node to the client.
 
-Both providers are usable (as is the API), in both browser-based and Node.js environments. Polyfills for unsupported functionality is automatically applied based on feature-detection.
+Both providers are usable (as is the API), in both browser-based and Node.js environments. Polyfills for unsupported functionality are automatically applied based on feature-detection.
 
 ## Usage
 
@@ -18,7 +18,7 @@ yarn add @polkadot/rpc-provider
 
 WebSocket Initialisation -
 
-```js
+```javascript
 import WsProvider from '@polkadot/rpc-provider/ws';
 
 // this is the actual default endpoint
@@ -30,7 +30,7 @@ console.log('client version', version);
 
 HTTP Initialisation -
 
-```js
+```javascript
 import { HttpProvider } from '@polkadot/rpc-provider';
 
 // this is the actual default endpoint