Updating the configuration for cross-domain with a small example and a resource hook

The biggest issue that's here is that * is being used which will allow any domain to use XHR connections to your domain. This opens up many security issues as it breaks the same-domain model built into the browser. It's suggested that users instead whitelist domains they wish to give connections to.

Adding further details and links regarding nginx configurations

Organizing the notes; Making sure it can still be used a solid, primer snippet

Took at look at https://github.com/h5bp/server-configs-apache/blob/master/.htaccess again and added the same allowed resources as the default allow-origin.
Not having a wide open allow-origin is the point to the changes.
The notes for whitelisting a domain are there for more advanced usages in domains.

Killing the indenting and blank lines

Quality reading experiences.
grammar, doesn't modify code.
Typo foorbar -> foobar
remove the sites-enabled readme

this file is considered a site config  file, preventing the use of the repo as is
Ensure compatibility with earlier/current versions of nginx

auto was not introdued until 1.3.8 and 1.2.5.

Debian wheezy for example only comes with 1.2.1, only the next version
(in testing) will have a version of nginx which supports auto.
rename conf folder to h5bp

The name "conf" is potentially confusing as something which should be inclued
en masse rather than a folder of config snippets.

Closes #13
Add a config file for no default site

fixes #10
add a doc block to no-default

and remove the default_server direcdtive from example.com. Since this file
is likely to be the copy-and-paste file for multiple server configs,
don't mark example.com as the default.

Making sure the defaults do not overwrite the cross-domain-fonts and provide a link
Merge branch 'patch-1' of github.com:geedew/server-configs-nginx into patch-1