Merge pull request #9 from rosborne132/add-pr-template

update README.md and add github pr template

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+## Summary of changes
+
+Fixes #123.
+
+Describe the reason for the change.
+
+Add a list of changes, and note any that might need special attention during review. Help us understand what this pull request is changing and why it's needed.

README.md

@@ -5,7 +5,7 @@ Javascript bindings.
 
 ## Prerequisites
 
-- Node 18 or higher ([https://nodejs.org/en/download](https://nodejs.org/en/download))
+- Node 17 or higher ([https://nodejs.org/en/download](https://nodejs.org/en/download))
 
 ## Getting Started
 Follow these steps to set up and run the JS Bindings project on your local machine:
@@ -29,12 +29,22 @@ make build
 make install
 ```
 
+Right now, files will be installed in the `./install` directory. This is hardcoded.
+
+5. Run unit tests
+```bash
+npm run test
+```
+
+[Jest](https://jestjs.io/) is used as a the test runner.
+Additional arguments can be passed to Jest like this: `npm test -- <additional arguments>`.
+
 ## State of the project
 
 This is still a work in progress for now, but the base is there. That is:
 
 * `SerializableObject`, `SerializableObjectWithMetadata`, ability to subclass them and
-  register custom schemas from Javascripts.
+  register custom schemas from Javascript.
 * `Composable`, `Marker`, `Clip` (partial) and `SerializableCollection` (partial).
 * Serialization and deserialization is mostly working, though it needs more work to
   cover everything.
@@ -49,11 +59,6 @@ This is still a work in progress for now, but the base is there. That is:
 * Tests live in the [tests](./tests) directory.
 * Tests are run automatically on every push using GitHub Actions.
 
-Right now, files will be installed in the `./install` directory. This is hardcoded.
-
-To run the tests, run `npm test`. [Jest](https://jestjs.io/) is used as a the test runner.
-Additional arguments can be passed to Jest like this: `npm test -- <additional arguments>`.
-
 ## TODO
 
 Most TODOs are documented in the code. Search for `TODO:` and you will find everything that