jjb/jenkins-job-builder
Code Issues Proposed changes

Fix two typos and Fix readability

Browse Source 
apropriate => appropriate
behaviour  => behavior

tha toption => that option

Change-Id: I97b771752062861f55f372b03cd1f5449482b6ef
This commit is contained in:
Atsushi SAKAI 2015-07-27 09:08:33 +09:00
parent d7add10803
commit 0dc94847a8
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/source/definition.rst
View File

@ -222,7 +222,7 @@ Raw config
It is possible, but not recommended, to use `raw` within a module to
inject raw xml into the job configs.
This is relevant in case there is no apropriate module for a
This is relevant in case there is no appropriate module for a
Jenkins plugin or the module does not behave as you expect it to do.
For example:
@ -231,7 +231,7 @@ For example:
Is the raw way of adding support for the `xvnc` wrapper.
To get the apropriate xml to use you would need to create/edit a job
To get the appropriate xml to use you would need to create/edit a job
in Jenkins and grab the relevant raw xml segment from the
`config.xml`.
@ -296,10 +296,10 @@ For example:
By default JJB will fail if it tries to interpolate a variable that was not
defined, but you can change that behaviour and allow empty variables with the
defined, but you can change that behavior and allow empty variables with the
allow_empty_variables configuration option.
For example, having a configuration file with tha toption enabled:
For example, having a configuration file with that option enabled:
.. literalinclude:: /../../tests/yamlparser/fixtures/allow_empty_variables.conf