openstack/openstack-manuals
Code Issues Proposed changes

[config-ref] remove unnecessary term markup

Browse Source 
Change-Id: Id00b277bbd35cc998ca1f8583d34660fe4fa2ede
This commit is contained in:
KATO Tomoyuki
2017-02-04 14:57:41 +09:00
parent 0d7623780c
commit 1302594c8e
7 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/config-reference/source/block-storage/drivers/blockbridge-eps-driver.rst
View File

@@ -7,8 +7,8 @@ Introduction
Blockbridge is software that transforms commodity infrastructure into
secure multi-tenant storage that operates as a programmable service. It
provides automatic encryption, secure deletion, :term:`quality of service
(QoS)`, replication, and programmable security capabilities on your choice of
provides automatic encryption, secure deletion, quality of service (QoS),
replication, and programmable security capabilities on your choice of
hardware. Blockbridge uses micro-segmentation to provide isolation that allows
you to concurrently operate OpenStack, Docker, and bare-metal workflows on
shared resources. When used with OpenStack, isolated management domains are

2
doc/config-reference/source/block-storage/drivers/hpe-3par-driver.rst
View File

@@ -186,7 +186,7 @@ Priority Optimization license installed.
``hpe3par:vvs``
The virtual volume set name that has been predefined by the Administrator
with :term:`quality of service (QoS)` rules associated to it. If you specify
with quality of service (QoS) rules associated to it. If you specify
extra_specs ``hpe3par:vvs``, the qos_specs ``minIOPS``, ``maxIOPS``,
``minBWS``, and ``maxBWS`` settings are ignored.

4
doc/config-reference/source/block-storage/drivers/xio-volume-driver.rst
View File

@@ -5,8 +5,8 @@ X-IO volume driver
The X-IO volume driver for OpenStack Block Storage enables ISE products to be
managed by OpenStack Block Storage nodes. This driver can be configured to work
with iSCSI and Fibre Channel storage protocols. The X-IO volume driver allows
the cloud operator to take advantage of ISE features like :term:`Quality of
Service (QOS)` and Continuous Adaptive Data Placement (CADP). It also supports
the cloud operator to take advantage of ISE features like quality of
service (QoS) and Continuous Adaptive Data Placement (CADP). It also supports
creating thin volumes and specifying volume media affinity.
Requirements

2
doc/config-reference/source/common-configurations/rpc.rst
View File

@@ -2,7 +2,7 @@
RPC messaging configurations
============================
OpenStack services use :term:`Advanced Message Queuing Protocol (AMQP)`,
OpenStack services use advanced message queuing protocol (AMQP),
an open standard for messaging middleware.
This messaging middleware enables the OpenStack services that run on
multiple servers to talk to each other. OpenStack Oslo RPC supports

4
doc/config-reference/source/config-format.rst
View File

@@ -2,8 +2,8 @@
Configuration file format
=========================
OpenStack uses the :term:`INI <INI format>` file format for configuration
files. An INI file is a simple text file that specifies options as
OpenStack uses the INI file format for configuration files.
An INI file is a simple text file that specifies options as
``key=value`` pairs, grouped into sections.
The ``DEFAULT`` section contains most of the configuration options.
Lines starting with a hash sign (``#``) are comment lines.

10
doc/config-reference/source/shared-file-systems/drivers/cephfs-native-driver.rst
View File

@@ -65,13 +65,13 @@ Requirements
http://docs.ceph.com/docs/master/cephfs/createfs/)
- ``ceph-common`` package installed in the servers running the
:term:`manila-share` service.
``manila-share`` service.
- Ceph client installed in the guest, preferably the FUSE based client,
``ceph-fuse``.
- Network connectivity between your Ceph cluster's public network and the
servers running the :term:`manila-share` service.
servers running the ``manila-share`` service.
- Network connectivity between your Ceph cluster's public network and guests.
@@ -104,7 +104,7 @@ Systems service to use:
``manila.keyring``, along with your ``ceph.conf`` file, then needs to be placed
on the server running the :term:`manila-share` service.
on the server running the ``manila-share`` service.
Enable snapshots in Ceph if you want to use them in the Shared File Systems
service:
@@ -113,9 +113,9 @@ service:
ceph mds set allow_new_snaps true --yes-i-really-mean-it
In the server running the :term:`manila-share` service, you can place the
In the server running the ``manila-share`` service, you can place the
``ceph.conf`` and ``manila.keyring`` files in the ``/etc/ceph`` directory. Set
the same owner for the :term:`manila-share` process and the ``manila.keyring``
the same owner for the ``manila-share`` process and the ``manila.keyring``
file. Add the following section to the ``ceph.conf`` file.
.. code-block:: ini

2
doc/config-reference/source/shared-file-systems/drivers/emc-unity-driver.rst
View File

@@ -225,7 +225,7 @@ for the Unity driver.
Unity driver requires this option to be as ``True``.
Restart of :term:`manila-share` service is needed for the configuration
Restart of ``manila-share`` service is needed for the configuration
changes to take effect.