chore(docs): rewrite internal redirects (#518)

- manually fixed link in /docs/plugin/framework/migrating/attributes-blocks/validators-predefined.mdx

website/docs/plugin/framework/migrating/attributes-blocks/blocks-computed.mdx

@@ -71,7 +71,7 @@ map[string]tfsdk.Attribute{
 ## Migration Notes
 
 - When using protocol version 5 specify `ElemType` as `types.ObjectType` when migrating blocks that are computed from SDKv2 to Framework.
-- When using protocol version 6, use [nested attributes](https://www.terraform.io/plugin/framework/schemas#attributes-1) when migrating blocks that are computed from SDKv2 to Framework.
+- When using protocol version 6, use [nested attributes](/plugin/framework/schemas#attributes-1) when migrating blocks that are computed from SDKv2 to Framework.
 
 ## Example
 

website/docs/plugin/framework/migrating/attributes-blocks/types.mdx

@@ -113,7 +113,7 @@ Remember the following differences between SDKv2 and the Framework when completi
 a primitive type such as an integer or string, and you use the `Attributes` field for `NestedAttributes`. Refer to
 [Providers](/plugin/framework/migrating/providers#example-1) for an example of using a single
 nested attribute. Nested attributes are also described in more detail on the
-[Schemas](https://www.terraform.io/plugin/framework/schemas#attributes-1) page in the Framework documentation.
+[Schemas](/plugin/framework/schemas#attributes-1) page in the Framework documentation.
 
 ## Example
 

website/docs/plugin/framework/migrating/attributes-blocks/validators-predefined.mdx

@@ -12,7 +12,7 @@ description: >-
 Attribute validators ensure that attributes do or do not contain specific values. You can use predefined validators for
 many use cases, or implement custom validators. Refer to [Schemas - Validators](/plugin/framework/schemas#validators) in
 the Framework documentation for details. Refer to the
-[Attributes - Custom Validators](/plugin/framework/migrating/validators-custom) page in this guide to learn how to
+[Attributes - Custom Validators](/plugin/framework/migrating/attributes-blocks/validators-custom) page in this guide to learn how to
 implement custom validators.
 
 This page explains how to migrate a predefined validator from SDKv2 to the Framework.

website/docs/plugin/framework/migrating/resources/import.mdx

@@ -9,7 +9,7 @@ description: >-
 
 -> **Note:** The Plugin Framework is in beta.
 
-Practitioners can use the [`terraform import` command](https://www.terraform.io/cli/commands/import) to let Terraform
+Practitioners can use the [`terraform import` command](/cli/commands/import) to let Terraform
 begin managing existing infrastructure by importing an existing resource into their Terraform project's state. A
 resource's importer function implements the logic to add a resource to Terraform's state. Refer to
 [Resources - Import](/plugin/framework/resources/import) in the Framework documentation for details.

website/docs/plugin/framework/provider-servers.mdx

@@ -86,4 +86,4 @@ Refer to the [acceptance testing](/plugin/framework/acctests) page for implement
 
 ### Debugging
 
-Refer to the [debugging](/plugin/framework/) page for implementation details.
+Refer to the [debugging](/plugin/framework) page for implementation details.