fix: Addressing easy to address PR feedback

Author: yhakbar

docs/2.0/docs/pipelines/installation/addingexistinggitlabrepo.mdx

@@ -65,7 +65,7 @@ Review your existing project structure and identify:
 
 For each AWS Account / Azure Subscription you want to manage, you might already have some or all of the following resources provisioned.
 
-<Tabs>
+<Tabs groupId="cloud-provider">
 <TabItem value="aws" label="AWS" default>
 
 **Required AWS Resources:**
@@ -96,9 +96,9 @@ For each AWS Account / Azure Subscription you want to manage, you might already
 
 ## Configuring SCM Access
 
-Pipelines needs the ability to interact with Source Control Management (SCM) platforms to fetch resources (e.g. IaC code, reusable CI/CD code and the Pipelines binary itself).
+Pipelines needs the ability to interact with GitLab to fetch resources (e.g. IaC code, reusable CI/CD code and the Pipelines binary itself).
 
-For GitLab, you'll need to configure SCM access using [machine users](/2.0/docs/pipelines/installation/viamachineusers) with appropriate Personal Access Tokens (PATs).
+To create machine users for GitLab access, follow our [machine users guide](/2.0/docs/pipelines/installation/viamachineusers) to set up the appropriate Personal Access Tokens (PATs) with the required permissions.
 
 :::note Progress Checklist
 
@@ -186,7 +186,7 @@ mise use -g terragrunt@latest opentofu@latest
 
 ### Cloud-specific bootstrap instructions
 
-<Tabs>
+<Tabs groupId="cloud-provider">
 <TabItem value="aws" label="AWS" default>
 
 The resources you need provisioned in AWS to start managing resources with Pipelines are:
@@ -253,7 +253,7 @@ EOF
 
 If you don't have a `root.hcl` file, you might need to customize the bootstrapping process, as the Terragrunt scale catalog expects a `root.hcl` file in the root of the project. Please contact [Gruntwork support](/support) for assistance if you need help.
 
-For each AWS account that needs bootstrapping, we'll use Boilerplate to scaffold the necessary content.
+For each AWS account that needs bootstrapping, we'll use Boilerplate to scaffold the necessary content. Run this command from the root of your project for each account:
 
 ```bash
 boilerplate \
@@ -263,6 +263,12 @@ boilerplate \
 
 :::tip
 
+You'll need to run this boilerplate command once for each AWS account you want to manage with Pipelines. Boilerplate will prompt you for account-specific values each time.
+
+:::
+
+:::tip
+
 You can reply `y` to all the prompts to include dependencies, and accept defaults unless you want to customize something.
 
 Alternatively, you could run Boilerplate non-interactively by passing the `--non-interactive` flag. You'll need to supply the relevant values for required variables in that case.
@@ -405,7 +411,7 @@ The process that we'll follow to get these resources ready for Pipelines is:
 {/* We're using an h3 tag here instead of a markdown heading to avoid adding content to the ToC that won't work when switching between tabs */}
 <h3>Bootstrap Your Project for Azure</h3>
 
-For each Azure subscription that needs bootstrapping, we'll use Boilerplate to scaffold the necessary content.
+For each Azure subscription that needs bootstrapping, we'll use Boilerplate to scaffold the necessary content. Run this command from the root of your project for each subscription:
 
 ```bash
 boilerplate \
@@ -415,6 +421,12 @@ boilerplate \
 
 :::tip
 
+You'll need to run this boilerplate command once for each Azure subscription you want to manage with Pipelines. Boilerplate will prompt you for subscription-specific values each time.
+
+:::
+
+:::tip
+
 You can reply `y` to all the prompts to include dependencies, and accept defaults unless you want to customize something.
 
 Alternatively, you could run Boilerplate non-interactively by passing the `--non-interactive` flag. You'll need to supply the relevant values for required variables in that case.
