readme: Fix puppet server typo

Fix server typo and remove whitespaces.
Typo in Readme.md
Merge pull request #15 from sbadia/fix-typo

(maint) readme: Fix puppet server typo
"project_page" should point to the source.
Merge pull request #17 from adreyer/master

"project_page" should point to the source.
(PDOC-8) Add .rubocop.yml to project

Since we want to use rubocop to help maintain the code quality of
this project, add a .rubocop.yml file (borrowed from the puppet repo)
so that we can successfully enforce the things we want and disable
those we don't.
(PDOC-8) Fix present rubocop offenses

Since we want to run rubocop in travis when pull requests are
submitted, fix a few pre-existing rubocop offenses.
(PDOC-8) Add rubocop to travis job

In order to ensure long term code quality, add a rubocop check to
the travis job which runs when a pull request is submitted. Do this
by adding a rake task for rubocop and setting up travis to run
both the spec rake task and the rubocop one.

Additionally, make a few changes to the .rubocop.yml file so it
will stop complaining about incorrect namespaces.
(PDOC-14) Fix strings to work with future parser

Prior to this commit, two require statements were in the wrong
order, causing strings to fail when running against anything that
required the future parser.

Now, those requires have been flipped and strings can run with
`--parser future` successfully.
Merge remote-tracking branch 'upstream/pr/18'

* upstream/pr/18:
  (PDOC-8) Add rubocop to travis job
  (PDOC-8) Fix present rubocop offenses
  (PDOC-8) Add .rubocop.yml to project
Merge pull request #19 from hkenney/issue/master/pdoc14_fix_strings_for_future_parser

(PDOC-14) Fix strings to work with future parser
(maint) Fix ironic misspelling of intelligence

intelligance -> intelligence in README.md
(maint) Add build status to README.md

In order to make it easy to quickly tell if the Travis CI build is currently green,
add a badge to the README.
(maint) Update metadata.json for 0.1.1 release
(PDOC-13) Add documentation examples to README

In order to make it easier for users, give some basic examples
in the README of how write documentation that is compatible with
strings. Also provide a few resources for getting started.
(maint) Exclude files that cause YARD errors

Running `puppet strings server` generates documentation for all
modules in your modulepath, meaning that it also generates HTML
for strings itself. Since there are parts of strings that are not
meant to be documented with YARD, exclude the files that cause
error messages so that `puppet strings server` is not needlessly
noisy.

Additionally, make a few suggested changes to the README to make
it clearer and easier to read.
Merge pull request #20 from hkenney/maint/master/pdoc-11_update_readme_with_examples_and_resources

(PDOC-13) Update README with examples and resources