Browse Source

Fix some grammar or spelling de-normalization

Fix some de-normalization of plural forms or grammar

Change-Id: I9e2b5ab7a2744cd730a95e9f53c0ebc5fb696ad9
changes/21/446421/2
yuanpeng 5 years ago
parent
commit
cc4940f756
  1. 2
      api-ref/source/bays.inc
  2. 4
      api-ref/source/clusters.inc
  3. 2
      doc/source/troubleshooting-guide.rst
  4. 4
      specs/resource-quotas.rst

2
api-ref/source/bays.inc

@ -63,7 +63,7 @@ Response Example
.. literalinclude:: samples/bay-create-resp.json
:language: javascript
List all bay
List all bays
====================
.. rest_method:: GET /v1/bays/

4
api-ref/source/clusters.inc

@ -64,8 +64,8 @@ Response Example
.. literalinclude:: samples/cluster-create-resp.json
:language: javascript
List all cluster
================
List all clusters
=================
.. rest_method:: GET /v1/clusters

2
doc/source/troubleshooting-guide.rst

@ -793,7 +793,7 @@ Helpful nuances about the Devstack Gate
search for the magnum jobs where you'll see examples of what
gets passed in.
* Three jobs are usually run as a part of Magnum gate, all of with are found in ``project-config``'s `macros.yml <https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/macros.yaml>`_:
* Three jobs are usually run as a part of Magnum gate, all of which are found in ``project-config``'s `macros.yml <https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/macros.yaml>`_:
* link-logs

4
specs/resource-quotas.rst

@ -39,7 +39,7 @@ appropriately.
a. Ability to know current resource consumption.
b. Ability to prohibit overuse by a project.
c. Prevent situation where users in the project get starved because users in
other project consume all the resource. Alice feels something like
other project consume all the resources. Alice feels something like
"Quota Management" would help to guarantee "fairness".
d. Prevent DOS kind of attack, abuse or error by users where an excessive
amount of resources are created.
@ -72,7 +72,7 @@ Other Openstack projects like Nova [2]_, Cinder [3]_ follow a similar pattern
and we will also do so and hence won't have a separate CLI for quota-create.
Later if the user wants to change the Quota of the resource option will be
provided to do so using magnum quota-update. In situation where all of the
quota for a specific Magnum resource (Bay) have been consumed and is
quota for a specific Magnum resource (Bay) has been consumed and is
under use, admin will be allowed to set the quota to a any value lower than
the usage or hardlimit to prohibit users from the project to create new
Bays. This gives more flexibility to the admin to have a better control

Loading…
Cancel
Save