Pipelines-section-4 : Changes to Pipelines / Guides files

docs/2.0/docs/accountfactory/concepts/delegated-repositories.md

@@ -15,7 +15,7 @@ Using this pattern core platform teams have the ability to:
 * Enforce least-privilege access to IaC, restricting teams to have access only to IaC and deployment capability / role assumptions for resources that they are responsible for.
 
 ## Delegated Repository Creation
-Delegated repositories are optionally created by [Account Factory](/2.0/docs/accountfactory/concepts) during account creation.  A delegated account vend follows the following (automated) workflow:
+Delegated repositories are optionally created by [Account Factory](/2.0/docs/accountfactory/concepts) during account creation. A delegated account vend follows the following (automated) workflow:
 
 ```mermaid
 sequenceDiagram

docs/2.0/docs/accountfactory/installation/index.md

@@ -6,7 +6,7 @@ Account Factory is automatically added to [new Pipelines root repositories](/2.0
 
 Out of the box Account Factory has the following components:
 
-- 📋 An HTML form for generating workflow inputs:  `.github/workflows/account-factory-inputs.html`
+- 📋 An HTML form for generating workflow inputs: `.github/workflows/account-factory-inputs.html`
 
 - 🏭 A workflow for generating new requests: `.github/workflows/account-factory.yml`
 

docs/2.0/docs/accountfactory/tutorials/modify-account.md

@@ -1,5 +1,3 @@
-
-
 # Modifying an AWS Account
 
 Over time you will need to run various operations on your AWS accounts such as requesting new accounts, creating new accounts, renaming accounts, etc. With the Gruntwork Account Factory, some AWS account management operations should only be done using IaC, some can only be done using ClickOps, and some can be done using either.

docs/2.0/docs/accountfactory/tutorials/remove-account.md

@@ -1,5 +1,3 @@
-
-
 # Removing an AWS Account
 
 ## Prerequisites
@@ -15,7 +13,7 @@ We recommend following a two step procedure to close AWS Accounts managed by Dev
 1. [Cleanup Infrastructure Code](#1-cleanup-infrastructure-code) and modify OpenTofu/Terraform state for the Control Tower module.
 1. [Close Account with Clickops](#2-close-the-accounts-in-aws-organizations)
 
-We are recommending that accounts be closed with ClickOps instead of using Gruntwork Pipelines. Removing the account via pipelines by deleting the account request file can and often does work, however the underlying AWS Service Catalog that we use to interact with Control Tower and deprovision the account is not (https://github.com/hashicorp/terraform-provider-aws/issues/31705) and often returns spurious errors that can require multiple retries to complete successfully.  The procedure here is fundamentally about working around that unreliability.
+We are recommending that accounts be closed with ClickOps instead of using Gruntwork Pipelines. Removing the account via pipelines by deleting the account request file can and often does work, however the underlying AWS Service Catalog that we use to interact with Control Tower and deprovision the account is not (https://github.com/hashicorp/terraform-provider-aws/issues/31705) and often returns spurious errors that can require multiple retries to complete successfully. The procedure here is fundamentally about working around that unreliability.
 
 ### 1. Cleanup Infrastructure Code
 

docs/2.0/docs/pipelines/guides/installing-drift-detection.md

@@ -3,26 +3,26 @@
 import PersistentCheckbox from '/src/components/PersistentCheckbox';
 
 :::note
-Pipelines Drift Detection is only available to Devops Foundations Enterprise customers.
+Pipelines Drift Detection is exclusively available to DevOps Foundations Enterprise customers.
 :::
 
-If you're creating new pipelines repositories using the latest version of Pipelines, then Drift Detection will be installed automatically without any action on your part.
+For new pipelines repositories using the latest version of Pipelines, Drift Detection is installed automatically and requires no additional action.
 
-If you want to upgrade an older repository to add Drift Detection perform the following steps:
+To upgrade an existing repository and enable Drift Detection, follow these steps:
 
-### Step 1 - Ensure the GitHub App is Installed
+### Step 1 - Ensure the GitHub App is installed
 
-Ensure you are using the [GitHub App](/2.0/docs/pipelines/installation/viagithubapp) in this repository. Drift Detection requires permissions from the GitHub App and is not available via machine user tokens.
+Verify that the [GitHub App](/2.0/docs/pipelines/installation/viagithubapp) is installed and in use for this repository. Drift Detection relies on permissions granted by the GitHub App and is not compatible with machine user tokens.
 
 <PersistentCheckbox id="install-drift-1" label="GitHub App In Use" />
 
-### Step 2 - Setup the Workflow file
+### Step 2 - Set up the workflow file
 
-Create a new workflow file in your repository at `.github/workflows/pipelines-drift-detection.yml`
+Create a new workflow file in your repository at `.github/workflows/pipelines-drift-detection.yml`.
 
-This is the same directory where your other Pipelines workflows are located.
+This directory is the same location as your other Pipelines workflows.
 
-Add the following content to the workflow
+Add the following content to the workflow:
 
 ```yml
 name: Pipelines Drift Detection
@@ -51,7 +51,7 @@ jobs:
       branch-name: ${{ inputs.branch-name }}
 ```
 
-Commit the changes to the repository. If you are using [branch protection](/2.0/docs/pipelines/installation/branch-protection) (highly  recommended) you will need to create a new pull request to add the workflow.
+Commit the changes to the repository. If [branch protection](/2.0/docs/pipelines/installation/branch-protection) is enabled—which is strongly recommended—you must create a new pull request to incorporate the workflow into your repository.
 
 <PersistentCheckbox id="install-drift-2" label="Workflow File Created" />