You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@polaris.apache.org by yu...@apache.org on 2026/08/14 04:39:06 UTC
(polaris) branch main updated: Fix typos and grammar issues in the documentation (#5283)
This is an automated email from the ASF dual-hosted git repository.
flyrain pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/polaris.git
The following commit(s) were added to refs/heads/main by this push:
new c86e2d23e7 Fix typos and grammar issues in the documentation (#5283)
c86e2d23e7 is described below
commit c86e2d23e7eba383f08b0ec0e876dc441c40f099
Author: Xiaodong DENG <xd...@gmail.com>
AuthorDate: Thu Aug 13 21:39:01 2026 -0700
Fix typos and grammar issues in the documentation (#5283)
---
.../java/org/apache/polaris/core/config/FeatureConfiguration.java | 8 ++++----
.../org/apache/polaris/service/storage/aws/S3AccessConfig.java | 2 +-
site/content/in-dev/unreleased/admin-tool.md | 4 ++--
.../configuration/config-sections/flags-polaris_features.md | 8 ++++----
.../configuration/config-sections/smallrye-polaris_storage.md | 2 +-
site/content/in-dev/unreleased/downstream-build.md | 2 +-
site/content/in-dev/unreleased/entities.md | 2 +-
site/content/in-dev/unreleased/evolution.md | 2 +-
site/content/in-dev/unreleased/generic-table.md | 8 ++++----
.../getting-started/creating-a-catalog/catalog-azure.md | 2 +-
.../unreleased/getting-started/creating-a-catalog/catalog-gcs.md | 2 +-
.../getting-started/creating-a-catalog/s3/catalog-aws.md | 2 +-
.../getting-started/creating-a-catalog/s3/catalog-minio.md | 2 +-
.../getting-started/creating-a-catalog/s3/catalog-ozone.md | 4 ++--
.../in-dev/unreleased/getting-started/deploying-polaris/_index.md | 4 ++--
.../getting-started/deploying-polaris/cloud-deploy/deploy-aws.md | 2 +-
.../in-dev/unreleased/getting-started/using-polaris/_index.md | 2 +-
site/content/in-dev/unreleased/helm-chart/dev.md | 2 +-
site/content/in-dev/unreleased/helm-chart/production.md | 2 +-
site/content/in-dev/unreleased/metastores/relational-jdbc.md | 2 +-
site/content/in-dev/unreleased/polaris-spark-client.md | 8 ++++----
site/content/in-dev/unreleased/realm.md | 6 +++---
site/content/in-dev/unreleased/telemetry.md | 2 +-
23 files changed, 40 insertions(+), 40 deletions(-)
diff --git a/polaris-core/src/main/java/org/apache/polaris/core/config/FeatureConfiguration.java b/polaris-core/src/main/java/org/apache/polaris/core/config/FeatureConfiguration.java
index 571e5e0f43..b7ef2fe143 100644
--- a/polaris-core/src/main/java/org/apache/polaris/core/config/FeatureConfiguration.java
+++ b/polaris-core/src/main/java/org/apache/polaris/core/config/FeatureConfiguration.java
@@ -454,7 +454,7 @@ public class FeatureConfiguration<T> extends PolarisConfiguration<T> {
.description(
"The duration of time that vended storage credentials are valid for. Support for"
+ " longer (or shorter) durations is dependent on the storage provider. GCS"
- + " current does not respect this value.")
+ + " currently does not respect this value.")
.defaultValue(60 * 60) // 1 hour
.buildFeatureConfiguration();
@@ -671,7 +671,7 @@ public class FeatureConfiguration<T> extends PolarisConfiguration<T> {
.key("ALLOW_SETTING_SUB_CATALOG_RBAC_FOR_FEDERATED_CATALOGS")
.description(
"If set to true (default), Polaris will allow setting or changing "
- + "catalog property polaris.config.enable-sub-catalog-rbac-for-federated-catalogs."
+ + "catalog property polaris.config.enable-sub-catalog-rbac-for-federated-catalogs. "
+ "If set to false, Polaris will disallow setting or changing the above catalog property")
.defaultValue(true)
.buildFeatureConfiguration();
@@ -682,7 +682,7 @@ public class FeatureConfiguration<T> extends PolarisConfiguration<T> {
.key("ALLOW_DROPPING_NON_EMPTY_PASSTHROUGH_FACADE_CATALOG")
.description(
"If enabled, allow dropping a passthrough-facade catalog even if it contains namespaces or tables. "
- + "passthrough-facade catalogs may contain leftover entities when syncing with source catalog."
+ + "passthrough-facade catalogs may contain leftover entities when syncing with source catalog. "
+ "In the short term these entities will be ignored, in the long term there will be method/background job to clean them up.")
.catalogConfig("polaris.config.allow-dropping-non-empty-passthrough-facade-catalog")
.defaultValue(false)
@@ -740,7 +740,7 @@ public class FeatureConfiguration<T> extends PolarisConfiguration<T> {
.description(
"Jitter factor (0.0 to 1.0) applied to retry delays for Azure API requests. "
+ "The jitter is applied as a random percentage of the computed exponential backoff delay. "
- + "For example, 0.5 means up to 50%% random jitter will be added to each retry delay. "
+ + "For example, 0.5 means up to 50% random jitter will be added to each retry delay. "
+ "Helps prevent thundering herd when multiple requests fail simultaneously.")
.defaultValue(0.5)
.buildFeatureConfiguration();
diff --git a/runtime/service/src/main/java/org/apache/polaris/service/storage/aws/S3AccessConfig.java b/runtime/service/src/main/java/org/apache/polaris/service/storage/aws/S3AccessConfig.java
index 935770be80..65679557c4 100644
--- a/runtime/service/src/main/java/org/apache/polaris/service/storage/aws/S3AccessConfig.java
+++ b/runtime/service/src/main/java/org/apache/polaris/service/storage/aws/S3AccessConfig.java
@@ -66,7 +66,7 @@ public interface S3AccessConfig {
/** Override default max idle time of a pooled connection. */
Optional<Duration> connectionMaxIdleTime();
- /** Override default time-time of a pooled connection. */
+ /** Override default time-to-live of a pooled connection. */
Optional<Duration> connectionTimeToLive();
/** Override default behavior whether to expect an HTTP/100-Continue. */
diff --git a/site/content/in-dev/unreleased/admin-tool.md b/site/content/in-dev/unreleased/admin-tool.md
index b7ea65eb99..5a129503eb 100644
--- a/site/content/in-dev/unreleased/admin-tool.md
+++ b/site/content/in-dev/unreleased/admin-tool.md
@@ -33,7 +33,7 @@ The default build includes drivers for the PostgreSQL and NoSQL (MongoDB) backen
## Usage
-Please make sure the admin tool and Polaris server are with the same version before using it.
+Please make sure the admin tool and Polaris server are at the same version before using it.
To run the standalone JAR, use the following command:
If you downloaded the [binary distribution]({{% ref "getting-started/binary-distribution" %}}), you
@@ -227,7 +227,7 @@ NoSQL maintenance is run using the `nosql maintenance-run` command.
Maintenance covers the deletion of stale database entries.
{{< alert note >}}
-It is recommended to run the `nosql maintenance-run` command regulary, for example, once per day.
+It is recommended to run the `nosql maintenance-run` command regularly, for example, once per day.
{{< /alert >}}
The output shows a bunch of configuration options, most of which are automatically determined by the tool.
diff --git a/site/content/in-dev/unreleased/configuration/config-sections/flags-polaris_features.md b/site/content/in-dev/unreleased/configuration/config-sections/flags-polaris_features.md
index 34ad721214..92bfcdf4ef 100644
--- a/site/content/in-dev/unreleased/configuration/config-sections/flags-polaris_features.md
+++ b/site/content/in-dev/unreleased/configuration/config-sections/flags-polaris_features.md
@@ -47,7 +47,7 @@ If set to true (the default), Polaris honors a `location` (and the `write.data.p
##### `polaris.features."ALLOW_DROPPING_NON_EMPTY_PASSTHROUGH_FACADE_CATALOG"`
-If enabled, allow dropping a passthrough-facade catalog even if it contains namespaces or tables. passthrough-facade catalogs may contain leftover entities when syncing with source catalog.In the short term these entities will be ignored, in the long term there will be method/background job to clean them up.
+If enabled, allow dropping a passthrough-facade catalog even if it contains namespaces or tables. passthrough-facade catalogs may contain leftover entities when syncing with source catalog. In the short term these entities will be ignored, in the long term there will be method/background job to clean them up.
- **Type:** `Boolean`
- **Default:** `false`
@@ -142,7 +142,7 @@ If set to true (default), Polaris will permit S3 storage configurations to have
##### `polaris.features."ALLOW_SETTING_SUB_CATALOG_RBAC_FOR_FEDERATED_CATALOGS"`
-If set to true (default), Polaris will allow setting or changing catalog property polaris.config.enable-sub-catalog-rbac-for-federated-catalogs.If set to false, Polaris will disallow setting or changing the above catalog property
+If set to true (default), Polaris will allow setting or changing catalog property polaris.config.enable-sub-catalog-rbac-for-federated-catalogs. If set to false, Polaris will disallow setting or changing the above catalog property
- **Type:** `Boolean`
- **Default:** `true`
@@ -216,7 +216,7 @@ Initial delay in milliseconds before first retry for Azure API requests. Delay d
##### `polaris.features."AZURE_RETRY_JITTER_FACTOR"`
-Jitter factor (0.0 to 1.0) applied to retry delays for Azure API requests. The jitter is applied as a random percentage of the computed exponential backoff delay. For example, 0.5 means up to 50%% random jitter will be added to each retry delay. Helps prevent thundering herd when multiple requests fail simultaneously.
+Jitter factor (0.0 to 1.0) applied to retry delays for Azure API requests. The jitter is applied as a random percentage of the computed exponential backoff delay. For example, 0.5 means up to 50% random jitter will be added to each retry delay. Helps prevent thundering herd when multiple requests fail simultaneously.
- **Type:** `Double`
- **Default:** `0.5`
@@ -533,7 +533,7 @@ How long to store storage credentials in the local cache. This should be less th
##### `polaris.features."STORAGE_CREDENTIAL_DURATION_SECONDS"`
-The duration of time that vended storage credentials are valid for. Support for longer (or shorter) durations is dependent on the storage provider. GCS current does not respect this value.
+The duration of time that vended storage credentials are valid for. Support for longer (or shorter) durations is dependent on the storage provider. GCS currently does not respect this value.
- **Type:** `Integer`
- **Default:** `3600`
diff --git a/site/content/in-dev/unreleased/configuration/config-sections/smallrye-polaris_storage.md b/site/content/in-dev/unreleased/configuration/config-sections/smallrye-polaris_storage.md
index f7af9089a8..45d6b79278 100644
--- a/site/content/in-dev/unreleased/configuration/config-sections/smallrye-polaris_storage.md
+++ b/site/content/in-dev/unreleased/configuration/config-sections/smallrye-polaris_storage.md
@@ -41,5 +41,5 @@ Applies to the STS client pool and to Iceberg S3 clients created for table opera
| `polaris.storage.connect-timeout` | | `duration` | Override the default TCP connect timeout. |
| `polaris.storage.connection-acquisition-timeout` | | `duration` | Override default connection acquisition timeout. This is the time a request will wait for a connection from the pool. |
| `polaris.storage.connection-max-idle-time` | | `duration` | Override default max idle time of a pooled connection. |
-| `polaris.storage.connection-time-to-live` | | `duration` | Override default time-time of a pooled connection. |
+| `polaris.storage.connection-time-to-live` | | `duration` | Override default time-to-live of a pooled connection. |
| `polaris.storage.expect-continue-enabled` | | `boolean` | Override default behavior whether to expect an HTTP/100-Continue. |
diff --git a/site/content/in-dev/unreleased/downstream-build.md b/site/content/in-dev/unreleased/downstream-build.md
index e1b870c6df..16b414848c 100644
--- a/site/content/in-dev/unreleased/downstream-build.md
+++ b/site/content/in-dev/unreleased/downstream-build.md
@@ -22,7 +22,7 @@ type: docs
weight: 1005
---
-This page highlights a few keys points for building custom servers based on Apache Polaris.
+This page highlights a few key points for building custom servers based on Apache Polaris.
Polaris produces several jars. These jars may be used to build custom catalog server
according to the terms of the license included in Polaris distributions.
diff --git a/site/content/in-dev/unreleased/entities.md b/site/content/in-dev/unreleased/entities.md
index fe9cafe3b9..38fca62d03 100644
--- a/site/content/in-dev/unreleased/entities.md
+++ b/site/content/in-dev/unreleased/entities.md
@@ -111,7 +111,7 @@ Each catalog role may have multiple [privileges](#privilege) granted to it, and
## Policy
-Polaris policy is a set of rules governing actions on specified resources under predefined conditions. Polaris support policy for Iceberg table compaction, snapshot expiry, row-level access control, and custom policy definitions.
+Polaris policy is a set of rules governing actions on specified resources under predefined conditions. Polaris supports policies for Iceberg table compaction, snapshot expiry, row-level access control, and custom policy definitions.
Policy names may only contain letters (`A–Z`, `a–z`), digits (`0–9`), hyphens (`-`), and underscores (`_`). Names that do not match this pattern are rejected with HTTP 400.
diff --git a/site/content/in-dev/unreleased/evolution.md b/site/content/in-dev/unreleased/evolution.md
index 0462d37339..467770d42c 100644
--- a/site/content/in-dev/unreleased/evolution.md
+++ b/site/content/in-dev/unreleased/evolution.md
@@ -77,7 +77,7 @@ downstream projects according to the terms of the license included into Polaris
The minimal version of the JRE required by Polaris code (compilation target) may be updated in
any release. Different Polaris jars may have different minimal JRE version requirements.
-Changes in Java class should be expected at any time regardless of the module name or
+Changes in Java classes should be expected at any time regardless of the module name or
whether the class / method is `public` or not.
This approach is not meant to discourage the use of Polaris code in downstream projects, but
diff --git a/site/content/in-dev/unreleased/generic-table.md b/site/content/in-dev/unreleased/generic-table.md
index 9ac666b5e9..62881c2e03 100644
--- a/site/content/in-dev/unreleased/generic-table.md
+++ b/site/content/in-dev/unreleased/generic-table.md
@@ -55,8 +55,8 @@ shows the comparison between the two APIs:
| Operations | **Iceberg Table API** | **Generic Table API** |
|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
| Create Table | Create an Iceberg table | Create a generic table |
-| Load Table | Load an Iceberg table. If the table to load is a generic table, you need to call the Generic Table loadTable API, otherwise a TableNotFoundException will be thrown | Load a generic table. Similarly, try to load an Iceberg table through Generic Table API will thrown a TableNotFoundException. |
-| Drop Table | Drop an Iceberg table. Similar as load table, if the table to drop is a Generic table, a tableNotFoundException will be thrown. | Drop a generic table. Drop an Iceberg table through Generic table endpoint will thrown a TableNotFound Exception |
+| Load Table | Load an Iceberg table. If the table to load is a generic table, you need to call the Generic Table loadTable API, otherwise a TableNotFoundException will be thrown | Load a generic table. Similarly, trying to load an Iceberg table through the Generic Table API will throw a TableNotFoundException. |
+| Drop Table | Drop an Iceberg table. Similar as load table, if the table to drop is a Generic table, a TableNotFoundException will be thrown. | Drop a generic table. Dropping an Iceberg table through the Generic Table endpoint will throw a TableNotFoundException. |
| List Table | List all Iceberg tables | List all generic tables |
Note that generic table shares the same namespace with Iceberg tables, the table name has to be unique under the same namespace.
@@ -149,9 +149,9 @@ Example Response:
### Drop a Generic Table
The drop generic table REST endpoint is `DELETE /polaris/v1/{prefix}/namespaces/{namespace}/generic-tables/{generic-table}`
-The following curl call drops the table `delat_table`:
+The following curl call drops the table `delta_table`:
```shell
-curl -X DELETE http://localhost:8181/api/catalog/polaris/v1/delta_catalog/namespaces/delta_ns/generic-tables/{generic-table}
+curl -X DELETE http://localhost:8181/api/catalog/polaris/v1/delta_catalog/namespaces/delta_ns/generic-tables/delta_table
```
### API Reference
diff --git a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/catalog-azure.md b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/catalog-azure.md
index f2e377cdf8..3b3694fbf6 100644
--- a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/catalog-azure.md
+++ b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/catalog-azure.md
@@ -23,7 +23,7 @@ type: docs
weight: 300
---
-For the `polaris catalogs create` [command]({{% ref "../../command-line-interface#create" %}}) there are few `azure` only options
+For the `polaris catalogs create` [command]({{% ref "../../command-line-interface#create" %}}) there are a few `azure`-only options
```text
--storage-type azure
diff --git a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/catalog-gcs.md b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/catalog-gcs.md
index 6b4ef3aec8..510812b633 100644
--- a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/catalog-gcs.md
+++ b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/catalog-gcs.md
@@ -23,7 +23,7 @@ type: docs
weight: 200
---
-For the `polaris catalogs create` [command]({{% ref "../../command-line-interface#create" %}}) there are few `gcs` only options
+For the `polaris catalogs create` [command]({{% ref "../../command-line-interface#create" %}}) there are a few `gcs`-only options
```text
--storage-type gcs
diff --git a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-aws.md b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-aws.md
index 2177e1c269..5f8b995aa1 100644
--- a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-aws.md
+++ b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-aws.md
@@ -23,7 +23,7 @@ type: docs
weight: 100
---
-When creating a catalog based on AWS S3 storage only the `role-arn` is a required parameter. However, usually
+When creating a catalog based on AWS S3 storage, only the `role-arn` is a required parameter. However, usually
one also provides the `region` and
[external-id](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html).
diff --git a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-minio.md b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-minio.md
index cec21b5633..9744dde5c8 100644
--- a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-minio.md
+++ b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-minio.md
@@ -56,7 +56,7 @@ polaris \
In more complex deployments it may be necessary to configure different endpoints for S3 requests
and for STS (AssumeRole) requests. This can be achieved via the `--sts-endpoint` CLI option.
-Additionally, the `--endpoint-internal` CLI option cane be used to set the S3 endpoint for use by
+Additionally, the `--endpoint-internal` CLI option can be used to set the S3 endpoint for use by
the Polaris Server itself, if it needs to be different from the endpoint used by clients / engines.
A usable MinIO example for `docker-compose` is available in the Polaris source code under the
diff --git a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-ozone.md b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-ozone.md
index 096cbe47cd..40accf9a17 100644
--- a/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-ozone.md
+++ b/site/content/in-dev/unreleased/getting-started/creating-a-catalog/s3/catalog-ozone.md
@@ -23,7 +23,7 @@ type: docs
weight: 150
---
-When creating a catalog based on [Apache Ozone](https://ozone.apache.org/) storage it is important to
+When creating a catalog based on [Apache Ozone](https://ozone.apache.org/) storage, it is important to
configure the `endpoint` property to point to your own storage cluster. If the `endpoint` property is
not set, Polaris will attempt to contact AWS storage services (which is certain to fail in this case).
@@ -62,7 +62,7 @@ polaris \
In more complex deployments it may be necessary to configure different endpoints for S3 requests
and for STS (AssumeRole) requests. This can be achieved via the `--sts-endpoint` CLI option.
-Additionally, the `--endpoint-internal` CLI option cane be used to set the S3 endpoint for use by
+Additionally, the `--endpoint-internal` CLI option can be used to set the S3 endpoint for use by
the Polaris Server itself, if it needs to be different from the endpoint used by clients / engines.
A usable Apache Ozone example for `docker-compose` is available in the Polaris source code under the
diff --git a/site/content/in-dev/unreleased/getting-started/deploying-polaris/_index.md b/site/content/in-dev/unreleased/getting-started/deploying-polaris/_index.md
index e975f69274..d36525ad36 100644
--- a/site/content/in-dev/unreleased/getting-started/deploying-polaris/_index.md
+++ b/site/content/in-dev/unreleased/getting-started/deploying-polaris/_index.md
@@ -25,5 +25,5 @@ weight: 200
Here you can find the guides of how to deploy Polaris locally, as well as with all supported Cloud Providers: Amazon Web Services (AWS), Azure, and Google Cloud Platform (GCP).
-Locally, Polaris can be deployed using both docker and local build.
-On the cloud, the following tutorials will deploy Polaris using docker environment.
+Locally, Polaris can be deployed using both Docker and local build.
+On the cloud, the following tutorials will deploy Polaris using a Docker environment.
diff --git a/site/content/in-dev/unreleased/getting-started/deploying-polaris/cloud-deploy/deploy-aws.md b/site/content/in-dev/unreleased/getting-started/deploying-polaris/cloud-deploy/deploy-aws.md
index 06ce5e072a..0f03a8cc0a 100644
--- a/site/content/in-dev/unreleased/getting-started/deploying-polaris/cloud-deploy/deploy-aws.md
+++ b/site/content/in-dev/unreleased/getting-started/deploying-polaris/cloud-deploy/deploy-aws.md
@@ -27,7 +27,7 @@ Build and launch Polaris using the AWS Startup Script at the location provided i
Additionally, Polaris will be bootstrapped to use this database and Docker containers will be spun up for Spark SQL and Trino.
The requirements to run the script below are:
-* There must be at least two subnets created in the VPC and region in which your EC2 instance reside. The span of subnets MUST include at least 2 availability zones (AZs) within the same region.
+* There must be at least two subnets created in the VPC and region in which your EC2 instance resides. The span of subnets MUST include at least 2 availability zones (AZs) within the same region.
* Your EC2 instance must be enabled with [IMDSv1 or IMDSv2 with 2+ hop limit](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/configuring-IMDS-new-instances.html#configure-IMDS-new-instances-instance-settings).
* The AWS identity that you will use to run this script must have the following AWS permissions:
* "ec2:DescribeInstances"
diff --git a/site/content/in-dev/unreleased/getting-started/using-polaris/_index.md b/site/content/in-dev/unreleased/getting-started/using-polaris/_index.md
index 84509a80f8..2e12971fce 100644
--- a/site/content/in-dev/unreleased/getting-started/using-polaris/_index.md
+++ b/site/content/in-dev/unreleased/getting-started/using-polaris/_index.md
@@ -161,7 +161,7 @@ bin/spark-sql \
--conf spark.sql.catalog.polaris.client.region=us-west-2
```
-Similar to the CLI commands above, this configures Spark to use the Polaris running at `localhost:8181`. If your Polaris server is running elsewhere, but sure to update the configuration appropriately.
+Similar to the CLI commands above, this configures Spark to use the Polaris running at `localhost:8181`. If your Polaris server is running elsewhere, be sure to update the configuration appropriately.
Finally, note that we include the `iceberg-aws-bundle` package here. If your table is using a different filesystem, be sure to include the appropriate dependency.
diff --git a/site/content/in-dev/unreleased/helm-chart/dev.md b/site/content/in-dev/unreleased/helm-chart/dev.md
index 2f1f669d07..023e4c146f 100644
--- a/site/content/in-dev/unreleased/helm-chart/dev.md
+++ b/site/content/in-dev/unreleased/helm-chart/dev.md
@@ -248,7 +248,7 @@ helm uninstall --namespace polaris polaris
kubectl delete namespace polaris --wait=true --ignore-not-found
```
-The stop Minikube if desired:
+Then stop Minikube if desired:
```bash
minikube stop
diff --git a/site/content/in-dev/unreleased/helm-chart/production.md b/site/content/in-dev/unreleased/helm-chart/production.md
index 8d0e052e56..592ddcd84d 100644
--- a/site/content/in-dev/unreleased/helm-chart/production.md
+++ b/site/content/in-dev/unreleased/helm-chart/production.md
@@ -23,7 +23,7 @@ type: docs
weight: 200
---
-This guide provides instructions for configuring the Apache Polaris Helm chart for a production environment. For full list of chart values, see the [Chart Reference]({{% relref "reference" %}}) page.
+This guide provides instructions for configuring the Apache Polaris Helm chart for a production environment. For a full list of chart values, see the [Chart Reference]({{% relref "reference" %}}) page.
## Prerequisites
diff --git a/site/content/in-dev/unreleased/metastores/relational-jdbc.md b/site/content/in-dev/unreleased/metastores/relational-jdbc.md
index bae952e875..04eaeaf226 100644
--- a/site/content/in-dev/unreleased/metastores/relational-jdbc.md
+++ b/site/content/in-dev/unreleased/metastores/relational-jdbc.md
@@ -68,7 +68,7 @@ quarkus.rds.credentials-provider.aws.port=6160
This is the basic configuration. For more details, please refer to the [Quarkus plugin documentation](https://docs.quarkiverse.io/quarkus-amazon-services/dev/amazon-rds.html#_configuration_reference).
-The Relational JDBC metastore currently relies on a Quarkus-managed datasource and supports only PostgresSQL and H2 databases. At this time, official documentation is provided exclusively for usage with PostgreSQL.
+The Relational JDBC metastore currently relies on a Quarkus-managed datasource and supports only PostgreSQL and H2 databases. At this time, official documentation is provided exclusively for usage with PostgreSQL.
Please refer to the documentation here:
[Configure data sources in Quarkus](https://quarkus.io/guides/datasource).
diff --git a/site/content/in-dev/unreleased/polaris-spark-client.md b/site/content/in-dev/unreleased/polaris-spark-client.md
index 6c3cab7545..b7b1742f74 100644
--- a/site/content/in-dev/unreleased/polaris-spark-client.md
+++ b/site/content/in-dev/unreleased/polaris-spark-client.md
@@ -43,7 +43,7 @@ git clone https://github.com/apache/polaris.git ~/polaris
```
## Start Spark against a Deployed Polaris Service
-Before starting, ensure that the deployed Polaris service supports Generic Tables, and that Spark 3.5(version 3.5.3 or later is installed).
+Before starting, ensure that the deployed Polaris service supports Generic Tables, and that Spark 3.5 (version 3.5.3 or later) is installed.
Spark 3.5.6 is recommended, and you can follow the instructions below to get a Spark 3.5.6 distribution.
```shell
cd ~
@@ -82,7 +82,7 @@ Polaris service, the uri would be `http://localhost:8181/api/catalog`.
For `client-id` and `client-secret` values, you can refer to [Using Polaris]({{% ref "getting-started/using-polaris" %}})
for more details.
-You can also start the connection by programmatically initialize a SparkSession, following is an example with PySpark:
+You can also start the connection by programmatically initializing a SparkSession, following is an example with PySpark:
```python
from pyspark.sql import SparkSession
@@ -129,6 +129,6 @@ The following describes the current limitations of the Polaris Spark client:
### Delta Table Limitations
1. Create table as select (CTAS) is not supported for Delta tables. As a result, the `saveAsTable` method of `Dataframe`
is also not supported, since it relies on the CTAS support.
-2. Create a Delta table without explicit location is not supported.
-3. Rename a Delta table is not supported.
+2. Creating a Delta table without an explicit location is not supported.
+3. Renaming a Delta table is not supported.
4. ALTER TABLE ... SET LOCATION is not supported for DELTA table.
\ No newline at end of file
diff --git a/site/content/in-dev/unreleased/realm.md b/site/content/in-dev/unreleased/realm.md
index 57e007b25b..710bd3c5ab 100644
--- a/site/content/in-dev/unreleased/realm.md
+++ b/site/content/in-dev/unreleased/realm.md
@@ -26,15 +26,15 @@ This page explains what a realm is and what it is used for in Polaris.
### What is it?
-A realm in Polaris serves as logical partitioning mechanism within the catalog system. This isolation allows for multitenancy, enabling different teams, environments or organizations to operate independently within the same Polaris deployment.
+A realm in Polaris serves as a logical partitioning mechanism within the catalog system. This isolation allows for multitenancy, enabling different teams, environments or organizations to operate independently within the same Polaris deployment.
### Key Characteristics
**Isolation:** Each realm encapsulates its own set of resources, ensuring that operations, policies in one realm do not affect others.
-**Authentication Context:** When configuring Polaris, principals credentials are associated with a specific realm. This allows for the separation of security concerns across different realms.
+**Authentication Context:** When configuring Polaris, principals' credentials are associated with a specific realm. This allows for the separation of security concerns across different realms.
-**Configuration Scope:** Realm identifiers are used in various configurations, such as connection strings feature configurations, etc.
+**Configuration Scope:** Realm identifiers are used in various configurations, such as connection strings, feature configurations, etc.
An example of this is:
diff --git a/site/content/in-dev/unreleased/telemetry.md b/site/content/in-dev/unreleased/telemetry.md
index 3023e2ddbd..c91febb99c 100644
--- a/site/content/in-dev/unreleased/telemetry.md
+++ b/site/content/in-dev/unreleased/telemetry.md
@@ -69,7 +69,7 @@ HTTP request metrics will be recorded. This threshold can be changed by setting
### HTTP Request Histogram Buckets
By default, the HTTP server request duration timer exports only the count, sum, and max series.
-These support average and worse-case latency but cannot be used to compute aggregable percentiles
+These support average and worst-case latency but cannot be used to compute aggregable percentiles
(e.g. p95, p99) across instances.
To publish histogram buckets for HTTP server request duration, configure the Service Level