openstack/manila
Code Issues Proposed changes

Merge "Replace Chinese quotes to English quotes"

Browse Source
This commit is contained in:
Zuul 2018-03-25 02:29:03 +00:00 committed by Gerrit Code Review
commit b68fcb4b29
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/admin/hitachi_hnas_driver.rst
View File

@ -227,9 +227,9 @@ if it exists is located in: */etc/neutron/plugins/openvswitch/ovs_neutron_plugin
Create a route in HNAS to the tenant network. Please make sure Create a route in HNAS to the tenant network. Please make sure
multi-tenancy is enabled and routes are configured per EVS. Use the command multi-tenancy is enabled and routes are configured per EVS. Use the command
“route-net-add” in HNAS console, where the network parameter should be the "route-net-add" in HNAS console, where the network parameter should be the
tenant's private network, while the gateway parameter should be the flat tenant's private network, while the gateway parameter should be the flat
network gateway and the “console-context --evs” parameter should be the ID of network gateway and the "console-context --evs" parameter should be the ID of
EVS in use, such as in the following example: EVS in use, such as in the following example:
.. code-block:: console .. code-block:: console

2
doc/source/contributor/adding_release_notes.rst
View File

@ -57,7 +57,7 @@ How do I add a release note?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
We use `Reno <https://docs.openstack.org/reno/latest/>`_ to create and manage We use `Reno <https://docs.openstack.org/reno/latest/>`_ to create and manage
release notes. The new subcommand combines a random suffix with a “slug” value release notes. The new subcommand combines a random suffix with a "slug" value
to make the new file with a unique name that is easy to identify again later. to make the new file with a unique name that is easy to identify again later.
To create a release note for your change, use: To create a release note for your change, use: