precommit

Author: marcinwyszynski

CLAUDE.md

@@ -4,13 +4,13 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Documentation Build System
 
-This is the Spacelift user documentation repository using MkDocs with Material theme. The live documentation is at https://docs.spacelift.io/.
+This is the Spacelift user documentation repository using MkDocs with Material theme. The live documentation is at <https://docs.spacelift.io/>.
 
 ## Common Commands
 
 ### Development
 
-- `make run` - Run the documentation site locally via Docker Compose (http://localhost:8000)
+- `make run` - Run the documentation site locally via Docker Compose (<http://localhost:8000>)
 - `mkdocs serve` - Run locally with MkDocs directly
 - `mkdocs serve -a '0.0.0.0:8000'` - Run with external access
 

docs/installing-spacelift/reference-architecture/README.md

@@ -59,7 +59,7 @@ Once Spacelift has been deployed to your environment, follow our [first setup gu
 
 ## Upgrading
 
-Spacelift supports zero downtime upgrades unless otherwise mentioned in the [changelog](../changelog.md). The process for upgrading to a new release is as follows:
+Spacelift supports zero downtime upgrades. The process for upgrading to a new release is as follows:
 
 1. Make any required infrastructure adjustments.
 2. Push the latest container images to your registry.

docs/integrations/cloud-providers/oidc/gcp-oidc.md

@@ -105,7 +105,7 @@ For more information about configuring the OpenTofu/Terraform provider, please s
 
 ## Configuring the Pulumi GCP Provider
 
-To configure the Pulumi [GCP provider](https://www.pulumi.com/registry/packages/gcp/api-docs/provider/){: rel="nofollow"} follow the same steps as for the [OpenTofu/Terraform provider](#configuring-the-terraform-provider).
+To configure the Pulumi [GCP provider](https://www.pulumi.com/registry/packages/gcp/api-docs/provider/){: rel="nofollow"} follow the same steps as for the [OpenTofu/Terraform provider](#configuring-the-opentofuterraform-provider).
 
 ## Troubleshooting
 

docs/vendors/terraform/external-state-access.md

@@ -1,7 +1,7 @@
 # External state access
 
 !!! info
-    While this feature allows sharing outputs between stacks, we recommend using Spacelift's native [stack dependencies](../../concepts/configuration/stack-dependencies.md) instead when possible. Available for all supported IaC vendors, Stack dependencies provide a more integrated workflow with granular access, proper dependency tracking and access control, and they don't require external state access to be enabled.
+    While this feature allows sharing outputs between stacks, we recommend using Spacelift's native [stack dependencies](../../concepts/stack/stack-dependencies.md) instead when possible. Available for all supported IaC vendors, Stack dependencies provide a more integrated workflow with granular access, proper dependency tracking and access control, and they don't require external state access to be enabled.
 
 External state access allows you to read the state of the stack from outside authorized [runs](../../concepts/run/README.md) and [tasks](../../concepts/run/task.md). In particular, this enables sharing the outputs between stacks using the OpenTofu/Terraform mechanism of [remote state](https://opentofu.org/docs/language/state/remote-state-data/){: rel="nofollow"} or even accessing the state offline for analytical or compliance purposes.