Fixing trivial nits

- Changing newton to ocata for some links
- Capitals to small for project names

Change-Id: I82df51bbd74503e9fa97f96d77eff22365890e0a

security-guide/source/block-storage/volume_wiping.rst

@@ -7,7 +7,7 @@ to set the ``lvm_type`` to ``thin``, and then use the ``volume_clear``
 parameter. Alternatively, if the volume encryption feature is used, then
 volume wiping is not necessary if the volume encryption key is deleted.
 See the OpenStack Configuration Reference doc in the `Volume Encryption
-<https://docs.openstack.org/newton/config-reference/block-storage/volume-encryption.html>`__
+<https://docs.openstack.org/ocata/config-reference/block-storage/volume-encryption.html>`__
 section for set up details and also the `Castellan usage
 <https://docs.openstack.org/developer/castellan/usage.html>`__ document
 for key deletion.
@@ -25,7 +25,7 @@ patterns.
 
 For more information about the ``lvm_type`` parameter, see
 the `LVM Block Storage section
-<https://docs.openstack.org/newton/config-reference/block-storage/drivers/lvm-volume-driver.html>`__
+<https://docs.openstack.org/ocata/config-reference/block-storage/drivers/lvm-volume-driver.html>`__
 
 of OpenStack Configuration Reference and
 the `Oversubscription in thin provisioning
@@ -34,5 +34,5 @@ of OpenStack Administrator Guide.
 
 For more information about the ``volume_clear`` parameter, see the
 `Block Storage sample configuration files
-<https://docs.openstack.org/newton/config-reference/block-storage/samples/index.html>`__
+<https://docs.openstack.org/ocata/config-reference/block-storage/samples/index.html>`__
 of OpenStack Configuration Reference.

security-guide/source/compute/hardening-deployments.rst

@@ -33,7 +33,7 @@ successfully.
 
 Monitoring is a critical component of IT infrastructure, and we recommend the
 `Compute logfiles
-<https://docs.openstack.org/newton/config-reference/compute/logs.html>`__
+<https://docs.openstack.org/ocata/config-reference/compute/logs.html>`__
 be monitored and analyzed so that meaningful alerts can be created.
 
 

security-guide/source/identity/policies.rst

@@ -9,7 +9,7 @@ associated policy file. A resource, for example, could be API access, the
 ability to attach to a volume, or to fire up instances. The policy rules are
 specified in JSON format and the file is called ``policy.json``. The
 syntax and format of this file is discussed in the `Configuration Reference
-<https://docs.openstack.org/newton/config-reference/policy-json-file.html>`__.
+<https://docs.openstack.org/ocata/config-reference/policy-json-file.html>`__.
 
 These policies can be modified or updated by the cloud administrator to
 control the access to the various resources. Ensure that any changes to the

security-guide/source/instance-management/security-services-for-instances.rst

@@ -48,9 +48,9 @@ and volume requests.
 
 The ``FilterScheduler`` is the default scheduler for OpenStack
 Compute, although other schedulers exist (see the section `Scheduling
-<https://docs.openstack.org/newton/config-reference/compute/scheduler.html>`_
+<https://docs.openstack.org/ocata/config-reference/compute/scheduler.html>`_
 in the `OpenStack Configuration Reference
-<https://docs.openstack.org/newton/config-reference/config-overview.html>`_
+<https://docs.openstack.org/ocata/config-reference/config-overview.html>`_
 ). This works in collaboration with 'filter hints' to decide where an
 instance should be started. This process of host selection allows
 administrators to fulfill many different security and compliance

security-guide/source/object-storage.rst

@@ -86,7 +86,7 @@ non-root (UID 0) service account. One recommendation is the user name "swift"
 with the primary group "swift." Object Storage services include, for example,
 'proxy-server', 'container-server', 'account-server'. Detailed steps for setup
 and configuration can be found in the `Add Object Storage chapter
-<https://docs.openstack.org/project-install-guide/object-storage/newton/>`__
+<https://docs.openstack.org/project-install-guide/object-storage/ocata/>`__
 of the Installation Guide in the `OpenStack Documentation index
 <https://docs.openstack.org>`__. (The link defaults to the Ubuntu version.)
 

security-guide/source/shared-file-systems/policies.rst

@@ -46,4 +46,4 @@ management commands are used.
     service is running. Manual modification of the policy can have unexpected
     side effects and is not encouraged. For details, see
     `The policy.json file
-    <https://docs.openstack.org/newton/config-reference/policy-json-file.html>`_.
+    <https://docs.openstack.org/ocata/config-reference/policy-json-file.html>`_.

security-guide/source/tenant-data/data-encryption.rst

@@ -53,7 +53,7 @@ basis. As of the Kilo release, the following features are supported:
 
    -  Volume encryption is supported by back-end key storage for
       enhanced security (for example, a Hardware Security Module (HSM)
-      or a KMIP server can be used as a Barbican back-end secret store)
+      or a KMIP server can be used as a barbican back-end secret store)
 
 Ephemeral disk encryption
 ~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -119,9 +119,9 @@ risk of users’ data being read if an unauthorized party were to gain
 physical access to a disk.
 
 Encryption of data at rest is implemented by middleware that may be included in
-the proxy server WSGI pipeline. The feature is internal to a Swift cluster and
+the proxy server WSGI pipeline. The feature is internal to a swift cluster and
 not exposed through the API. Clients are unaware that data is encrypted by
-this feature internally to the Swift service; internally encrypted data
+this feature internally to the swift service; internally encrypted data
 should never be returned to clients through the swift API.
 
 The following data are encrypted while at rest in swift:

security-guide/source/tenant-data/data-privacy-concerns.rst

@@ -110,7 +110,7 @@ the encryption key. The end user can select this feature while creating a
 volume, but note that an admin must perform a one-time set up of the volume
 encryption feature first. Instructions for this setup are in the block
 storage section of the `Configuration Reference
-<https://docs.openstack.org/newton/config-reference/block-storage/volume-encryption.html>`__
+<https://docs.openstack.org/ocata/config-reference/block-storage/volume-encryption.html>`__
 , under volume encryption.
 
 If the OpenStack volume encryption feature is not used, then other approaches

security-guide/source/tenant-data/key-management.rst

@@ -29,7 +29,7 @@ called PyKMIP.
 Bibliography:
 ~~~~~~~~~~~~~
 
--  OpenStack.org, Welcome to Barbican's Developer Documentation!. 2014.
+-  OpenStack.org, Welcome to barbican's Developer Documentation!. 2014.
    `Barbican developer
    documentation <https://docs.openstack.org/developer/barbican>`__