Update references to psc-bundle to 'purs bundle'. (documentationjs#233)

Author: StephenWakely

CONTRIBUTORS.md

@@ -51,6 +51,7 @@ If you would prefer to use different terms, please use the section below instead
 | [@shuhei](https://github.com/shuhei) | Shuhei Kagawa | [CC BY-NC-SA 3.0](https://creativecommons.org/licenses/by-nc-sa/3.0/deed) |
 | [@owickstrom](https://github.com/owickstrom) | Oskar Wickström | [CC BY-NC-SA 3.0](https://creativecommons.org/licenses/by-nc-sa/3.0/deed) |
 | [@soupi](https://github.com/soupi) | Gil Mizrahi | [CC BY-NC-SA 3.0](https://creativecommons.org/licenses/by-nc-sa/3.0/deed) |
+| [@FungusHumungus](https://github.com/FungusHumungus) | Stephen Wakely | [CC BY-NC-SA 3.0](https://creativecommons.org/licenses/by-nc-sa/3.0/deed) |
 
 ### Contributors using Modified Terms
 

guides/FFI-Tips.md

@@ -71,7 +71,7 @@ exports.doSomethingImpl = function(fn, x) {
 };
 ```
 
-Calling these functions directly in the FFI code isn't recommended as it makes the code brittle to changes in the code generator. Additionally, doing this can cause problems when using `psc-bundle` for dead code elimination.
+Calling these functions directly in the FFI code isn't recommended as it makes the code brittle to changes in the code generator. Additionally, doing this can cause problems when using `purs bundle` for dead code elimination.
 
 The recommended approach is to add extra arguments to your FFI-defined function to accept the functions you need to call as arguments:
 

guides/FFI.md

@@ -39,7 +39,7 @@ Test.gcd(15)(20);
 
 Here, I am assuming that the code was compiled with `psc`, which compiles PureScript modules to CommonJS modules. For that reason, I was able to reference the `gcd` function on the `Test` object, after importing the `Test` module using `require`.
 
-You might also like to bundle JavaScript code for the browser, using `psc-bundle`. In that case, you would access the `Test` module on the global namespace, which defaults to `PS`:
+You might also like to bundle JavaScript code for the browser, using `purs bundle`. In that case, you would access the `Test` module on the global namespace, which defaults to `PS`:
 
 ``` javascript
 var Test = PS.Test;

guides/PureScript-Without-Node.md

@@ -59,14 +59,14 @@ Compiling Effect.Console
 
 #### Bundling JavaScript for the Browser
 
-To bundle the generated Javascript code, we will use the `psc-bundle` tool, which ships with the PureScript compiler binary distribution.
+To bundle the generated Javascript code, we will use `purs bundle`.
 
-`psc-bundle` takes a collection of CommonJS module files as input, and generates a single JavaScript file.
+`purs bundle` takes a collection of CommonJS module files as input, and generates a single JavaScript file.
 
-Run `psc-bundle` with the following arguments:
+Run `purs bundle` with the following arguments:
 
 ```text
-$ psc-bundle output/*/{index,foreign}.js --module Main --main Main
+$ purs bundle output/*/{index,foreign}.js --module Main --main Main
 ```
 
 The `--module` argument specifies an _entry-point_ module, which will be used to determine dead code which can be removed. For our purposes, we only care about bundling the CommonJS module corresponding to the Main PureScript module and its transitive dependencies.