[lucene-solr] 02/02: SOLR-12330: ref guide typos

[ct...@apache.org]

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

ctargett pushed a commit to branch branch_8x
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git

commit b3d1a7b8e2368027be71adddcfc79887cf8e7ddb
Author: Cassandra Targett <ct...@apache.org>
AuthorDate: Fri Jun 7 13:03:08 2019 -0500

    SOLR-12330: ref guide typos
---
 .../src/json-faceting-domain-changes.adoc            | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/solr/solr-ref-guide/src/json-faceting-domain-changes.adoc b/solr/solr-ref-guide/src/json-faceting-domain-changes.adoc
index 60a842e..88f6d1c 100644
--- a/solr/solr-ref-guide/src/json-faceting-domain-changes.adoc
+++ b/solr/solr-ref-guide/src/json-faceting-domain-changes.adoc
@@ -71,11 +71,11 @@ include::{example-source-dir}JsonRequestApiTest.java[tag=solrj-json-facet-filter
 
 The value of `filter` can be a single query to treat as a filter, or a JSON list of filter queries.  Each query can be:
 
-* a string containing a query in Solr query syntax
-* a reference to a request parameter containing Solr query syntax, of the form: `{param : <request_param_name>}`.
+* a string containing a query in Solr query syntax.
+* a reference to a request parameter containing Solr query syntax, of the form: `{param: <request_param_name>}`.
 The referred parameter might have 0 (absent) or many values.
-** When no values specified, no filter is applied and no error is thrown
-** When many values are specified, each value is parsed and used as filters
+** When no values are specified, no filter is applied and no error is thrown.
+** When many values are specified, each value is parsed and used as filters.
 
 When a `filter` option is combined with other `domain` changing options, the filtering is applied _after_ the other domain changes take place.
 
@@ -83,7 +83,7 @@ When a `filter` option is combined with other `domain` changing options, the fil
 
 Domains can also be expanded by using the `excludeTags` keyword to discard or ignore particular tagged query filters.
 
-This is used in the example below to show the top two manufacturers matching a search.  The search results match the filter `manu_id_s:apple`, but the computed facet discards this filter and operates a domain widened by discarding the `manu_id_s`  filter.
+This is used in the example below to show the top two manufacturers matching a search. The search results match the filter `manu_id_s:apple`, but the computed facet discards this filter and operates a domain widened by discarding the `manu_id_s`  filter.
 
 [.dynamic-tabs]
 --
@@ -120,7 +120,7 @@ include::{example-source-dir}JsonRequestApiTest.java[tag=solrj-json-facet-exclud
 ====
 --
 
-The value of `excludeTags` can be a single string tag, array of string tags or comma-separated tags in the single string.
+The value of `excludeTags` can be a single string tag, an array of string tags, or comma-separated tags in the single string.
 
 When an `excludeTags` option is combined with other `domain` changing options, it expands the domain _before_ any other domain changes take place.
 
@@ -167,11 +167,11 @@ include::{example-source-dir}JsonRequestApiTest.java[tag=solrj-json-facet-query-
 
 The value of `query` can be a single query, or a JSON list of queries.  Each query can be:
 
-* a string containing a query in Solr query syntax
-* a reference to a request parameter containing Solr query syntax, of the form: `{param : <request_param_name>}`.
+* a string containing a query in Solr query syntax.
+* a reference to a request parameter containing Solr query syntax, of the form: `{param: <request_param_name>}`.
 The referred parameter might have 0 (absent) or many values.
-** When no values specified, no error is thrown
-** When many values are specified, each value is parsed and used as queries
+** When no values are specified, no error is thrown.
+** When many values are specified, each value is parsed and used as queries.
 
 NOTE: While a `query` domain can be combined with an additional domain `filter`, It is not possible to also use `excludeTags`, because the tags would be meaningless: The `query` domain already completely ignores the top-level query and all previous filters.