diff --git a/README.md b/README.md index f3f5fe7..e5bac91 100644 --- a/README.md +++ b/README.md @@ -126,11 +126,11 @@ const sanFrancisco = citySchema.parse(sanFranciscoBuf) `sanFrancisco` will be similar to the object we built `sanFranciscoBuf` from. It will have an array of building objects. -### Utilizing StreamingAbstractor +## Utilizing StreamingAbstractor -StreamingAbstractors allow us to create duplex, event-based streaming systems for applications. +`StreamingAbstractor`s allow us to create duplex, event-based streaming systems for applications. -Let's create a StreamingAbstractor. +Let's create a `StreamingAbstractor`. ```js const myAbstractor = new StreamingAbstractor() @@ -148,11 +148,11 @@ myAbstractor.register('login', new Schema([ ])) ``` -Above we've registered an event called 'login' in our abstractor. Now it can recieve login events from a stream connected to another StreamingAbstractor. +Above we've registered an event called 'login' in our abstractor. Now it can recieve login events from a stream connected to another `StreamingAbstractor`. -#### Recieving Events Through StreamingAbstractor +### Recieving Events Through StreamingAbstractor -Now that we have a StreamingAbstractor (`myAbstractor`) with the `login` event registered, we'll listen for `login` on our end. +Now that we have a `StreamingAbstractor` (`myAbstractor`) with the `login` event registered, we'll listen for `login` on our end. ```js myAbstractor.on('login', (data) => { @@ -160,7 +160,7 @@ myAbstractor.on('login', (data) => { }) ``` -#### Sending Events Through StreamingAbstractor +### Sending Events Through StreamingAbstractor Because we've registered the `login` event, we can send `login` events using `myAbstractor`. diff --git a/package.json b/package.json index 6547fe8..aca28fe 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "protocore", - "version": "1.1.1", + "version": "1.1.2", "description": "Specify and deploy custom binary protocol structures in Node", "main": "index.js", "scripts": {