openstack/senlin
Code Issues Proposed changes

fix typos in doc

Browse Source 
Change-Id: I1815a68fadd78410de91585300c4efc879d5d762
This commit is contained in:
jolie
2016-09-20 17:18:43 +08:00
committed by Shan Guo
parent df9879f886
commit 350040f58d
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/tutorial/receivers.rst
View File

@@ -77,9 +77,9 @@ action using tools like ``curl``.
.. code-block:: console
$ curl -X POST http://node1:8778/v1/webhooks/5dacde18-661e-4db4-b7a8-f2a6e3466f98/trigger?V=1
$ curl -X POST http://node1:8778/v1/webhooks/5dacde18-661e-4db4-b7a8-f2a6e3466f98/trigger?V=1
After a while, you can check that the cluster has been shrinked by 1 node.
After a while, you can check that the cluster has been shrunk by 1 node.
For more details about managing receivers, please check the
:doc:`Receivers <../user/receivers>` section in the

2
doc/source/user/scenarios/autoscaling_heat.rst
View File

@@ -27,7 +27,7 @@ users who want to use heat to create a senlin cluster.
It is often requried by real deployment practices to make the cluster load-balanced
and auto-scaled. We also want the scaling action triggered based on business data
instead of infrastructure metrics. When exsiting cluster is not enough to afford the
instead of infrastructure metrics. When exisiting cluster is not enough to afford the
throughput/workload, the cluster will be scaled-out; when low throughput or workload,
the cluster will be scaled-in.