openstack
/
cinder-specs
Code Issues Proposed changes

Replace Chinese punctuation with English punctuation 

Curly quotes(Chinese punctuation) usually input from Chinese input method.
When read from english context, it makes some confusion.

Change-Id: Idd44863ba3b1747a88a0773ee32c8a3fa14cb19b
This commit is contained in:
gaofei 2018-01-24 13:32:23 +08:00 committed by Gao Fei
parent 64a0b299c7
commit 90acb319bb
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
specs/mitaka/api-microversions.rst
View File

@ -71,11 +71,11 @@ Use Cases
Proposed change
===============
Cinder will use a framework we will call ‘API Microversions’ for allowing
Cinder will use a framework we will call 'API Microversions' for allowing
changes to the API while preserving backward compatibility. The basic idea is
that a user has to explicitly ask for their request to be treated with a
particular version of the API. So breaking changes can be added to the API
without breaking users who don’t specifically ask for it. This is done with
without breaking users who don't specifically ask for it. This is done with
an HTTP header X-OpenStack-Cinder-API-Version which is a monotonically
increasing semantic version number starting from 2.1.

2
specs/ocata/ha-aa-job-distribution.rst
View File

@ -168,7 +168,7 @@ on where to perform operations.
In a similar way to the Service state reporting we need to prevent concurrent
access to the data structure when updating this information. Fortunately for us
we are storing this information in a Python dictionary on the schedulers, and
since we are using an eventlet executor for the RPC server we don’t have to
since we are using an eventlet executor for the RPC server we don't have to
worry about using locks, the inherent behavior of the executor will prevent
concurrent access to the dictionary. So no changes are needed there to have
exclusive access to the data structure.

2
specs/queens/v3-api-validation.rst
View File

@ -171,7 +171,7 @@ each API method in ad-hoc. These changes would make the API method code dirty
and we needed to create multiple patches due to incomplete validation.
If using JSON Schema definitions instead, acceptable request formats are clear
and we don’t need to do ad-hoc works in the future.
and we don't need to do ad-hoc works in the future.
Pecan Framework:
`Pecan <http://pecan.readthedocs.org/en/latest/>`_