Update placeholderplaceholderplaceholder occurrences to our doc site (#684)

internal/command/e2etest/automation_test.go

@@ -14,10 +14,6 @@ import (
 	"github.com/opentofu/opentofu/internal/plans"
 )
 
-// The tests in this file run through different scenarios recommended in our
-// "Running Terraform in Automation" guide:
-//     https://www.placeholderplaceholderplaceholder.io/guides/running-terraform-in-automation.html
-
 // TestPlanApplyInAutomation runs through the "main case" of init, plan, apply
 // using the specific command line options suggested in the guide.
 func TestPlanApplyInAutomation(t *testing.T) {

internal/command/import.go

@@ -345,7 +345,7 @@ func (c *ImportCommand) Synopsis() string {
 }
 
 const importCommandInvalidAddressReference = `For information on valid syntax, see:
-https://www.placeholderplaceholderplaceholder.io/docs/cli/state/resource-addressing.html`
+https://opentofu.org/docs/cli/state/resource-addressing/`
 
 const importCommandMissingResourceFmt = `[reset][bold][red]Error:[reset][bold] resource address %q does not exist in the configuration.[reset]
 

internal/command/init.go

@@ -868,7 +868,7 @@ func (c *InitCommand) getProviders(ctx context.Context, config *configs.Config,
 			if thirdPartySigned {
 				c.Ui.Info(fmt.Sprintf("\nProviders are signed by their developers.\n" +
 					"If you'd like to know more about provider signing, you can read about it here:\n" +
-					"https://www.placeholderplaceholderplaceholder.io/docs/cli/plugins/signing.html"))
+					"https://opentofu.org/docs/cli/plugins/signing/"))
 			}
 		},
 	}

internal/command/meta_backend_migrate.go

@@ -981,8 +981,6 @@ the error above and try again.
 
 const errTFCMigrateNotYetImplemented = `
 Migrating state from Terraform Cloud to another backend is not yet implemented.
-
-Please use the API to do this: https://www.placeholderplaceholderplaceholder.io/docs/cloud/api/state-versions.html
 `
 
 const errInteractiveInputDisabled = `
@@ -1005,8 +1003,6 @@ configuration (e.g. production, staging, development), Terraform Cloud workspace
 across all configurations used within an organization. A typical strategy to start with is
 <COMPONENT>-<ENVIRONMENT>-<REGION> (e.g. networking-prod-us-east, networking-staging-us-east).
 
-For more information on workspace naming, see https://www.placeholderplaceholderplaceholder.io/docs/cloud/workspaces/naming.html
-
 When migrating existing workspaces from the backend %[1]q to Terraform Cloud, would you like to
 rename your workspaces? Enter 1 or 2.