spelling fixes

Author: gingerwizard

docs/cloud/manage/hyperdx.md

@@ -26,4 +26,4 @@ HyperDX in ClickHouse Cloud is currently in private preview and must be enabled
 
 To get started with HyperDX in ClickHouse Cloud, we recommend our dedicated [getting started guide](/use-cases/observability/clickstack/deployment/hyperdx-clickhouse-cloud).
 
-For further details on Clickstack, see the [full documentation](/use-cases/observability/clickstack). 
+For further details on ClickStack, see the [full documentation](/use-cases/observability/clickstack). 

docs/use-cases/observability/clickstack/dashboards.md

@@ -149,7 +149,7 @@ The dashboard will be auto-saved. To set the dashboard name, select the title an
 
 </VerticalStepper>
 
-## Dashboards - editing visualizations
+## Dashboards - editing visualizations {#dashboards-editing-visualizations}
 
 To remove, edit, or duplicate a visualization, hover over it and use the corresponding action buttons.
 

docs/use-cases/observability/clickstack/deployment/hyperdx-clickhouse-cloud.md

@@ -31,11 +31,11 @@ This deployment pattern is ideal in the following scenarios:
 
 1. You already have observability data in ClickHouse Cloud and wish to visualize it using HyperDX.
 2. You operate a large observability deployment and need the dedicated performance and scalability of ClickStack with ClickHouse Cloud.
-3. You're already using ClickHouse Cloud for analytics and want to instrument your application using ClickStack’s instrumentation libraries — sending data to the same cluster. In this case, we recommend using [warehouses](/cloud/reference/warehouses) to isolate compute for observability workloads.
+3. You're already using ClickHouse Cloud for analytics and want to instrument your application using ClickStack instrumentation libraries — sending data to the same cluster. In this case, we recommend using [warehouses](/cloud/reference/warehouses) to isolate compute for observability workloads.
 
 ## Deployment steps {#deployment-steps}
 
-The following guide assumes you have already created a ClickHouse Cloud service. If you haven't created a service, follow the ["Create a ClicKhouse service"](/getting-started/quick-start/cloud#1-create-a-clickhouse-service) step from our Quick Start guide.
+The following guide assumes you have already created a ClickHouse Cloud service. If you haven't created a service, follow the ["Create a ClickHouse service"](/getting-started/quick-start/cloud#1-create-a-clickhouse-service) step from our Quick Start guide.
 
 <VerticalStepper headerLevel="h3">
 
@@ -56,7 +56,7 @@ Press the `Connect` button from the navigation menu. A modal will open offering
 This step ensures tables are created with an Open Telemetry (OTel) schema, which can in turn be used seamlessly to create a data source in HyperDX. This also provides an OLTP endpoint which can be used for loading [sample datasets](/use-cases/observability/clickstack/sample-datasets) and sending OTel events to ClickStack.
 
 :::note Use of standard Open Telemetry collector
-The following instructions use the standard distribution of the OTel collector, rather than the ClickStack distribution. The latter requires an OpAMP server for configutation. This is currently not supported in private preview. The configuration below replicates the version used by the ClickStack distribution of the collector, providing an OTLP endpoint to which events can be sent.
+The following instructions use the standard distribution of the OTel collector, rather than the ClickStack distribution. The latter requires an OpAMP server for configuration. This is currently not supported in private preview. The configuration below replicates the version used by the ClickStack distribution of the collector, providing an OTLP endpoint to which events can be sent.
 :::
 
 Create a `otel-file-collector.yaml` file with the following content:

docs/use-cases/observability/clickstack/example-datasets/remote-demo-data.md

@@ -40,7 +40,6 @@ import edit_connection from '@site/static/images/use-cases/observability/edit_co
 
 **The following guide assumes you have deployed ClickStack using the [instructions for the all-in-one image](/use-cases/observability/clickstack/getting-started), or [Local Mode Only](/use-cases/observability/clickstack/deployment/local-mode-only) and completed initial user creation. Alternatively, users can skip all local setup and simply connect to our ClickStack hosted demo [play-clickstack.clickhouse.com](https://play-clickstack.clickhouse.com) which uses this dataset.**
 
-
 This guide uses a sample dataset hosted on the public ClickHouse playground at [sql.clickhouse.com](https://sql.clickhpouse.com), which you can connect to from your local ClickStack deployment.
 
 :::warning Not supported with HyperDX in ClickHouse Cloud

docs/use-cases/observability/clickstack/example-datasets/sample-data.md

@@ -53,7 +53,6 @@ This step is not required if using HyperDX in ClickHouse Cloud, where ingestion
 
 Navigate to [`Team Settings`](http://localhost:8080/team) and copy the `Ingestion API Key` from the `API Keys` section. This API key ensures data ingestion through the OpenTelemetry collector is secure.
 
-
 <Image img={copy_api_key} alt="Copy API key" size="lg"/>
 
 ## Download sample data {#download-sample-data}
@@ -103,7 +102,7 @@ done
 
 This simulates OLTP log, trace, and metric sources sending data to the OTel collector. In production, these sources may be language clients or even other OTel collectors.
 
-Returning to the `Search` view, you should see that data has started to load (adjust the timeframe to the `Last 1 hour` if the data does not rendwer):
+Returning to the `Search` view, you should see that data has started to load (adjust the time frame to the `Last 1 hour` if the data does not render):
 
 <Image img={hyperdx_10} alt="HyperDX search" size="lg"/>