[DATALAD RUNCMD] Do interactive fixing of some ambigous typos

=== Do not change lines below ===
{
 "chain": [],
 "cmd": "codespell -w -i 3 -C 2",
 "exit": 0,
 "extra_inputs": [],
 "inputs": [],
 "outputs": [],
 "pwd": "."
}
^^^ Do not change lines above ^^^

docs/howto/troubleshoot/logs.md

@@ -27,7 +27,7 @@ logs are kept for 30 days, and are searchable.
    as time sliders. However, for most of our logs, the 'log levels' (error, warning, etc)
    are not parsed correctly, and hence are useless.
 
-4. Google provies a [query library](https://cloud.google.com/logging/docs/view/query-library) set of [sample queries](https://cloudlogging.app.goo.gl/Ad7B8hjFHpj6X7rT8) that you can access via the Library tab in Logs Explorer.
+4. Google provides a [query library](https://cloud.google.com/logging/docs/view/query-library) set of [sample queries](https://cloudlogging.app.goo.gl/Ad7B8hjFHpj6X7rT8) that you can access via the Library tab in Logs Explorer.
 
 
 ### Common queries

docs/hub-deployment-guide/deploy-support/configure-support.md

@@ -115,7 +115,7 @@ Namecheap.com](https://ap.www.namecheap.com/Domains/DomainControlPanel/2i2c.clou
 2. `*.<cluster-name>.2i2c.cloud.`, for all other hubs, grafana and prometheus
    instances.
 
-Use an `A` record when we point to an external IP addresse (GCP, Azure), and a
+Use an `A` record when we point to an external IP address (GCP, Azure), and a
 `CNAME` record when we point to another domain (AWS).
 
 ```{note}

docs/hub-deployment-guide/new-cluster/aws.md

@@ -35,7 +35,7 @@ terraform to provision supporting infrastructure, such as storage buckets.
 (new-cluster:aws-setup-credentials)=
 ### Setup credentials
 
-Depending on wether this project is using AWS SSO or not, you can use the following
+Depending on whether this project is using AWS SSO or not, you can use the following
 links to figure out how to authenticate to this project from your terminal.
 
 - [For accounts setup with AWS SSO](cloud-access:aws-sso:terminal)

docs/topic/features.md

@@ -60,6 +60,6 @@ of a project. We set the environment variable `PERSISTENT_BUCKET` to the form
 `<s3 or gcs>://<bucket-name>/<user-name>` so users can put stuff in this.
 
 ```{warning}
-Objects put in `PERSISTENT_BUCKET` *must* be deleted by the users when no logner in use
+Objects put in `PERSISTENT_BUCKET` *must* be deleted by the users when no longer in use
 to prevent cost overruns! This *can not* be managed by 2i2c.
 ```

docs/topic/monitoring-alerting/grafana.md

@@ -54,7 +54,7 @@ Navigating at <https://grafana.pilot.2i2c.cloud/dashboards>, shows a `JupyterHub
   - user CPU usage distribution
   - user memory usage distribution
   - server start times
-  - hub respone latency
+  - hub response latency
 
   There is also a Panel section about `Anomalous user pods` where pods with high CPU usage or high memory usage are tracked.
 

terraform/gcp/variables.tf

@@ -252,7 +252,7 @@ variable "user_buckets" {
   'delete_after' specifies the number of days after which any content
   in the bucket will be deleted. Set to null to not delete data.
 
-  'extra_admin_members' describes extra identies (user groups, user accounts,
+  'extra_admin_members' describes extra identities (user groups, user accounts,
   service accounts, etc) that will have *full* access to this bucket. This
   is primarily useful for moving data into and out of buckets from outside
   the cloud. See https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/storage_bucket_iam#member/members

tests/test_billing.py

@@ -198,7 +198,7 @@ def test_shared_cluster_internal(shared_cluster, start_date, end_date):
     ), "Utilization for 2i2c_costs should be 0.75"
     assert (
         "staging" not in rows
-    ), "Utilization for 2i2c_costs should replace interal namespaces"
+    ), "Utilization for 2i2c_costs should replace internal namespaces"
 
 
 def test_shared_cluster_aggregates_internal(shared_cluster, start_date, end_date):