Update outdated links in document and spelling error

Update doc links according to OpenStack document migration.
Use https instead of http for docs links.
1)http://docs.openstack.org/releasenotes/puppet-neutron/
  -->https://docs.openstack.org/releasenotes/puppet-neutron/
2)http://docs.openstack.org/infra/bindep/
  -->http://docs.openstack.org/infra/bindep/

Change-Id: I819d0d4b066e5b74b1eca4c017b538b130a12f54
Closes-Bug:#1718333

CHANGELOG.md

@@ -1,7 +1,7 @@
 ## 8.0.0 and beyond
 
 From 8.0.0 release and beyond, release notes are published on
-[docs.openstack.org](http://docs.openstack.org/releasenotes/puppet-neutron/).
+[docs.openstack.org](https://docs.openstack.org/releasenotes/puppet-neutron/).
 
 ##2015-11-25 - 7.0.0
 ###Summary
@@ -57,7 +57,7 @@ This is a backwards-incompatible major release for OpenStack Liberty.
 - dbsync should only notify services that use the db
 - map allocation_pool property to set
 - restart Neutron agents if packages are updated
-- remove unecessary constraint between Package and Config resource
+- remove unnecessary constraint between Package and Config resource
 - fix 'shared' parameter check in neutron_network provider
 
 ####Maintenance

bindep.txt

@@ -1,5 +1,5 @@
 # This is a cross-platform list tracking distribution packages needed by tests;
-# see http://docs.openstack.org/infra/bindep/ for additional information.
+# see https://docs.openstack.org/infra/bindep/ for additional information.
 
 libxml2-devel [test platform:rpm]
 libxml2-dev [test platform:dpkg]

manifests/wsgi/apache.pp

@@ -69,7 +69,7 @@
 #     Optional. Default to apache::vhost 'ssl_*' defaults.
 #
 # [*custom_wsgi_process_options*]
-#   (optional) gives you the oportunity to add custom process options or to
+#   (optional) gives you the opportunity to add custom process options or to
 #   overwrite the default options for the WSGI main process.
 #   eg. to use a virtual python environment for the WSGI process
 #   you could set it to:

templates/n1kv.conf.erb

@@ -9,7 +9,7 @@
 # b)For any updates to parameters to take effect, you just need to execute
 #   'vemcmd reread config'. Its the least-disruptive way for changes to
 #   take effect. However for certain params, n1kv service need to be restarted.
-#    These parameter are stated explictly (restart_on_modify: YES).
+#    These parameter are stated explicitly (restart_on_modify: YES).
 #
 
 #