svn commit: r979963 - in /websites/staging/lucene/trunk/content: ./ solr/news.html solr/resources.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb  9 20:16:43 2016
New Revision: 979963

Log:
Staging update by buildbot for lucene

Modified:
    websites/staging/lucene/trunk/content/   (props changed)
    websites/staging/lucene/trunk/content/solr/news.html
    websites/staging/lucene/trunk/content/solr/resources.html

Propchange: websites/staging/lucene/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Feb  9 20:16:43 2016
@@ -1 +1 @@
-1729120
+1729447

Modified: websites/staging/lucene/trunk/content/solr/news.html
==============================================================================
--- websites/staging/lucene/trunk/content/solr/news.html (original)
+++ websites/staging/lucene/trunk/content/solr/news.html Tue Feb  9 20:16:43 2016
@@ -196,13 +196,13 @@ h2:hover > .headerlink, h3:hover > .head
 <p>As of January 23rd 2016, Lucene/Solr source code is hosted in Apache's GIT repository. 
 This means that the old SVN repository is now stale and should not be used.
 For information on working with git, please consult 
-<a href="http://lucene.apache.org/solr/resources.html#solr-version-control">The Solr web site</a>
-and the <a href="https://wiki.apache.org/solr/Git%20commit%20process">WIKI</a></p>
+<a href="http://lucene.apache.org/solr/resources.html#solr-version-control">the Solr web site</a>
+and the <a href="https://wiki.apache.org/solr/Git%20commit%20process">wiki</a>.</p>
 <p>The <a href="https://github.com/apache/lucene-solr/">GitHub mirror</a> remains at 
 the same location as before, but since it now mirrors git.apache.org, the contents
-has changed. Therefore, if you had a personal fork, you will find
+have changed. Therefore, if you had a personal fork, you will find
 that it has changed its "origin remote", and you will have to re-add the
-Apache repo as your origin, and then rebase your changes. Instructions 
+Apache repo as your origin, and then rebase your changes. Instructions
 <a href="https://wiki.apache.org/solr/Git%20commit%20process">here</a>.</p>
 <p>If you had active Pull Requests against our GitHub mirror, these are unfortunately
 gone, but not lost. Please create a new PR against the new mirror or send an email 

Modified: websites/staging/lucene/trunk/content/solr/resources.html
==============================================================================
--- websites/staging/lucene/trunk/content/solr/resources.html (original)
+++ websites/staging/lucene/trunk/content/solr/resources.html Tue Feb  9 20:16:43 2016
@@ -212,7 +212,6 @@
   visibility: hidden;
 }
 h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Title: Resources</p>
 <h2 id="tutorials">Tutorials<a class="headerlink" href="#tutorials" title="Permanent link">&para;</a></h2>
 <!-- 
    TODO: this was previously mentioned.  do we retain something like this?  or...?