IPsec and IPSec are used mixedly

[Akihiro Motoki]

Both IPsec and IPSec are used. It should be consistent and either of them should be used.
In RFC, "IPsec" is used (https://tools.ietf.org/html/rfc6071), so IPsec looks better.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/498901

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/498901
Committed: https://git.openstack.org/cgit/openstack/neutron-vpnaas-dashboard/commit/?id=e3156ce5f9a1d722fa90bde1d9a7ad149af14eff
Submitter: Jenkins
Branch: master

commit e3156ce5f9a1d722fa90bde1d9a7ad149af14eff
Author: Akihiro Motoki <email address hidden>
Date: Tue Aug 29 17:16:09 2017 +0000

    Use 'IPsec' consistently

    Previously both 'IPsec' and 'IPSec' are used. It is consistent.
    In IETF we use 'IPsec' consistently and 'IPsec' looks a better choice.

    This commit also updates unnecessary capitalizations like:
    - IPsec Policy -> IPsec policy
    - IKE Policy -> IKE policy
    - IPsec Site Connection -> IPsec site connection
    - VPN Service -> VPN service

    In the horizon convention, every word is capitalized
    only in page titles, action captions and field captions.
    For other messages, there is no need to capitalize them.

    Change-Id: I7f3ba10d5a7051fe598b45d13af79cc1ead0285f
    Closes-Bug: #1713766

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron-vpnaas-dashboard 1.2.0 release.