Fixed documentation by removing colon from Content-Security-Policy

The doc is not in par with what the framework is actually doing.
The framework sends out the header without a colon by default (which is correct) but the doc uses a colon (which is wrong).
See http://content-security-policy.com/ for reference.
By using the colon browsers will raise exceptions....