Update 'Style Guide' to reflect Spago as recommended build tool (#297)

Author: mbbx6spp

guides/Style-Guide.md

@@ -4,7 +4,7 @@ The PureScript core libraries are good examples of how to put these guidelines i
 
 ## Build Tools
 
-- Consider using a one-step build tool such as Pulp or `gulp-purescript` to make your build as simple as possible for end-users.
+- Consider using a one-step build tool such as [Spago](https://github.com/purescript/spago) to make your build as simple as possible for end-users.
 - Document build steps for compilation, testing and documentation clearly in your `README` file.
 
 ## Documentation
@@ -41,17 +41,16 @@ It was previously common to include Markdown documentation generated by `psc-doc
     sudo: required
     node_js: 6
     install:
-      - npm install purescript pulp bower -g
-      - bower install
+      - npm install purescript spago -g
     script:
-      - pulp build && pulp test
+      - spago build && spago test
     ```
 
 - Display the Travis badge in your `README` file so that the build status is visible.
 
 ## Publishing
 
-- Share your library on [Bower](http://bower.io/search/?q=purescript), prefixing the name of your library with `purescript-` so others can find your work. 
+- Share your library on [Bower](http://bower.io/search/?q=purescript), prefixing the name of your library with `purescript-` so others can find your work.
   - Bower works with git tags, but does not require any present tags to publish. Please run `bower version 0.0.0` and push tags for your initial release (this prevents interim work not intended for publication from leaking on `0.0.0` libs).
   - Considering that you may need to be editing your library live as a part of the development of your main project, check out `bower link` (learn all about it [here](https://oncletom.io/2013/live-development-bower-component/)). This will enable you to keep the repos in sync as you work, and facilitate publishing when ready.
   - `bower link` can also be useful if you plan on contributing to a package needed by your project. Simply fork the repo, and link. Once you have your additional bindings, or features needed for your project working, you can contribute them back to the source repo easily with a Pull Request.
@@ -76,7 +75,7 @@ It was previously common to include Markdown documentation generated by `psc-doc
 ## Foreign Function Interface
 
 - PureScript is a new language, and has a need for high quality FFI libraries.
-- If you have already written a library that has FFI code into a native API, consider splitting it into two libraries, a barebones set of FFI bindings, and your extra functionality. 
+- If you have already written a library that has FFI code into a native API, consider splitting it into two libraries, a barebones set of FFI bindings, and your extra functionality.
 
 ## Runtime Requirements