svn commit: r981539 - in /websites/staging/olingo/trunk/content: ./ contribute.html

[bu...@apache.org]

Author: buildbot
Date: Tue Mar  1 20:37:01 2016
New Revision: 981539

Log:
Staging update by buildbot for olingo

Modified:
    websites/staging/olingo/trunk/content/   (props changed)
    websites/staging/olingo/trunk/content/contribute.html

Propchange: websites/staging/olingo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar  1 20:37:01 2016
@@ -1 +1 @@
-1733132
+1733138

Modified: websites/staging/olingo/trunk/content/contribute.html
==============================================================================
--- websites/staging/olingo/trunk/content/contribute.html (original)
+++ websites/staging/olingo/trunk/content/contribute.html Tue Mar  1 20:37:01 2016
@@ -155,8 +155,8 @@ The Olingo project uses the following <e
 <li><em>Feature</em> - An issue that introduced a new feature (behaviour) to the Olingo library (this could be e.g. an additional not yet implemented part of the OData specification or convenience methods)</li>
 <li><em>Improvement</em> - An issue that improves an existing feature (behaviour) of the Olingo library (this could be e.g. a convenience method or internal improvements which does not change behavior)</li>
 <li><em>Bug</em> - An issue that describes an incorrect behaviour of the Olingo library in relation to the according OData specification.</li>
-<li><em>Test</em> - An issue that only improve or exentds tests for the  Olingo library.</li>
-<li><em>Task</em> - An issue that improve or exentds basic parts for the Olingo library without changing code (or logic). This could be e.g. improvements or changes necessary for the build infrastructure.</li>
+<li><em>Test</em> - An issue that only improve or extends tests for the  Olingo library.</li>
+<li><em>Task</em> - An issue that improve or extends basic parts for the Olingo library without changing code (or logic). This could be e.g. improvements or changes necessary for the build infrastructure.</li>
 <li><em>Question</em> - An issue that only is a question related to the Olingo library.</li>
 </ul>
 <h3 id="develop-the-according-bugfix-feature">Develop the according bugfix / feature<a class="headerlink" href="#develop-the-according-bugfix-feature" title="Permanent link">&para;</a></h3>
@@ -195,7 +195,7 @@ You have done several commits and want t
 
 
 <p>First rebase your local history to create a single commit. After that create a patch file using <code>git format-patch</code>. Now you can upload and append your created patch file to the JIRA issue.</p>
-<p><strong>Example - Appling a patch file</strong>
+<p><strong>Example - Applying a patch file</strong>
 You like to apply a patch file named "OLINGO_42.patch". Use the following commands:</p>
 <div class="codehilite"><pre><span class="n">git</span> <span class="n">am</span> <span class="o">--</span><span class="n">signoff</span> <span class="n">OLINGO_42</span><span class="p">.</span><span class="n">patch</span>
 </pre></div><div align="center">