svn commit: r910172 - in /websites/staging/mahout/trunk/content: ./ developers/github.html

[bu...@apache.org]

Author: buildbot
Date: Tue May 27 22:07:07 2014
New Revision: 910172

Log:
Staging update by buildbot for mahout

Modified:
    websites/staging/mahout/trunk/content/   (props changed)
    websites/staging/mahout/trunk/content/developers/github.html

Propchange: websites/staging/mahout/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 27 22:07:07 2014
@@ -1 +1 @@
-1597891
+1597892

Modified: websites/staging/mahout/trunk/content/developers/github.html
==============================================================================
--- websites/staging/mahout/trunk/content/developers/github.html (original)
+++ websites/staging/mahout/trunk/content/developers/github.html Tue May 27 22:07:07 2014
@@ -245,7 +245,7 @@
 <h2 id="how-to-create-a-pr-for-contributers">How to create a PR (for contributers)</h2>
 <p>Read [<a href="https://help.github.com/articles/creating-a-pull-request">1</a>]. </p>
 <p>Pull requests are made to apache/mahout repository on Github. </p>
-<h2 id="merging-a-pr-and-closing-it-for-committers">merging a PR and closing it (for committers).</h2>
+<h2 id="merging-a-pr-and-closing-it-for-committers">Merging a PR and closing it (for committers)</h2>
 <p>Remember that pull requests are equivalent to a remote branch with potentially a multitude of commits. 
 In this case it is recommended to squash remote commit history to have one commit per issue, rather 
 than merging in a multitude of contributer's commits. In order to do that, as well as close the PR at the