Skip to content

armgit / solr

Public Imported from GitHub
0

Apache Solr open-source search software

SOLR-17622: Fix some typos in the reference guide (#3038)

Stefan Weila86d21c26199
diff --git a/solr/solr-ref-guide/build.gradle b/solr/solr-ref-guide/build.gradle
index b548d9981af..811b0748568 100644
--- a/solr/solr-ref-guide/build.gradle
+++ b/solr/solr-ref-guide/build.gradle
@@ -277,7 +277,7 @@ task startUIBuildDir(type: Copy) {
group = 'Site - UI'
dependsOn tasks.downloadDefaultUITemplate
- // Copy the antora latest default ui into the root folder, to mimick a new checkout of the default ui
+ // Copy the antora latest default ui into the root folder, to mimic a new checkout of the default ui
with {
from "${project.ext.nodeProjectDir}/node_modules/@antora/ui-default"
duplicatesStrategy = 'EXCLUDE'
diff --git a/solr/solr-ref-guide/modules/ROOT/images/diagrams/splitshard-seq.puml b/solr/solr-ref-guide/modules/ROOT/images/diagrams/splitshard-seq.puml
index feb7b4199d1..8292ae803ab 100644
--- a/solr/solr-ref-guide/modules/ROOT/images/diagrams/splitshard-seq.puml
+++ b/solr/solr-ref-guide/modules/ROOT/images/diagrams/splitshard-seq.puml
@@ -17,7 +17,7 @@
@startuml
-' Note: in TEOZ mode som skinparams don't work
+' Note: in TEOZ mode some skinparams don't work
' and currently notes on messages can't be customized -
' but this mode creates more compact layout, enable if needed
diff --git a/solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc b/solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc
index 68873c6ca7d..c1053d93c43 100644
--- a/solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc
+++ b/solr/solr-ref-guide/modules/configuration-guide/pages/coreadmin-api.adoc
@@ -828,7 +828,7 @@ http://localhost:8983/solr/admin/cores?action=REQUESTSTATUS&requestid=1
[[coreadmin-requestrecovery]]
== REQUESTRECOVERY
-The `REQUESTRECOVERY` action manually asks a core to recover by synching with the leader.
+The `REQUESTRECOVERY` action manually asks a core to recover by syncing with the leader.
This should be considered an "expert" level command and should be used in situations where the node (SorlCloud replica) is unable to become active automatically.
`admin/cores?action=REQUESTRECOVERY&core=_core-name_`
diff --git a/solr/solr-ref-guide/modules/configuration-guide/pages/index-segments-merging.adoc b/solr/solr-ref-guide/modules/configuration-guide/pages/index-segments-merging.adoc
index 72e70cf6f32..ca292a85a79 100644
--- a/solr/solr-ref-guide/modules/configuration-guide/pages/index-segments-merging.adoc
+++ b/solr/solr-ref-guide/modules/configuration-guide/pages/index-segments-merging.adoc
@@ -330,7 +330,7 @@ These settings affect how or when updates are made to an index.
=== deletionPolicy
Controls how commits are retained in case of rollback.
-The default is `SolrDeletionPolicy`, which take ths following parameters:
+The default is `SolrDeletionPolicy`, which takes the following parameters:
`maxCommitsToKeep`::
+
diff --git a/solr/solr-ref-guide/modules/configuration-guide/pages/requestdispatcher.adoc b/solr/solr-ref-guide/modules/configuration-guide/pages/requestdispatcher.adoc
index 8e9b154f823..ecc97008218 100644
--- a/solr/solr-ref-guide/modules/configuration-guide/pages/requestdispatcher.adoc
+++ b/solr/solr-ref-guide/modules/configuration-guide/pages/requestdispatcher.adoc
@@ -146,7 +146,7 @@ The content of this element will be sent as the value of the Cache-Control heade
This header is used to modify the default caching behavior of the requesting client.
The possible values for the Cache-Control header are defined by the HTTP 1.1 specification in http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9[Section 14.9].
-Setting the max-age field controls how long a client may re-use a cached response before requesting it again from the server.
+Setting the max-age field controls how long a client may reuse a cached response before requesting it again from the server.
This time interval should be set according to how often you update your index and whether or not it is acceptable for your application to use content that is somewhat out of date.
Setting `must-revalidate` will tell the client to validate with the server that its cached copy is still good before re-using it.
This will ensure that the most timely result is used, while avoiding a second fetch of the content if it isn't needed, at the cost of a request to the server to do the check.
diff --git a/solr/solr-ref-guide/modules/configuration-guide/pages/schema-factory.adoc b/solr/solr-ref-guide/modules/configuration-guide/pages/schema-factory.adoc
index 61843aadac4..0daa76e9019 100644
--- a/solr/solr-ref-guide/modules/configuration-guide/pages/schema-factory.adoc
+++ b/solr/solr-ref-guide/modules/configuration-guide/pages/schema-factory.adoc
@@ -85,7 +85,7 @@ The name can be anything other than `schema.xml`, as that name is reserved for t
=== ClassicIndexSchemaFactory
An alternative to using a managed schema is to explicitly configure a `ClassicIndexSchemaFactory`.
-This requires the use of a `schema.xml` file, and disallows any programatic changes to the Schema at run time.
+This requires the use of a `schema.xml` file, and disallows any programmatic changes to the Schema at run time.
The `schema.xml` file must be edited manually and is loaded only when the collection is loaded.
[source,xml]
diff --git a/solr/solr-ref-guide/modules/configuration-guide/pages/update-request-processors.adoc b/solr/solr-ref-guide/modules/configuration-guide/pages/update-request-processors.adoc
index 3abebae9747..fe2c22203e8 100644
--- a/solr/solr-ref-guide/modules/configuration-guide/pages/update-request-processors.adoc
+++ b/solr/solr-ref-guide/modules/configuration-guide/pages/update-request-processors.adoc
@@ -339,7 +339,7 @@ Alternatively, the processor offers a "permissive" mode (`permissiveMode=true`)
{solr-javadocs}/core/org/apache/solr/update/processor/NumFieldLimitingUpdateRequestProcessorFactory.html[NumFieldLimitingUpdateRequestProcessorFactory]:: Fails update requests once a core has exceeded a configurable "maximum" number of fields.
+
-Solr performance can degrade and even become unstable if cores accumulate too many (e.g. more than 500) fields. The "NumFieldLimiting" URP is offered as a safeguard that helps users notice potentially-dangerous schema design and/or mis-use of dynamic fields, before these performance and stability problems would manifest.
+Solr performance can degrade and even become unstable if cores accumulate too many (e.g. more than 500) fields. The "NumFieldLimiting" URP is offered as a safeguard that helps users notice potentially-dangerous schema design and/or misuse of dynamic fields, before these performance and stability problems would manifest.
Note that the field count an index reports can be influenced by deleted (but not yet purged) documents, and may vary from replica to replica.
In order to avoid these sort of discrepancies between replicas, use of this URP should almost always precede DistributedUpdateProcessor in when running in SolrCloud mode.
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/authentication-and-authorization-plugins.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/authentication-and-authorization-plugins.adoc
index 176fc3a5932..5ff8199d17c 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/authentication-and-authorization-plugins.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/authentication-and-authorization-plugins.adoc
@@ -227,7 +227,7 @@ To support rolling restarts from older versions, Solr can be configured to accep
If the `SolrAuthV2` header is present but fails validation, then Solr will not fall back to checking `SolrAuth`. The legacy authentication headers will only be consulted when the newest headers are not present.
-Unkown values for `solr.pki.acceptVersion` will emit a warning log message but will not cause errors to more smoothly support future protocol revisions.
+Unknown values for `solr.pki.acceptVersion` will emit a warning log message but will not cause errors to more smoothly support future protocol revisions.
The timeout is configurable through a system property called `pkiauth.ttl`.
For example, if you wish to increase the time-to-live to 10 seconds (10,000 milliseconds), start each node with a property `'-Dpkiauth.ttl=10000'`.
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/backup-restore.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/backup-restore.adoc
index 57d874ef932..6b48bc179e1 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/backup-restore.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/backup-restore.adoc
@@ -726,13 +726,13 @@ When using the Backup & Restore Collections API Calls, the **`location`** option
All the above options will resolve to the same directory in your S3 Bucket: `dir/in/bucket`.
Pre-Creation::
-The location must already exist within your S3 bucket before you can preform any backup operations with that location.
+The location must already exist within your S3 bucket before you can perform any backup operations with that location.
+
**Please note that the directory you create in S3 cannot begin with a `/`, as `locations` are stripped of any `/` prefix (shown in `Location Format`).**
Empty Location::
If you do not want to use a sub-directory within your bucket to store your backup, you can use any of the following location options: `/`, `s3:/`, `s3://`.
-However the location option is mandatory and you will recieve an error when trying to perform backup operations without it.
+However the location option is mandatory and you will receive an error when trying to perform backup operations without it.
====
An example configuration to enable S3 backups and restore can be seen below:
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/basic-authentication-plugin.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/basic-authentication-plugin.adoc
index 662f0a3bd59..4687fe5f6c0 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/basic-authentication-plugin.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/basic-authentication-plugin.adoc
@@ -58,7 +58,7 @@ There are several options defined in this example:
<2> The parameter `"blockUnknown":true` means that unauthenticated requests are not allowed to pass through.
<3> A user called 'solr', with a password `'SolrRocks'`, in the encoded format detailed above, has been defined.
<4> We override the `realm` property to display another text on the login prompt.
-<5> The parameter `"forwardCredentials":false` means we let Solr's PKI authenticaion handle distributed request instead of forwarding the Basic Auth header.
+<5> The parameter `"forwardCredentials":false` means we let Solr's PKI authentication handle distributed request instead of forwarding the Basic Auth header.
Save your settings to a file called `security.json` locally.
If you are using Solr in single-node installation, you should put this file in `$SOLR_HOME`.
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/collection-management.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/collection-management.adoc
index 6f89932a3a6..44e72cd491a 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/collection-management.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/collection-management.adoc
@@ -2256,7 +2256,7 @@ In this example:
This is considered successful.
* In the "successes" section, core_node23 was _not_ the leader for shard3, so leadership was assigned to that replica.
-The "Summary" section with the "Success" tag indicates that the command rebalanced all _active_ replicas with the preferredLeader property set as requried.
+The "Summary" section with the "Success" tag indicates that the command rebalanced all _active_ replicas with the preferredLeader property set as required.
If a replica cannot be made leader due to not being healthy (for example, it is on a Solr instance that is not running), it's also considered success.
[source,json]
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/installing-solr.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/installing-solr.adoc
index 497006c4de2..9b19d230b9c 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/installing-solr.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/installing-solr.adoc
@@ -73,7 +73,7 @@ tar zxf solr-{solr-full-version}.tgz
Once extracted, you are now ready to run Solr using the instructions provided in the <<Starting Solr>> section below.
-TIP: Windows includes the `tar` tool since Windows 10. Open a command line window and execute the above comamnd. There are also several 3rd party un-archiving tools that support `.tar` archives.
+TIP: Windows includes the `tar` tool since Windows 10. Open a command line window and execute the above command. There are also several 3rd party un-archiving tools that support `.tar` archives.
== Directory Layout
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/monitoring-with-prometheus-and-grafana.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/monitoring-with-prometheus-and-grafana.adoc
index 006888ede88..1146f8f2a41 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/monitoring-with-prometheus-and-grafana.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/monitoring-with-prometheus-and-grafana.adoc
@@ -618,7 +618,7 @@ Any metrics aggregations and/or filtering must be done on Grafana or the Prometh
=== Prometheus Configuration
-Like the Prometheus Exporter, the `prometheus.yml` needs to be configurated for the Prometheus Server to ingest metrics.
+Like the Prometheus Exporter, the `prometheus.yml` needs to be configured for the Prometheus Server to ingest metrics.
The difference is it must instead scrape the Metrics API with the `wt=prometheus` parameter directly from each host/port Solr is running on as in this example:
[source,plain]
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/securing-solr.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/securing-solr.adoc
index ca1b98307fd..f29d50f8d0a 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/securing-solr.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/securing-solr.adoc
@@ -75,7 +75,7 @@ The authorization plugins that ship with Solr are:
== Audit Logging
-Audit logging will record an audit trail of incoming reqests to your cluster, such as users being denied access to admin APIs.
+Audit logging will record an audit trail of incoming requests to your cluster, such as users being denied access to admin APIs.
Learn more about audit logging and how to implement an audit logger plugin in the section xref:audit-logging.adoc[].
== IP Access Control
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/solr-control-script-reference.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/solr-control-script-reference.adoc
index 6cab3f6789a..0cf4288bfbb 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/solr-control-script-reference.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/solr-control-script-reference.adoc
@@ -1385,7 +1385,7 @@ Trailing wildcards are supported when copying from localand must be quoted.
Other examples are:
-*Recursively copy a directory from local to ZooKeeper*: `bin/solr zk cp -r file:/apache/confgs/whatever/conf zk:/configs/myconf -z 111.222.333.444:2181`
+*Recursively copy a directory from local to ZooKeeper*: `bin/solr zk cp -r file:/apache/configs/whatever/conf zk:/configs/myconf -z 111.222.333.444:2181`
*Copy a single file from ZooKeeper to local*: `bin/solr zk cp zk:/configs/myconf/managed_schema /configs/myconf/managed_schema -z 111.222.333.444:2181`
@@ -1834,7 +1834,7 @@ The `package` command allows you to interact with Solr's xref:configuration-guid
== Snapshots and Backups
-The snapshots capablity of the CLI allows you to:
+The snapshots capability of the CLI allows you to:
* Create snapshotted view of your index
* List all the available snapshots
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/solr-on-hdfs.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/solr-on-hdfs.adoc
index 25548bfac2c..f99cff169ae 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/solr-on-hdfs.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/solr-on-hdfs.adoc
@@ -53,7 +53,7 @@ bin/solr start -Dsolr.directoryFactory=HdfsDirectoryFactory
This command starts Solr using the defined JVM properties.
-=== User-Managed Cluters and Single-Node Installations
+=== User-Managed Clusters and Single-Node Installations
For For user-managed clusters or single-node Solr installations, there are a few parameters you should modify before starting Solr.
These can be set in `solrconfig.xml` (more on that <<HdfsDirectoryFactory Parameters,below>>), or passed to the `bin/solr` script at startup.
@@ -246,7 +246,7 @@ s|Required |Default: none
The Kerberos principal that Solr should use to authenticate to secure Hadoop; the format of a typical Kerberos V5 principal is: `primary/instance@realm`.
== Update Log settings
-When using HDFS to store Solr indexes, it is recommended to also store the transaction logs on HDFS. This can be done by using the `solr.HdfsUpdateLog` update log hander class.
+When using HDFS to store Solr indexes, it is recommended to also store the transaction logs on HDFS. This can be done by using the `solr.HdfsUpdateLog` update log handler class.
The solrconfig.xml is often used to define an update log handler class name either using a variable reference or direct specification, for example:
[source,xml]
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/solrcloud-shards-indexing.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/solrcloud-shards-indexing.adoc
index d01ce96f3b9..36f0701e473 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/solrcloud-shards-indexing.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/solrcloud-shards-indexing.adoc
@@ -25,7 +25,7 @@ For example, you might have a collection where the "country" field of each docum
A different collection might simply use a "hash" on the uniqueKey of each document to determine its Shard.
There is support for distributing both the index process and the queries automatically, and ZooKeeper provides failover and load balancing.
-As well as supporting replication, automatic index spliting to shards, there is support for automatic routing of documents to specific shards by a sharding strategy.
+As well as supporting replication, automatic index splitting into shards, there is support for automatic routing of documents to specific shards by a sharding strategy.
Additionally, every shard can have multiple replicas for additional robustness.
== Leaders and Replicas
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/solrj.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/solrj.adoc
index e2936efa9a3..13d69bba824 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/solrj.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/solrj.adoc
@@ -120,7 +120,7 @@ Unless otherwise specified, SolrJ expects these URLs to point to the root Solr p
A few notable exceptions to this are described below:
-- *Http2SolrClient* - Users of `Http2SolrClient` may choose to skip providing a root URL to their client, in favor of specifing the URL as a argument for the `Http2SolrClient.requestWithBaseUrl` method.
+- *Http2SolrClient* - Users of `Http2SolrClient` may choose to skip providing a root URL to their client, in favor of specifying the URL as an argument for the `Http2SolrClient.requestWithBaseUrl` method.
Calling any other `request` methods on a URL-less `Http2SolrClient` will result in an `IllegalArgumentException`.
- *LBHttpSolrClient* and *LBHttp2SolrClient* - Solr's "load balancing" clients are frequently used to round-robin requests across a set of replicas or cores.
URLs are still expected to point to the Solr root (i.e. "/solr"), but to support this use-case the URLs are often supplemented by an additional parameter to specify the targeted core.
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/taking-solr-to-production.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/taking-solr-to-production.adoc
index 4adb5fd6b57..2d904a5d1ff 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/taking-solr-to-production.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/taking-solr-to-production.adoc
@@ -422,7 +422,7 @@ Then, change or add this line to the file:
vm.swappiness = 1
----
-Alternatively, you can change the setting temporarily by running this comamnd:
+Alternatively, you can change the setting temporarily by running this command:
[source,bash]
----
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/zookeeper-access-control.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/zookeeper-access-control.adoc
index c976feb96a3..d931ee1cd01 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/zookeeper-access-control.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/zookeeper-access-control.adoc
@@ -454,9 +454,9 @@ Attempting to do so while Solr is running may result in inconsistent state and s
The VM properties `zkCredentialsInjector`, `zkACLProvider` and `zkCredentialsProvider`, included in the `SOLR_ZK_CREDS_AND_ACLS` environment variable in `solr.in.*`, control the conversion:
* The Credentials Injector reads the credentials and pass them to the Credentials Provider.
-When omitted, the process will use no credentials (suitable for an unsecure configuration).
+When omitted, the process will use no credentials (suitable for an insecure configuration).
* The Credentials Provider uses the credentials of the user with admin privileges on the nodes.
-When omitted, the process will use no credentials (suitable for an unsecure configuration).
+When omitted, the process will use no credentials (suitable for an insecure configuration).
* The ACL Provider will be used to compute the new ACLs.
When omitted, the process will set all permissions to all users, removing any security present.
diff --git a/solr/solr-ref-guide/modules/indexing-guide/pages/language-detection.adoc b/solr/solr-ref-guide/modules/indexing-guide/pages/language-detection.adoc
index bf777c0345a..f4f5ab158f3 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/language-detection.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/language-detection.adoc
@@ -95,7 +95,7 @@ s|Required |Default: none
+
An OpenNLP language detection model.
+
-The OpenNLP project provides a pre-trained 103 language model on the http://opennlp.apache.org/models.html[OpenNLP site's model dowload page].
+The OpenNLP project provides a pre-trained 103 language model on the http://opennlp.apache.org/models.html[OpenNLP site's model download page].
Model training instructions are provided on the http://opennlp.apache.org/docs/{dep-version-opennlp}/manual/opennlp.html#tools.langdetect[OpenNLP website].
+
See xref:configuration-guide:resource-loading.adoc[] for information on where to put the model.
diff --git a/solr/solr-ref-guide/modules/indexing-guide/pages/partial-document-updates.adoc b/solr/solr-ref-guide/modules/indexing-guide/pages/partial-document-updates.adoc
index ad10ea3c4fc..46b81958ddc 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/partial-document-updates.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/partial-document-updates.adoc
@@ -253,7 +253,7 @@ May be specified as a single value.
`inc`::
Increments or decrements a numeric field's value by a specific amount, specified as a single integer or float.
-Postive amounts increment the field's value, and negative decrement.
+Positive amounts increment the field's value, and negative decrement.
[TIP]
====
diff --git a/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc b/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc
index 821c00dafb8..0b0e5045fb7 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/reindexing.adoc
@@ -95,7 +95,7 @@ plan to reindex your documents to avoid unintended behavior.
When upgrading between major versions (for example, from a 7.x release to 8.x), a best practice is to always reindex your data.
The reason for this is that subtle changes may occur in default field type definitions or the underlying code.
-Lucene works hard to insure one major version back-compatability, thus Solr 8x functions with indexes created with Solr 7x.
+Lucene works hard to insure one major version back-compatibility, thus Solr 8x functions with indexes created with Solr 7x.
However, given that this guarantee does _not_ apply to Solr X-2 (Solr 6x in this example) we still recommend completely reindexing when moving from Solr X-1 to Solr X.
[NOTE]
diff --git a/solr/solr-ref-guide/modules/indexing-guide/pages/schema-api.adoc b/solr/solr-ref-guide/modules/indexing-guide/pages/schema-api.adoc
index f5dc074e424..8f0d3c6a6ce 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/schema-api.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/schema-api.adoc
@@ -1608,7 +1608,7 @@ The query parameters can be added to the API request after a '?'.
Defines the format of the response.
The options are `json` or `xml`.
-==== Show Global Similary Response
+==== Show Global Similarity Response
The output will include the class name of the global similarity defined (if any).
diff --git a/solr/solr-ref-guide/modules/indexing-guide/pages/transforming-and-indexing-custom-json.adoc b/solr/solr-ref-guide/modules/indexing-guide/pages/transforming-and-indexing-custom-json.adoc
index f3fdd6f2153..2ad1e684cc9 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/transforming-and-indexing-custom-json.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/transforming-and-indexing-custom-json.adoc
@@ -338,7 +338,7 @@ If you are working in xref:schemaless-mode.adoc[], however, fields that don't ex
=== Reusing Parameters in Multiple Requests
-You can store and re-use parameters with Solr's xref:configuration-guide:request-parameters-api.adoc[].
+You can store and reuse parameters with Solr's xref:configuration-guide:request-parameters-api.adoc[].
Say we wanted to define parameters to split documents at the `exams` field, and map several other fields.
We could make an API request such as:
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/other-parsers.adoc b/solr/solr-ref-guide/modules/query-guide/pages/other-parsers.adoc
index 1bb9316f563..68a4c92b1c5 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/other-parsers.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/other-parsers.adoc
@@ -823,7 +823,7 @@ It would be more prudent to get the analyser from the schema.
ts.end();
----
-The schema will just define a multi-valued string value and an optional field to use at anlysis time - similar to above.
+The schema will just define a multi-valued string value and an optional field to use at analysis time - similar to the above.
[source,xml]
----
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/pagination-of-results.adoc b/solr/solr-ref-guide/modules/query-guide/pages/pagination-of-results.adoc
index 1c687869fb1..59ee7fe4193 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/pagination-of-results.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/pagination-of-results.adoc
@@ -117,7 +117,7 @@ If `id` is your uniqueKey field, then sort parameters like `id asc` and `name as
. Sorts including xref:indexing-guide:date-formatting-math.adoc[Date Math-based] functions that involve calculations relative to `NOW` will cause confusing results, since every document will get a new sort value on every subsequent request.
This can easily result in cursors that never end, and constantly return the same documents over and over – even if the documents are never updated.
+
-In this situation, choose & re-use a fixed value for the xref:indexing-guide:date-formatting-math.adoc#now[`NOW` request parameter] in all of your cursor requests.
+In this situation, choose & reuse a fixed value for the xref:indexing-guide:date-formatting-math.adoc#now[`NOW` request parameter] in all of your cursor requests.
. `sort` clauses containing the `score` pseudo-field should also be used with care in multi-replica SolrCloud deployments.
+
Scores rely on term statistics which may vary from replica to replica, causing the same document to score differently in each.
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/result-clustering.adoc b/solr/solr-ref-guide/modules/query-guide/pages/result-clustering.adoc
index 541ea99c363..c91b86661a0 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/result-clustering.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/result-clustering.adoc
@@ -211,7 +211,7 @@ In other words, if cluster _A_ has a higher score than cluster _B_, cluster _A_
Each cluster has an array of identifiers of documents belonging to it.
These identifiers correspond to the `uniqueKey` field declared in the schema.
-Sometimes cluster labels may not make much sense (this depends on many factors -- text in clustered fields, number of documents, algorithm paramerters).
+Sometimes cluster labels may not make much sense (this depends on many factors -- text in clustered fields, number of documents, algorithm parameters).
Also, some documents may be left out and not be clustered at all; these will be assigned to the synthetic _Other Topics_ group, marked with the `other-topics` property set to `true` (see the XML dump above for an example).
The score of the other topics group is zero.
@@ -459,7 +459,7 @@ Ideally, the engine should translate (or understand) the content of documents an
In reality, clustering algorithms are typically much simpler -- they infer similarity between documents from statistical properties of terms and phrases that occur in those documents.
So texts written in different languages will not cluster too well.
-To deal witht his situation the default clustering component implementation in Solr will try to first group all documents by their language and then apply clustering to each sub-group in that language.
+To deal with this situation the default clustering component implementation in Solr will try to first group all documents by their language and then apply clustering to each sub-group in that language.
It is recommended to store the language of each document as its separate field and point at it using the `clustering.languageField` configuration property described above.
== Tweaking Algorithm Settings
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/search-sample.adoc b/solr/solr-ref-guide/modules/query-guide/pages/search-sample.adoc
index dddf2e729c0..0a1e39eaf0e 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/search-sample.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/search-sample.adoc
@@ -26,7 +26,7 @@ This section provides an overview of the key functions for retrieving data for v
The `search` function can be used to search a SolrCloud 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 in *table* format.
+Zeppelin-Solr sends the `search(logs)` call to the `/stream` handler and displays the results in *table* format.
In the example the `search` function is passed only the name of the collection being searched.
This returns a result set of 10 records with all fields.
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/searching-nested-documents.adoc b/solr/solr-ref-guide/modules/query-guide/pages/searching-nested-documents.adoc
index 4ccf81f9dd5..124dce3b6de 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/searching-nested-documents.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/searching-nested-documents.adoc
@@ -272,7 +272,7 @@ The combination of these two parsers with the `[child] transformer enables seaml
Here for example is a query where:
* the (sku) documents returned must have a color of "RED"
-* the (sku) docments returned must be the descendents of root level (product) documents which have:
+* the (sku) documents returned must be the descendents of root level (product) documents which have:
** immediate child "manuals" documents which have:
*** "lifetime guarantee" in their content
* each return (sku) document also includes any descendent (manuals) documents it has
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/spatial-search.adoc b/solr/solr-ref-guide/modules/query-guide/pages/spatial-search.adoc
index 3efa0bfaf85..29992f99aa9 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/spatial-search.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/spatial-search.adoc
@@ -682,7 +682,7 @@ The entire value is null if there is no matching spatial data.
If `format=png` then the output key is `counts_png`.
It's a base-64 encoded string of a 4-byte PNG.
The PNG logically holds exactly the same data that the ints2D format does.
-Note that the alpha channel byte is flipped to make it easier to view the PNG for diagnostic purposes, since otherwise counts would have to exceed 2^24 before it becomes non-opague.
+Note that the alpha channel byte is flipped to make it easier to view the PNG for diagnostic purposes, since otherwise counts would have to exceed 2^24 before it becomes non-opaque.
Thus counts greater than this value will become opaque.
== BBoxField
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/sql-query.adoc b/solr/solr-ref-guide/modules/query-guide/pages/sql-query.adoc
index f6f768fc465..6a5731c1458 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/sql-query.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/sql-query.adoc
@@ -171,7 +171,7 @@ The SQL query interface supports and pushes down most common SQL operators, spec
|>= |Greater than or equals |`fielda >= 10` |`fielda:[10 TO *]`
|< |Less than |`fielda < 10` |`fielda:[* TO 10}`
|\<= |Less than or equals |`fielda \<= 10` |`fielda:[* TO 10]`
-|IN |Specify multiple values (shorthand for multiple OR clasues) |`fielda IN (10,20,30)` |`(fielda:10 OR fielda:20 OR fielda:30)`
+|IN |Specify multiple values (shorthand for multiple OR clauses) |`fielda IN (10,20,30)` |`(fielda:10 OR fielda:20 OR fielda:30)`
|LIKE |Wildcard match on string or text fields |`fielda LIKE 'day%'` |`{!complexphrase}fielda:"day*"`
|BETWEEN |Range match |`fielda BETWEEN 2 AND 4` |`fielda: [2 TO 4]`
|IS NULL |Match columns with null value |`fielda IS NULL` |+++(*:* -field:*)+++
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/standard-query-parser.adoc b/solr/solr-ref-guide/modules/query-guide/pages/standard-query-parser.adoc
index 43f79bd652b..56629af9a43 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/standard-query-parser.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/standard-query-parser.adoc
@@ -438,7 +438,7 @@ There is no limitation on the number of terms that match (as there was in past v
=== Specifying Dates and Times
-Queries against date based fields must use the xref:indexing-guide:date-formatting-math.adoc[appropriate date formating].
+Queries against date based fields must use the xref:indexing-guide:date-formatting-math.adoc[appropriate date formatting].
Queries for exact date values will require quoting or escaping since `:` is the parser syntax used to denote a field query:
* `createdate:1976-03-06T23\:59\:59.999Z`
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/stream-decorator-reference.adoc b/solr/solr-ref-guide/modules/query-guide/pages/stream-decorator-reference.adoc
index 28a570ffae4..608ee65b06c 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/stream-decorator-reference.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/stream-decorator-reference.adoc
@@ -1213,7 +1213,7 @@ It executes on all the documents and the result bitset is cached in the filterCa
For a `parallel` stream with the same number of workers and `partitionKeys` the first query would be slower than subsequent queries.
A trick to not pay the penalty for the first slow query would be to use a warmup query for every new searcher.
-The following is a `solrconfig.xml` snippet for 2 workers and "year_i" as the `partionKeys`.
+The following is a `solrconfig.xml` snippet for 2 workers and "year_i" as the `partitionKeys`.
[source,text]
----
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/stream-evaluator-reference.adoc b/solr/solr-ref-guide/modules/query-guide/pages/stream-evaluator-reference.adoc
index 61c17c96b31..a108bd21747 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/stream-evaluator-reference.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/stream-evaluator-reference.adoc
@@ -1822,7 +1822,7 @@ The supported continuous distribution functions are:
<<empiricalDistribution>>, <<triangularDistribution>>, <<weibullDistribution>>,
<<uniformDistribution>>, <<constantDistribution>>
-The supported discreet distributions are:
+The supported discrete distributions are:
<<poissonDistribution>>, <<binomialDistribution>>, <<enumeratedDistribution>>, <<zipFDistribution>>,
<<geometricDistribution>>, <<uniformIntegerDistribution>>
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/stream-source-reference.adoc b/solr/solr-ref-guide/modules/query-guide/pages/stream-source-reference.adoc
index a4213776f6b..07c79689daa 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/stream-source-reference.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/stream-source-reference.adoc
@@ -225,7 +225,7 @@ This can be used to retrieve the features if they are stored in a SolrCloud coll
* `field`: (Mandatory) The text field to extract the features from.
* `outcome`: (Mandatory) The field that defines the class, positive or negative
* `numTerms`: (Mandatory) How many feature terms to extract.
-* `positiveLabel`: (defaults to 1) The value in the outcome field that defines a postive outcome.
+* `positiveLabel`: (defaults to 1) The value in the outcome field that defines a positive outcome.
=== features Syntax
diff --git a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc
index fa08dc0d287..fd15a943f5b 100644
--- a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc
+++ b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-9.adoc
@@ -252,7 +252,7 @@ TIP: Users who cannot upgrade their Docker engine will need to specify the docke
* Streaming Expressions have been moved out of Solrj core into its own module called `solrj-streaming`.
This change will only affect users that have used streaming expression classes in clients outside
of Solr. Streaming expressions sent to the /stream handler will still operate exactly as before.
-External clients using streaming expression classes will need to update their depenencies to reference
+External clients using streaming expression classes will need to update their dependencies to reference
the `solrj-streaming` artifacts under the `org.apache.solr` groupId.
=== Deprecations