Fabn 1693 reset snapshot 1.4.18 (#422)

Signed-off-by: lesleyannj <lesleyannj@hotmail.com>

Author: lesleyannjordan

CHANGELOG.md

@@ -7,7 +7,7 @@ Thu Jan 14 09:47:48 EST 2021
 * [02fe7d8d](https://github.com/hyperledger/fabric-sdk-node/commit/02fe7d8d) [[FABN-1591](https://jira.hyperledger.org/browse/FABN-1591)] Document Release Process (#409)
 * [3d45bc20](https://github.com/hyperledger/fabric-sdk-node/commit/3d45bc20) [[FABN-1591](https://jira.hyperledger.org/browse/FABN-1591)] Document Release Process (#404)
 
-## 1.4.16
+## v1.4.16
 Wed 16 Dec 17:22:55 GMT 2020
 
 * [bdb6c0a0](https://github.com/hyperledger/fabric-sdk-node/commit/bdb6c0a0) [[FABN-1680](https://jira.hyperledger.org/browse/FABN-1680)] Update dependency (#396)

RELEASING.md

@@ -11,7 +11,7 @@ Check top level `package.json` file properties **version** and **tag** are one a
 - Create a jira for publish  - publish v1.4.16.
 - Run `scripts/changelog.sh` script from the project root directory.  It takes two arguments; last release commit hash and next release version number - `./scripts/changelog.sh <commithash> 1.4.16`.
 - Update the **version** and **tag** properties in the top-level `package.json` file to be the appropriate values - next release version *1.4.16* and release npm tag *latest-1.4*.
-- Create `release_notes/v1.4.16.txt` file with appropriate text - "This is a mainenance release containing bug fixes".
+- Create `release_notes/v1.4.16.txt` file with appropriate text - "This is a maintenance release containing bug fixes".
 - Git add, submit, push and create PR.  The build once the PR is merged will do the npm publishing.  Check it has npm published at https://www.npmjs.com/package/fabric-client and https://www.npmjs.com/package/fabric-common
 
 ## Tag Release

package.json

@@ -1,7 +1,7 @@
 {
   "name": "fabric-sdk-node",
-  "version": "1.4.17",
-  "tag": "latest-1.4",
+  "version": "1.4.18-snapshot",
+  "tag": "unstable-1.4",
   "main": "index.js",
   "repository": {
     "type": "git",