This is an automated email from the ASF dual-hosted git repository.
epugh pushed a commit to branch branch_10_0
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/branch_10_0 by this push:
new 55389d8fb09 Copilot/check typos and grammar (#3800)
55389d8fb09 is described below
commit 55389d8fb09226d42323af14c0bfe55476eb5fbe
Author: Eric Pugh <[email protected]>
AuthorDate: Fri Oct 24 11:00:38 2025 -0400
Copilot/check typos and grammar (#3800)
---------
Co-authored-by: copilot-swe-agent[bot]
<[email protected]>
Co-authored-by: epugh <[email protected]>
Co-authored-by: Christine Poerschke <[email protected]>
---
dev-docs/FAQ.adoc | 2 +-
dev-docs/README.adoc | 2 +-
dev-docs/asf-jenkins.adoc | 2 +-
dev-docs/ref-guide/antora.adoc | 2 +-
dev-docs/v2-api-conventions.adoc | 2 +-
.../modules/configuration-guide/pages/index-segments-merging.adoc | 4 ++--
solr/solr-ref-guide/modules/deployment-guide/pages/aliases.adoc | 2 +-
.../modules/deployment-guide/pages/backup-restore.adoc | 2 +-
.../deployment-guide/pages/basic-authentication-plugin.adoc | 2 +-
.../deployment-guide/pages/rule-based-authorization-plugin.adoc | 2 +-
.../deployment-guide/pages/solr-control-script-reference.adoc | 4 ++--
.../modules/deployment-guide/pages/zookeeper-ensemble.adoc | 2 +-
.../modules/getting-started/pages/tutorial-paramsets.adoc | 2 +-
solr/solr-ref-guide/modules/query-guide/pages/faceting.adoc | 2 +-
.../modules/query-guide/pages/probability-distributions.adoc | 2 +-
solr/solr-ref-guide/modules/query-guide/pages/search-sample.adoc | 8 ++++----
.../modules/query-guide/pages/searching-nested-documents.adoc | 2 +-
.../modules/upgrade-notes/pages/major-changes-in-solr-6.adoc | 2 +-
18 files changed, 23 insertions(+), 23 deletions(-)
diff --git a/dev-docs/FAQ.adoc b/dev-docs/FAQ.adoc
index 23621db8e5c..4f0d6a312b8 100644
--- a/dev-docs/FAQ.adoc
+++ b/dev-docs/FAQ.adoc
@@ -23,7 +23,7 @@ created a branch that can be deleted.
You can review instructions for running Solr in Docker in the
xref:running-in-docker.adoc[Running in Docker developer doc].
-=== Whats the fastest build lifecycle for frontend work on Solr Admin?
+=== What's the fastest build lifecycle for frontend work on Solr Admin?
Run `gradle dev`, and then `cd ./packaging/build/dev/`. Fire up your cluster
via `bin/solr start -e cloud --no-prompt` and then as you make changes to
assets in `/solr/webapp/web`,
diff --git a/dev-docs/README.adoc b/dev-docs/README.adoc
index bb0d17d75f9..17d64ccbb54 100644
--- a/dev-docs/README.adoc
+++ b/dev-docs/README.adoc
@@ -25,7 +25,7 @@ sources of information for learning about developing on Solr:
details, see the information in `/solr/licenses/README.committers.txt`.
3. The Solr Reference Guide, which provides primarily end user oriented
documentation.
-However, the Ref Guide hosts it's own documentation on how to write Ref Guide
content.
+However, the Ref Guide hosts its own documentation on how to write Ref Guide
content.
There are a number of tools related to doing development on Solr available in
the `/dev-tools`
directory.
diff --git a/dev-docs/asf-jenkins.adoc b/dev-docs/asf-jenkins.adoc
index 62cc39053a5..312ac098ec6 100644
--- a/dev-docs/asf-jenkins.adoc
+++ b/dev-docs/asf-jenkins.adoc
@@ -47,7 +47,7 @@ With a few steps, Solr committers can access our project's
Jenkins agent VMs via
3. SSH into the desired box with: `ssh <apache-id>@$HOSTNAME` (where
`$HOSTNAME` is either `lucene1-us-west.apache.org` or
`lucene-us-west.apache.org`)
Often, SSH access on the boxes is not sufficient, and administrators require
"root" access to diagnose and solve problems.
-Sudo/su priveleges can be accessed via a one-time pad ("OTP") challenge,
managed by the "Orthrus PAM" module.
+Sudo/su privileges can be accessed via a one-time pad ("OTP") challenge,
managed by the "Orthrus PAM" module.
Users in need of root access can perform the following steps:
1. Open the ASF's [OTP Generator
Tool](https://selfserve.apache.org/otp-calculator.html) in your browser of
choice
diff --git a/dev-docs/ref-guide/antora.adoc b/dev-docs/ref-guide/antora.adoc
index 2f3306f35c7..a363cb3fe46 100644
--- a/dev-docs/ref-guide/antora.adoc
+++ b/dev-docs/ref-guide/antora.adoc
@@ -31,7 +31,7 @@ Antora is an open source project, online at
https://antora.org/.
The following sections describe the main features of Antora that you will
encounter while working with the Solr Ref Guide.
=== Asciidoctor
-Antora uses Asciidoctor.js by default as it's content markup language.
+Antora uses Asciidoctor.js by default as its content markup language.
Read more on the Solr xref:asciidoc-syntax.adoc[AsciiDoc Syntax] page, or on
Antora's guide: https://docs.antora.org/antora/latest/asciidoc/asciidoc/
diff --git a/dev-docs/v2-api-conventions.adoc b/dev-docs/v2-api-conventions.adoc
index f27eae76c44..d40d7dd4a48 100644
--- a/dev-docs/v2-api-conventions.adoc
+++ b/dev-docs/v2-api-conventions.adoc
@@ -62,7 +62,7 @@ Solr's "modify collection" functionality uses partial update
semantics, but the
For use within the v2 API, the four "popular" HTTP methods have the following
semantics and implications:
-* `GET` - used for non-mutating (i.e. "read only") requests. Most often used
to list elements of a particular resource type, or fetch information about
about a specific named resource.
+* `GET` - used for non-mutating (i.e. "read only") requests. Most often used
to list elements of a particular resource type, or fetch information about a
specific named resource.
* `POST` - used for non-idempotent resource modifications.
* `PUT` - used for idempotent resource modifications.
* `DELETE` - Used to delete or cleanup resource
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 5a917887ba5..a06851de955 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
@@ -141,7 +141,7 @@ Faster index updates also means shorter commit turnaround
times, which means mor
=== Controlling Deleted Document Percentages
When a document is deleted or updated, the document is marked as deleted but
it not removed from the index until the segment is merged.
-There are two parameters that can can be adjusted when using the default
`TieredMergePolicy` that influence the number of deleted documents in an index.
+There are two parameters that can be adjusted when using the default
`TieredMergePolicy` that influence the number of deleted documents in an index.
`forceMergeDeletesPctAllowed`::
+
@@ -285,7 +285,7 @@ The LockFactory options specify the locking implementation
to use.
The set of valid lock type options depends on the
xref:index-location-format.adoc[DirectoryFactory] you have configured.
-The values listed below are are supported by `StandardDirectoryFactory` (the
default):
+The values listed below are supported by `StandardDirectoryFactory` (the
default):
* `native` (default) uses `NativeFSLockFactory` to specify native OS file
locking.
If a second Solr process attempts to access the directory, it will fail.
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/aliases.adoc
b/solr/solr-ref-guide/modules/deployment-guide/pages/aliases.adoc
index cea787cf640..7e1dc1d85d3 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/aliases.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/aliases.adoc
@@ -213,7 +213,7 @@ It may not be avoided and is necessary to support future
features.
=== Dimensional Routed Aliases
-For cases where the desired segregation of of data relates to two fields and
combination into a single field during indexing is impractical, or the TRA
behavior is desired across multiple categories, Dimensional Routed aliases may
be used.
+For cases where the desired segregation of data relates to two fields and
combination into a single field during indexing is impractical, or the TRA
behavior is desired across multiple categories, Dimensional Routed aliases may
be used.
This feature has been designed to handle an arbitrary number and combination
of category and time dimensions in any order, but users are cautioned to
carefully consider the total number of collections that will result from such
configurations.
Collection counts in the high hundreds or low 1000's begin to pose significant
challenges with ZooKeeper.
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 cc5454cb2e2..e6fa3e4d403 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
@@ -204,7 +204,7 @@ If no repository is specified then the local filesystem
repository will be used
The `restore` command is an asynchronous call.
Once the restore is complete the data reflected will be of the backed up index
which was restored.
-Only one `restore` call can can be made against a core at one point in time.
+Only one `restore` call can be made against a core at one point in time.
While an ongoing restore operation is happening subsequent calls for restoring
will throw an exception.
=== Restore Status API
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 4c0aa1821f0..490f932582e 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
@@ -386,7 +386,7 @@ SOLR_AUTH_TYPE="basic"
SOLR_AUTHENTICATION_OPTS="-Dsolr.security.auth.basicauth.credentials=solr:SolrRocks"
----
-This tells the `bin/solr` command line to to use "basic" as the type of
authentication, and to pass credentials with the user-name "solr" and password
"SolrRocks".
+This tells the `bin/solr` command line to use "basic" as the type of
authentication, and to pass credentials with the user-name "solr" and password
"SolrRocks".
Alternatively, the `SOLR_AUTHENTICATION_OPTS` can take a path to a
configuration file, as in:
diff --git
a/solr/solr-ref-guide/modules/deployment-guide/pages/rule-based-authorization-plugin.adoc
b/solr/solr-ref-guide/modules/deployment-guide/pages/rule-based-authorization-plugin.adoc
index d756a3e4f7f..6996a7277f4 100644
---
a/solr/solr-ref-guide/modules/deployment-guide/pages/rule-based-authorization-plugin.adoc
+++
b/solr/solr-ref-guide/modules/deployment-guide/pages/rule-based-authorization-plugin.adoc
@@ -64,7 +64,7 @@ Permissions control which roles (and consequently which
users) have access to wh
Each permission has two main components: a description of the APIs the
permission applies to, and a list of the roles that should be allowed to access
to this set of APIs.
-Administrators can use permissions from a list of predefined options or define
their own custom permissions, are are free to mix and match both.
+Administrators can use permissions from a list of predefined options or define
their own custom permissions, they are free to mix and match both.
== Configuring the Rule-Based Authorization Plugins
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 842d294b06e..f8d50fabafb 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
@@ -1663,8 +1663,8 @@ Name of the collection to run an export against.
+
The file format of the export, `json` (default) or `jsonl` or `javabin`, this
also specifies the file extension to be used.
`json` and `jsonl` both export documents in the same format as using
`wt=json`. The `json` output file is suitable for
-immediately posting back to solr via the `/update/json` endpoint. `jsonl`
outputs each Solr document on it's own line,
-and it useful for parallel processing tasks. Learn more at
https://jsonlines.org/.
+immediately posting back to solr via the `/update/json` endpoint. `jsonl`
outputs each Solr document on its own line,
+and is useful for parallel processing tasks. Learn more at
https://jsonlines.org/.
Choosing `javabin` exports in the native binary Solr format and is compact and
faster to import.
`--output <path>`::
diff --git
a/solr/solr-ref-guide/modules/deployment-guide/pages/zookeeper-ensemble.adoc
b/solr/solr-ref-guide/modules/deployment-guide/pages/zookeeper-ensemble.adoc
index 7bc232bb5ff..d422b89572a 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/zookeeper-ensemble.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/zookeeper-ensemble.adoc
@@ -377,7 +377,7 @@ But note that Solr will only be able to talk to the servers
listed in the static
If your ensemble is or will be shared among other systems besides Solr, you
should consider defining application-specific _znodes_, or a hierarchical
namespace that will only include Solr's files.
-Once you create a znode for each application, you add it's name, also called a
_chroot_, to the end of your connect string whenever you tell Solr where to
access ZooKeeper.
+Once you create a znode for each application, you add its name, also called a
_chroot_, to the end of your connection string whenever you tell Solr where to
access ZooKeeper.
Creating a chroot is done with a `bin/solr` command:
diff --git
a/solr/solr-ref-guide/modules/getting-started/pages/tutorial-paramsets.adoc
b/solr/solr-ref-guide/modules/getting-started/pages/tutorial-paramsets.adoc
index 1b769e2322c..84f3e56b169 100644
--- a/solr/solr-ref-guide/modules/getting-started/pages/tutorial-paramsets.adoc
+++ b/solr/solr-ref-guide/modules/getting-started/pages/tutorial-paramsets.adoc
@@ -143,7 +143,7 @@ Search for 'harry potter' with Algorithm *B*:
http://localhost:8983/solr/films/query?q=harry%20potter&useParams=algo_b
We are returning only the four Harry Potter movies, leading to more precise
results!
-We can say that we believe Algorithm *B* is better then Algorithm *A*, at
least for this one query.
+We can say that we believe Algorithm *B* is better than Algorithm *A*, at
least for this one query.
You can validate this hypothesis with online A/B testing to confirm with real
users that Algorithm *B* is better overall.
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/faceting.adoc
b/solr/solr-ref-guide/modules/query-guide/pages/faceting.adoc
index 9196ad4f6f7..e45b17ea500 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/faceting.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/faceting.adoc
@@ -360,7 +360,7 @@ f.lastModified_dt.facet.range.gap=+1DAY
How to handle cases where the `facet.range.gap` does not divide evenly between
`facet.range.start` and `facet.range.end`.
+
If `true`, the last range constraint will have the `facet.range.end` value as
an upper bound.
-If `false`, the last range will have the smallest possible upper bound greater
then `facet.range.end` so the range is the exact width of the specified range
gap.
+If `false`, the last range will have the smallest possible upper bound greater
than `facet.range.end` so the range is the exact width of the specified range
gap.
+
This parameter can be specified on a per field basis with the syntax
`f.<fieldname>.facet.range.hardend`.
diff --git
a/solr/solr-ref-guide/modules/query-guide/pages/probability-distributions.adoc
b/solr/solr-ref-guide/modules/query-guide/pages/probability-distributions.adoc
index 9ed35fc5329..f688811ff2e 100644
---
a/solr/solr-ref-guide/modules/query-guide/pages/probability-distributions.adoc
+++
b/solr/solr-ref-guide/modules/query-guide/pages/probability-distributions.adoc
@@ -145,7 +145,7 @@ image::math-expressions/zipf.png[]
The `cumulativeProbability` function can be used with all probability
distributions to calculate the cumulative probability of encountering a
specific random variable within a specific distribution.
-Below is example of calculating the cumulative probability of a random
variable within a normal distribution.
+Below is an example of calculating the cumulative probability of a random
variable within a normal distribution.
[source,text]
----
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 0a1e39eaf0e..38cd2150d6f 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
@@ -228,7 +228,7 @@ In this example the focus will be on finding correlated
nodes in a time series g
The example below finds stock tickers whose daily movements tend to be
correlated with the 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) is greater then .25.
+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) is greater than .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.
The `nodes` function wraps the `search` function and operates over its results.
@@ -236,7 +236,7 @@ The `walk` parameter maps a field from the search results
to a field in the inde
In this case the `yearMonthDay_s` is mapped back to the `yearMonthDay_s`
field in the same index.
This will find records that have same `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.
+This will find all records on the matching days that have a 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.
@@ -245,8 +245,8 @@ This will count the number of times each ticker appears in
the breadth first sea
Finally, the `top` function selects the top 5 tickers by count and returns
them.
The result below shows the ticker symbols in the `nodes` field and the counts
for each node.
-Notice *jpm* is first, which shows how many days *jpm* had a change greater
then .25 in this time period.
-The next set of ticker symbols (*mtb*, *slvb*, *gs* and *pnc*) are the symbols
with the highest number of days with a change greater then .25 on the same days
that *jpm* had a change greater then .25.
+Notice *jpm* is first, which shows how many days *jpm* had a change greater
than .25 in this time period.
+The next set of ticker symbols (*mtb*, *slvb*, *gs* and *pnc*) are the symbols
with the highest number of days with a change greater than .25 on the same days
that *jpm* had a change greater than .25.
image::math-expressions/nodestab.png[]
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 92a99b4d1db..7f85d8330bf 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
@@ -149,7 +149,7 @@ $ curl 'http://localhost:8983/solr/gettingstarted/select'
-d 'omitHeader=true' -
In this example we've used `\*:* -\_nest_path_:*` as our
xref:block-join-query-parser.adoc#block-mask[`of` parameter] to indicate we
want to consider all documents which don't have a nest path -- i.e., all "root"
level document -- as the set of possible parents.
By changing the `of` parameter to match ancestors at specific `\_nest_path_`
levels, we can narrow down the list of children we return.
-In the query below, we search for all descendants of `skus` (using an `of`
parameter that identifies all documents that do _not_ have a `\_nest_path_`
with the prefix `/skus/*`) with a `price_i` less then `50`:
+In the query below, we search for all descendants of `skus` (using an `of`
parameter that identifies all documents that do _not_ have a `\_nest_path_`
with the prefix `/skus/*`) with a `price_i` less than `50`:
[source,text]
----
diff --git
a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-6.adoc
b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-6.adoc
index ace04dd3b05..dd9cd2ad082 100644
---
a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-6.adoc
+++
b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-6.adoc
@@ -51,7 +51,7 @@ Replication across data centers is now possible with Cross
Data Center Replicati
=== Graph QueryParser
-A new xref:query-guide:other-parsers.adoc#graph-query-parser[`graph` query
parser] makes it possible to to graph traversal queries of Directed (Cyclic)
Graphs modelled using Solr documents.
+A new xref:query-guide:other-parsers.adoc#graph-query-parser[`graph` query
parser] makes it possible to run graph traversal queries of Directed (Cyclic)
Graphs modelled using Solr documents.
[[major-5-6-docvalues]]
=== DocValues
