[lucene-solr] branch jira/solr-13105-toMerge updated: copy editing text

[ep...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

epugh pushed a commit to branch jira/solr-13105-toMerge
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git


The following commit(s) were added to refs/heads/jira/solr-13105-toMerge by this push:
     new 4de6389  copy editing text
4de6389 is described below

commit 4de638941f112c6bde0e89d096e7f46167e131c5
Author: epugh@opensourceconnections.com <>
AuthorDate: Thu Jan 7 15:59:10 2021 -0500

    copy editing text
---
 solr/solr-ref-guide/src/loading.adoc       |  4 ++--
 solr/solr-ref-guide/src/search-sample.adoc | 10 +++++-----
 solr/solr-ref-guide/src/transform.adoc     |  2 +-
 solr/solr-ref-guide/src/vector-math.adoc   |  2 +-
 4 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/solr/solr-ref-guide/src/loading.adoc b/solr/solr-ref-guide/src/loading.adoc
index dd8005f..e49103f 100644
--- a/solr/solr-ref-guide/src/loading.adoc
+++ b/solr/solr-ref-guide/src/loading.adoc
@@ -269,7 +269,7 @@ with the date string, a template to parse the date using a Java SimpleDateFormat
 and an optional time zone.
 
 If the time zone is not present the time zone defaults to GMT time unless
-its included in the date string itself.
+it's included in the date string itself.
 
 Below is an example of the `dateTime` function applied to the date format
 in the example above.
@@ -453,7 +453,7 @@ The `if` function and `isNull`, `notNull` functions can be combined to replace n
 
 In the example below the `if` function applies the `isNull` boolean expression to two different fields.
 
-In the first example it replaces null *patel_width* values with 0, and returns the *petal_width* if present.
+In the first example it replaces null *petal_width* values with 0, and returns the *petal_width* if present.
 In the second example it replace null *field1* values with the string literal "NA" and returns *field1* if present.
 
 image::images/math-expressions/ifIsNull.png[]
diff --git a/solr/solr-ref-guide/src/search-sample.adoc b/solr/solr-ref-guide/src/search-sample.adoc
index e91983c..76ad251 100644
--- a/solr/solr-ref-guide/src/search-sample.adoc
+++ b/solr/solr-ref-guide/src/search-sample.adoc
@@ -29,7 +29,7 @@ The *search* function can be used to search a Solr Cloud collection and return a
 result set.
 
 Below is an example of the most basic *search* function called from the Zeppelin-Solr interpreter.
-Zeppelin-Solr sends the *seach(logs)* call to the /stream handler and displays the results
+Zeppelin-Solr sends the *search(logs)* call to the /stream handler and displays the results
 in *table* format.
 
 
@@ -129,7 +129,7 @@ the relationship between the two variables.
 
 By studying the scatter plot we can learn the following:
 
-* As filesize_d rises response_d tends to rise.
+* As *filesize_d* rises *response_d* tends to rise.
 * This relationship appears to be linear, as a straight line put through the data could
 be used to model the relationship.
 * The points appear to cluster more densely along a straight line through the middle
@@ -263,7 +263,7 @@ In the next example the `significantTerms` function returns the top 5 significan
 in the *complaint_type_s* field for the borough of Brooklyn. The highest scoring term,
 Elder Abuse, has a foreground count of 285 and background count of 298. This means
 that there were 298 Elder Abuse complaints in the entire data set, and 285 of them
-were in Brooklyn. This shows that Elder Abuse complaints have a much higher occurrence
+where in Brooklyn. This shows that Elder Abuse complaints have a much higher occurrence
 rate in Brooklyn than the other boroughs.
 
 image::images/math-expressions/significantTerms2.png[]
@@ -289,7 +289,7 @@ The example below finds stock tickers whose daily movements tend to be correlate
 ticker *jpm* (JP Morgan).
 
 The inner `search` expression finds records between a specific date range
-where the ticker symbol is *jpm* and the change_d field (daily change in stock price)
+where the ticker symbol is *jpm* and the *change_d* field (daily change in stock price)
 is greater then .25. This search returns all fields in the index including
 the *yearMonthDay_s* which is the string representation of the year, month and day
 of the matching records.
@@ -301,7 +301,7 @@ yearMonthDay_s field value returned
 by the initial search, and will return records for all tickers on those days.
 A filter query is applied to the search to filter the search to rows that have a *change_d*
 greater the .25. This will find all records on the matching days, that have a
-daily change greater then .25.
+daily change greater than .25.
 
 The *gather* parameter tells the nodes expression to gather the *ticker_s* symbols during the
 breadth first search. The `count(*)` parameter counts the occurrences of the tickers.
diff --git a/solr/solr-ref-guide/src/transform.adoc b/solr/solr-ref-guide/src/transform.adoc
index 11f4371..0b9d2df 100644
--- a/solr/solr-ref-guide/src/transform.adoc
+++ b/solr/solr-ref-guide/src/transform.adoc
@@ -48,7 +48,7 @@ The `having` function can be used to filter tuples in the stream based on
 boolean logic.
 
 In the example below the `having` function is filtering the output of the
-`facet` function to only emit tuples that have `count(*)` greater then 20404.
+`facet` function to only emit tuples that have `count(*)` greater than 20404.
 
 image::images/math-expressions/having.png[]
 
diff --git a/solr/solr-ref-guide/src/vector-math.adoc b/solr/solr-ref-guide/src/vector-math.adoc
index 3f3abcd..235d420 100644
--- a/solr/solr-ref-guide/src/vector-math.adoc
+++ b/solr/solr-ref-guide/src/vector-math.adoc
@@ -54,7 +54,7 @@ When this expression is sent to the `/stream` handler it responds with a JSON ar
 
 == Visualization
 
-The *zplot* function can be used to visualize vectors using Zeppeling-Solr.
+The *zplot* function can be used to visualize vectors using Zeppelin-Solr.
 
 Let's first see what happens when we visualize the array function as a table.