svn commit: r1006675 - in /websites/staging/lucene/trunk/content: ./ pylucene/jcc/features.html

[bu...@apache.org]

Author: buildbot
Date: Mon Feb 13 13:02:05 2017
New Revision: 1006675

Log:
Staging update by buildbot for lucene

Modified:
    websites/staging/lucene/trunk/content/   (props changed)
    websites/staging/lucene/trunk/content/pylucene/jcc/features.html

Propchange: websites/staging/lucene/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Feb 13 13:02:05 2017
@@ -1 +1 @@
-1782764
+1782765

Modified: websites/staging/lucene/trunk/content/pylucene/jcc/features.html
==============================================================================
--- websites/staging/lucene/trunk/content/pylucene/jcc/features.html (original)
+++ websites/staging/lucene/trunk/content/pylucene/jcc/features.html Mon Feb 13 13:02:05 2017
@@ -756,7 +756,7 @@ Following are the steps and constraints
 <p>JCC must be built in shared mode.  See
 <a href="install.html">installation
 instructions</a> for more information about shared mode.
-Note that for this use on Mac OS X, JCC must also be built
+Note that for this use on macOS, JCC must also be built
 with the link flags <i>"-framework", "Python"</i> in
 the <i>LFLAGS</i> value.</p>
 </li>
@@ -777,7 +777,7 @@ directory must be on the Java <i>CLASSPA
 <li>
 <p>The JCC egg directory contains the JCC shared runtime library - not
 the JCC Python extension shared library - but a library
-called <i>libjcc.dylib</i> on Mac OS X, 
+called <i>libjcc.dylib</i> on macOS, 
 <i>libjcc.so</i> on Linux or <i>jcc.dll</i> on Windows. 
 This directory must be added to the Java VM's shared library path
 via the <i>-Djava.library.path</i> command line parameter.</p>