@@ -676,7 +688,7 @@ Next, you'll want to define the environments you want to manage with Pipelines u
 
 For each environment, you'll want to define a [`filter` block](/2.0/reference/pipelines/configurations-as-code/api#filter-block) that tells Pipelines which units are part of that environment. You'll also want to define an [`authentication` block](/2.0/reference/pipelines/configurations-as-code/api#authentication-block) that tells Pipelines how to authenticate with your cloud provider(s) for that environment.
 
-<Tabs>
+<Tabs groupId="cloud-provider">
 <TabItem value="aws" label="AWS" default>
 
 ```hcl title=".gruntwork/environment-production.hcl"

docs/2.0/docs/pipelines/installation/addingexistingrepo.mdx

@@ -50,7 +50,7 @@ Review your existing repository structure and identify:
 
 For each AWS Account / Azure Subscription you want to manage, you might already have some or all of the following resources provisioned.
 
-<Tabs>
+<Tabs groupId="cloud-provider">
 <TabItem value="aws" label="AWS" default>
 
 **Required AWS Resources:**
@@ -174,7 +174,7 @@ mise use -g terragrunt@latest opentofu@latest
 
 ### Cloud-specific bootstrap instructions
 
-<Tabs>
+<Tabs groupId="cloud-provider">
 <TabItem value="aws" label="AWS" default>
 
 The resources you need provisioned in AWS to start managing resources with Pipelines are:
@@ -241,7 +241,7 @@ EOF
 
 If you don't have a `root.hcl` file, you might need to customize the bootstrapping process, as the Terragrunt scale catalog expects a `root.hcl` file in the root of the repository. Please contact [Gruntwork support](/support) for assistance if you need help.
 
-For each AWS account that needs bootstrapping, we'll use Boilerplate to scaffold the necessary content.
+For each AWS account that needs bootstrapping, we'll use Boilerplate to scaffold the necessary content. Run this command from the root of your repository for each account:
 
 ```bash
 boilerplate \
@@ -251,6 +251,12 @@ boilerplate \
 
 :::tip
 
+You'll need to run this boilerplate command once for each AWS account you want to manage with Pipelines. Boilerplate will prompt you for account-specific values each time.
+
+:::
+
+:::tip
+
 You can reply `y` to all the prompts to include dependencies, and accept defaults unless you want to customize something.
 
 Alternatively, you could run Boilerplate non-interactively by passing the `--non-interactive` flag. You'll need to supply the relevant values for required variables in that case.
@@ -374,7 +380,7 @@ The process that we'll follow to get these resources ready for Pipelines is:
 {/* We're using an h3 tag here instead of a markdown heading to avoid adding content to the ToC that won't work when switching between tabs */}
 <h3>Bootstrap Your Repository for Azure</h3>
 
-For each Azure subscription that needs bootstrapping, we'll use Boilerplate to scaffold the necessary content.
+For each Azure subscription that needs bootstrapping, we'll use Boilerplate to scaffold the necessary content. Run this command from the root of your repository for each subscription:
 
 ```bash
 boilerplate \
@@ -384,6 +390,12 @@ boilerplate \
 
 :::tip
 
+You'll need to run this boilerplate command once for each Azure subscription you want to manage with Pipelines. Boilerplate will prompt you for subscription-specific values each time.
+
+:::
+
+:::tip
+
 You can reply `y` to all the prompts to include dependencies, and accept defaults unless you want to customize something.
 
 Alternatively, you could run Boilerplate non-interactively by passing the `--non-interactive` flag. You'll need to supply the relevant values for required variables in that case.
@@ -643,7 +655,7 @@ Next, you'll want to define the environments you want to manage with Pipelines u
 
 For each environment, you'll want to define a [`filter` block](/2.0/reference/pipelines/configurations-as-code/api#filter-block) that tells Pipelines which units are part of that environment. You'll also want to define an [`authentication` block](/2.0/reference/pipelines/configurations-as-code/api#authentication-block) that tells Pipelines how to authenticate with your cloud provider(s) for that environment.
 
-<Tabs>
+<Tabs groupId="cloud-provider">
 <TabItem value="aws" label="AWS" default>
 
 ```hcl title=".gruntwork/environment-production.hcl"