openstack/training-guides
Code Issues Proposed changes

Fix spelling errors - commited to committed

Browse Source 
Change-Id: Ib33d77fce109b0a4598bd71f501bd3d9f677174e
This commit is contained in:
Alex Holden
2014-03-07 09:29:03 -08:00
parent a378f82d73
commit f0249df8ef
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
operator-editing-code.xml
View File

@@ -296,7 +296,7 @@
<screen><prompt>$</prompt> <userinput>git commit -a -m "Removed reference to volume scheduler in the computer scheduler config and admin pages, bug 1188522"</userinput></screen> <screen><prompt>$</prompt> <userinput>git commit -a -m "Removed reference to volume scheduler in the computer scheduler config and admin pages, bug 1188522"</userinput></screen>
</step> </step>
<step> <step>
<para>Build commited changes locally by using <command>tox</command>. As part of the review process, <para>Build committed changes locally by using <command>tox</command>. As part of the review process,
Jenkins runs gating scripts to check that the patch is fine. Locally, Jenkins runs gating scripts to check that the patch is fine. Locally,
you can use the <command>tox</command> tool to run the same checks and ensure that a patch works. you can use the <command>tox</command> tool to run the same checks and ensure that a patch works.
Install the tox package and run it from the top level directory which has the <filename>tox.ini</filename> file.</para> Install the tox package and run it from the top level directory which has the <filename>tox.ini</filename> file.</para>
@@ -471,7 +471,7 @@ more details go here. A few sentences would be nice.
blueprint training-manuals</computeroutput></screen> blueprint training-manuals</computeroutput></screen>
</step> </step>
<step> <step>
<para>Build commited changes locally using <command>tox</command>. As part of the review process, <para>Build committed changes locally using <command>tox</command>. As part of the review process,
Jenkins runs gating scripts to check that the patch is fine. Locally, Jenkins runs gating scripts to check that the patch is fine. Locally,
you can use the <command>tox</command> tool to run the same checks and ensure that a patch works. you can use the <command>tox</command> tool to run the same checks and ensure that a patch works.
Install the tox package and run it from the top level directory which has the <filename>tox.ini</filename> file.</para> Install the tox package and run it from the top level directory which has the <filename>tox.ini</filename> file.</para>