Fix typos and minor doc changes (#535)

Co-authored-by: Jake Champion <[email protected]>

Author: andrebenedetti

CHANGELOG.md

@@ -25,7 +25,7 @@ And this is the change that would need to be made for constructing an instance o
 ```
 
 
-Here is a full example of migrating an applicatin from ObjectStore to KVStore:
+Here is a full example of migrating an application from ObjectStore to KVStore:
 ```diff
 /// <reference types="@fastly/js-compute" />
 

DEVELOPMENT.md

@@ -18,7 +18,7 @@ to pull down or update submodules.
 
 To build from source, you need to ensure that the headers and object files for the [SpiderMonkey JavaScript engine](https://spidermonkey.dev/) are available. It's recommended to download pre-built object files:
 ```sh
-(cd runtime/spidermonkey && sh download-engine.sh)
+(cd runtime/spidermonkey && bash download-engine.sh)
 ```
 
 

documentation/docs/migration-guide/index.mdx

@@ -26,7 +26,7 @@ And this is the change that would need to be made for constructing an instance o
 ```
 
 
-Here is a full example of migrating an applicatin from ObjectStore to KVStore:
+Here is a full example of migrating an application from ObjectStore to KVStore:
 ```diff
 /// <reference types="@fastly/js-compute" />
 

documentation/versioned_docs/version-2.0.0/migration-guide/index.mdx

@@ -26,7 +26,7 @@ And this is the change that would need to be made for constructing an instance o
 ```
 
 
-Here is a full example of migrating an applicatin from ObjectStore to KVStore:
+Here is a full example of migrating an application from ObjectStore to KVStore:
 ```diff
 /// <reference types="@fastly/js-compute" />
 

js-compute-runtime-cli.js

@@ -21,11 +21,11 @@ if (version) {
   await printHelp();
 } else {
   // This is a dynamic import because this import will throw an error
-  // if if does not have a pre-compiled version of Wizer available the platform 
+  // if it does not have a pre-compiled version of Wizer available in the platform 
   // running the CLI. In that situation, we would still like the 
   // js-compute-runtime cli's --version and --help flags to work as
   // it could be that the user is using an older version of js-compute-runtime
-  // and a newer version does support the platform they are using.
+  // and a newer version does not support the platform they are using.
   const {compileApplicationToWasm} = await import('./src/compileApplicationToWasm.js')
   await compileApplicationToWasm(input, output, wasmEngine, enableExperimentalHighResolutionTimeMethods);
   if (component) {