DEV-604 - Refer to Account Factory as Account Factory (#2177)

* DEV-317 - add a note about bootstrap including mise.toml directly in docs

* DEV-604 - Update LZ references to AF

Author: ZachGoldberg

docs/2.0/docs/pipelines/concepts/cloud-auth.md

@@ -50,11 +50,11 @@ Pipelines can handle two main types of infrastructure-change events:
 1. Adding/changing/deleting Terragrunt files
 2. Creating new AWS accounts
 
-For the first type of infrastructure change (add/change/delete Terragrunt files) Pipelines authenticates to the specific AWS account where the affected resources live. For the second type of change (creating new AWS accounts), Pipelines uses the Gruntwork Landing Zone Management Account.
+For the first type of infrastructure change (add/change/delete Terragrunt files) Pipelines authenticates to the specific AWS account where the affected resources live. For the second type of change (creating new AWS accounts), Pipelines uses the Management Account.
 
-#### Gruntwork Landing Zone Management Account
+#### Management Account
 
-Gruntwork Landing Zone is built on top of AWS Control Tower, and AWS Control Tower requires that you create new AWS accounts using the [Control Tower Management AWS Account](https://docs.aws.amazon.com/controltower/latest/userguide/how-control-tower-works.html#what-is-mgmt).
+Gruntwork's Account Factory is built on top of AWS Control Tower, and AWS Control Tower requires that you create new AWS accounts using the [Control Tower Management AWS Account](https://docs.aws.amazon.com/controltower/latest/userguide/how-control-tower-works.html#what-is-mgmt).
 
 When new AWS account requests are approved and the AWS account is created, Pipelines will create a Pull Request that contains an account baseline. Since Pipelines does not yet have access to the AWS account, the baseline will be applied by authenticating to the Management Account.
 

docs/2.0/docs/pipelines/installation/prerequisites/awslandingzone.md

@@ -7,15 +7,15 @@ The Landing Zone component is focused on creating an initial best-practice AWS m
 
 ## Extending AWS Control Tower
 
-Gruntwork Landing Zone builds on AWS Control Tower to add important new functionality.
+Gruntwork's suggested Landing Zone / Account Factory builds on AWS Control Tower to add important new functionality.
 
 ### What is AWS Control Tower?
 
 AWS Control Tower helps you set up and govern AWS accounts, and gives you a centralized way to manage compliance and configuration across your AWS accounts. But Control Tower is fundamentally a Platform-as-a-Service (PaaS) paradigm where you use "ClickOps" to create and configure AWS accounts. That stands in contrast to the vision behind IaC tools like Terraform, which are built on the philosophy that all Cloud resources are described in code. It can also be challenging to customize Control Tower and maintain it over time.
 
 ### Additional functionality
 
-Gruntwork Landing Zone directly addresses these limitations by extending Control Tower with the following functionality:
+Gruntwork's Account Factory directly addresses these limitations by extending Control Tower with the following functionality:
 
 1. Configure and customize new AWS accounts using Terraform/OpenTofu
 1. Via the Gruntwork Account Factory:
@@ -27,7 +27,7 @@ Gruntwork Landing Zone directly addresses these limitations by extending Control
 
 ## Prerequisites
 
-The first step to using Gruntwork Landing Zone is to use AWS Control Tower to create a new multi-account setup, which requires that you meet the following prerequisites:
+The first step to using Gruntwork Account Factory is to use AWS Control Tower to create a new multi-account setup, which requires that you meet the following prerequisites:
 1. A [new AWS Account](https://portal.aws.amazon.com/billing/signup) and a user with administrator permissions. (We recommend using an IAM user with admin permissions rather than the root user)
 
    :::info
@@ -242,7 +242,7 @@ Control Tower Creation will take around an hour to complete
 ## Post Setup Configuration
 
 Now that Control Tower is enabled in your root account, there are a few configuration changes that need to be made to
-prepare for Gruntwork Landing Zone.
+prepare for Gruntwork Account Factory.
 
 1. [Turn off the default VPC created for new accounts](https://docs.aws.amazon.com/controltower/latest/userguide/configure-without-vpc.html#create-without-vpc). Gruntwork VPCs will be created for each account using terraform.