docs: Cleaning up changelog for full provider lock files

Author: yhakbar

docs/src/data/changelog/v1.0.4/full-provider-lock-files.mdx

@@ -26,5 +26,5 @@ provider "registry.opentofu.org/hashicorp/null" {
 The hashes come from the registry's per-platform download response. When the registry does not supply them (for example, a third-party registry that has not adopted the field), Terragrunt falls back to its previous behavior of writing an `h1:` hash for the current platform plus `zh:` hashes for every platform listed in the shasums document.
 
 <Aside type="tip" title="Thanks to the OpenTofu team">
-  This feature builds on work done by the OpenTofu team to expose per-platform hashes directly from the OpenTofu provider registry. Starting with [OpenTofu 1.12](https://opentofu.org/), `tofu init` populates `.terraform.lock.hcl` with hashes for every supported platform out of the box, with no Terragrunt or `tofu providers lock` invocation required. Users on older OpenTofu versions still get the same lock files when running through Terragrunt's provider cache server, but upgrading to 1.12 is the easiest way to get the same behavior everywhere.
+  This feature builds on work done by the OpenTofu team to expose per-platform hashes directly from the OpenTofu provider registry. Starting with [OpenTofu 1.12](https://opentofu.org/), `tofu init` populates `.terraform.lock.hcl` with hashes for every supported platform out of the box, with no `tofu providers lock` invocation required. Users on older OpenTofu versions still get the same lock files when running through Terragrunt's [provider cache server](https://docs.terragrunt.com/features/caching/provider-cache-server/), but upgrading to 1.12 is the easiest way to get the same behavior everywhere (including while using the [automatic provider cache dir](https://docs.terragrunt.com/features/caching/auto-provider-cache-dir/).
 </Aside>