Ref Guide: little typos

This commit is contained in:
Cassandra Targett 2019-06-07 17:31:46 -05:00
parent c598e27ae7
commit 4130876510
2 changed files with 5 additions and 5 deletions

View File

@ -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.

View File

@ -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`: