Fix paf31#105, remove references to psc

Author: paf31

text/chapter10.md

@@ -299,7 +299,7 @@ exports.encodeURIComponent = encodeURIComponent;
 
 Pulp will find `.js` files in the `src` directory, and provide them to the compiler as foreign Javascript modules.
 
-Javascript functions and values are exported from foreign Javascript modules by assigning them to the `exports` object just like a regular CommonJS module. The `psc` compiler treats this module like a regular CommonJS module, and simply adds it as a dependency to the compiled
+Javascript functions and values are exported from foreign Javascript modules by assigning them to the `exports` object just like a regular CommonJS module. The `purs` compiler treats this module like a regular CommonJS module, and simply adds it as a dependency to the compiled
 PureScript module. However, when bundling code for the browser with `psc-bundle` or `pulp build -O --to`, it is very important to follow the
 pattern above, assigning exports to the `exports` object using a property assignment. This is because `psc-bundle` recognizes this format,
 allowing unused Javascript exports to be removed from bundled code.

text/chapter5.md

@@ -299,7 +299,7 @@ Functions which return a value for any combination of inputs are called _total_
 
 It is generally considered better to define total functions where possible. If it is known that a function does not return a result for some valid set of inputs, it is usually better to return a value with type `Maybe a` for some `a`, using `Nothing` to indicate failure. This way, the presence or absence of a value can be indicated in a type-safe way.
 
-The PureScript compiler will generate an error if it can detect that your function is not total due to an incomplete pattern match. The `unsafePartial` function can be used to silence these errors (if you are sure that your partial function is safe!) If we removed the call to the `unsafePartial` function above, then `psc` would generate the following error:
+The PureScript compiler will generate an error if it can detect that your function is not total due to an incomplete pattern match. The `unsafePartial` function can be used to silence these errors (if you are sure that your partial function is safe!) If we removed the call to the `unsafePartial` function above, then the compiler would generate the following error:
 
 ```text
 A case expression could not be determined to cover all inputs.

text/chapter8.md

@@ -505,7 +505,7 @@ This time we have to choose `eff2` to be `(random :: RANDOM | eff)`.
 
 The point is that the types of `random` and `logShow` indicate the side-effects which they contain, but in such a way that other side-effects can be _mixed-in_, to build larger computations with larger sets of side-effects.
 
-Note that we don't have to give a type for `main`. `psc` will find a most general type for `main` given the polymorphic types of `random` and `logShow`.
+Note that we don't have to give a type for `main`. The compiler will find a most general type for `main` given the polymorphic types of `random` and `logShow`.
 
 ## The Kind of Eff
 
@@ -750,7 +750,7 @@ simulate x0 v0 time = runPure $ runST do
   pure final.x
 ```
 
-then the `psc` compiler will notice that the reference cell is not allowed to escape its scope, and can safely turn it into a `var`. Here is the generated JavaScript for the body of the call to `runST`:
+then the compiler will notice that the reference cell is not allowed to escape its scope, and can safely turn it into a `var`. Here is the generated JavaScript for the body of the call to `runST`:
 
 ```javascript
 var ref = { x: x0, v: v0 };