Fix typos in Senlin files
TrivialFix Change-Id: I64f8e5099219f6ced31cd302828a65d71bfcb2f7
This commit is contained in:
parent
21901ebc56
commit
5a2c3854d2
@ -125,7 +125,7 @@
|
||||
file="${basedir}/target/docbkx/pdf/bk-senlin-admin-guide.pdf"
|
||||
tofile="${basedir}/target/docbkx/webhelp/${release.path.name}/senlin-admin/bk-senlin-admin-guide-${release.path.name}.pdf"/>
|
||||
|
||||
<!--Deletes leftover uneeded directories -->
|
||||
<!--Deletes leftover unneeded directories -->
|
||||
|
||||
<delete dir="${basedir}/target/docbkx/webhelp/bk-senlin-admin-guide"/>
|
||||
|
||||
|
@ -195,7 +195,7 @@ in the action's ``data`` property, the policy proceeds to parse the raw inputs
|
||||
of the action.
|
||||
|
||||
The output from the parser may indicate an invalid combination of input
|
||||
values. If that is the case, the policy check failes with the action's
|
||||
values. If that is the case, the policy check fails with the action's
|
||||
``data`` set to something like the following example:
|
||||
|
||||
::
|
||||
|
@ -70,7 +70,7 @@ something similar to the following example:
|
||||
}
|
||||
|
||||
If the validation succeeds, the ``data`` property of the action is updated
|
||||
accordingly (see Senarios below).
|
||||
accordingly (see Scenarios below).
|
||||
|
||||
|
||||
Scenarios
|
||||
|
@ -198,7 +198,7 @@ in the action's ``data`` property, the policy proceeds to parse the raw inputs
|
||||
of the action.
|
||||
|
||||
The output from the parser may indicate an invalid combination of input
|
||||
values. If that is the case, the policy check failes with the action's
|
||||
values. If that is the case, the policy check fails with the action's
|
||||
``data`` set to something like the following example:
|
||||
|
||||
::
|
||||
@ -217,4 +217,4 @@ When the placement policy finds out the number of nodes to create (or delete),
|
||||
it proceeds to calculate a distribution plan. If the action is about growing
|
||||
the size of the cluster, the logic and the output format are the same as that
|
||||
have been outlined in scenario *S2*. Otherwise, the logic and the output
|
||||
format are identical to that have been describled in scenario *S1*.
|
||||
format are identical to that have been described in scenario *S1*.
|
||||
|
Loading…
Reference in New Issue
Block a user