[lucene-solr] branch master updated: Ref Guide: little typos

[ct...@apache.org]

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

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


The following commit(s) were added to refs/heads/master by this push:
     new 4130876  Ref Guide: little typos
4130876 is described below

commit 413087651044217e01d2203704b81cf5f9f86a44
Author: Cassandra Targett <ct...@apache.org>
AuthorDate: Fri Jun 7 17:31:46 2019 -0500

    Ref Guide: little typos
---
 solr/solr-ref-guide/src/collections-api.adoc  | 4 ++--
 solr/solr-ref-guide/src/response-writers.adoc | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/solr/solr-ref-guide/src/collections-api.adoc b/solr/solr-ref-guide/src/collections-api.adoc
index 12f80c7..d255142 100644
--- a/solr/solr-ref-guide/src/collections-api.adoc
+++ b/solr/solr-ref-guide/src/collections-api.adoc
@@ -206,7 +206,7 @@ See the <<create,CREATE action>> section above for details on these attributes.
 [[readonlymode]]
 ==== Read-Only Mode
 Setting the `readOnly` attribute to `true` puts the collection in read-only mode,
-in which any index update requests are rejected. Other collection-level actions (eg. adding /
+in which any index update requests are rejected. Other collection-level actions (e.g., adding /
 removing / moving replicas) are still available in this mode.
 
 The transition from the (default) read-write to read-only mode consists of the following steps:
@@ -316,7 +316,7 @@ http://localhost:8983/solr/admin/collections?action=REINDEXCOLLECTION&name=newCo
 ----
 This request specifies a different schema for the target collection, copies only some of the fields, selects only the documents
 matching a query, and also potentially re-shapes the collection by explicitly specifying 3 shards. Since the target collection
-hasn't been specified in the parameters a collection with a unique name eg. `.rx_newCollection_2` will be created and on success
+hasn't been specified in the parameters, a collection with a unique name, e.g., `.rx_newCollection_2`, will be created and on success
 an alias pointing from `newCollection` to `.rx_newCollection_2` will be created, effectively replacing the source collection
 for the purpose of indexing and searching. The source collection is assumed to be small so a synchronous request was made.
 
diff --git a/solr/solr-ref-guide/src/response-writers.adoc b/solr/solr-ref-guide/src/response-writers.adoc
index b8dca6a..f2e1f71 100644
--- a/solr/solr-ref-guide/src/response-writers.adoc
+++ b/solr/solr-ref-guide/src/response-writers.adoc
@@ -40,10 +40,10 @@ The `wt` parameter selects the Response Writer to be used. The list below descri
 == JSON Response Writer
 
 The default Solr Response Writer is the `JsonResponseWriter`, which formats output in JavaScript Object Notation (JSON), a lightweight data interchange format specified in specified in RFC 4627.
-The default response writer is used when,
+The default response writer is used when:
 
-* `wt` parameter is not specified in the request
-* non-existent response writer is specified
+* the `wt` parameter is not specified in the request, or
+* a non-existent response writer is specified.
 
 Here is a sample response for a simple query like `q=id:VS1GB400C3`: