fix: Fixing URL for pipelines machine users install

Author: yhakbar

docs/2.0/docs/accountfactory/architecture/security-controls.md

@@ -79,7 +79,7 @@ Requires the following tokens be created:
 - `INFRA_ROOT_WRITE_TOKEN`: Fine-grained PAT with read/write access to infrastructure repositories
 - `ORG_REPO_ADMIN_TOKEN`: Fine-grained PAT with admin access for repository management
 
-See [Setup via Machine Users](/2.0/docs/pipelines/installation/viamachineusers.md) for more details.
+See [Setup via Machine Users](/2.0/docs/pipelines/installation/viamachineusers) for more details.
 
 </TabItem>
 <TabItem value="gitlab" label="GitLab">

docs/2.0/docs/accountfactory/installation/addingnewrepo.md

@@ -23,7 +23,7 @@ Navigate to the template repository and select **Use this template** -> **Create
 
 Use the Gruntwork.io GitHub App to [add the repository as an Infra Root repository](/2.0/docs/pipelines/installation/viagithubapp#configuration).
 
-If using the [machine user model](/2.0/docs/pipelines/installation/viamachineusers.md), ensure the `INFRA_ROOT_WRITE_TOKEN` (and `ORG_REPO_ADMIN_TOKEN` for enterprise customers) is added to the repository as a secret or configured as an organization secret.
+If using the [machine user model](/2.0/docs/pipelines/installation/viamachineusers), ensure the `INFRA_ROOT_WRITE_TOKEN` (and `ORG_REPO_ADMIN_TOKEN` for enterprise customers) is added to the repository as a secret or configured as an organization secret.
 
 ## Updating the Bootstrap Workflow
 

docs/2.0/docs/pipelines/architecture/security-controls.md

@@ -47,7 +47,7 @@ Requires that the following tokens are created:
 - `INFRA_ROOT_WRITE_TOKEN`: Fine-grained PAT with read/write access to infrastructure repositories
 - `ORG_REPO_ADMIN_TOKEN`: Fine-grained PAT with admin access for repository management
 
-See [Setup via Machine Users](/2.0/docs/pipelines/installation/viamachineusers.md) for more details.
+See [Setup via Machine Users](/2.0/docs/pipelines/installation/viamachineusers) for more details.
 
 </TabItem>
 <TabItem value="gitlab" label="GitLab">

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

@@ -86,7 +86,7 @@ Pipelines needs the ability to interact with Source Control Management (SCM) pla
 There are two ways to configure SCM access for Pipelines:
 
 1. Using the [Gruntwork.io GitHub App](/2.0/docs/pipelines/installation/viagithubapp#configuration) (recommended for most GitHub users).
-2. Using a [machine user](/2.0/docs/pipelines/installation/viamachineusers.md) (recommended for GitHub users who cannot use the GitHub App).
+2. Using a [machine user](/2.0/docs/pipelines/installation/viamachineusers) (recommended for GitHub users who cannot use the GitHub App).
 
 :::note Progress Checklist
 

docs/2.0/docs/pipelines/installation/addingnewgitlabrepo.md

@@ -13,8 +13,8 @@ To use Gruntwork Pipelines in an **existing** GitLab repository, see this [guide
 Before you begin, make sure you have:
 
 - Basic familiarity with Git, GitLab, and infrastructure as code concepts
-- Completed the [AWS Landing Zone setup](/2.0/docs/pipelines/installation/prerequisites/awslandingzone)
-- Have programmatic access to the AWS accounts created in the [AWS Landing Zone setup](/2.0/docs/pipelines/installation/prerequisites/awslandingzone)
+- Completed the [AWS Landing Zone setup](/2.0/docs/accountfactory/prerequisites/awslandingzone)
+- Have programmatic access to the AWS accounts created in the [AWS Landing Zone setup](/2.0/docs/accountfactory/prerequisites/awslandingzone)
 - Completed the [Pipelines Auth setup for GitLab](/2.0/docs/pipelines/installation/viamachineusers#gitlab) and setup a machine user with appropriate PAT tokens
 - Local access to Gruntwork's GitHub repositories, specifically the [architecture catalog](https://github.com/gruntwork-io/terraform-aws-architecture-catalog/)
 

docs/2.0/docs/pipelines/installation/addingnewrepo.mdx

@@ -23,7 +23,7 @@ Pipelines needs the ability to interact with Source Control Management (SCM) pla
 There are two ways to configure SCM access for Pipelines:
 
 1. Using the [Gruntwork.io GitHub App](/2.0/docs/pipelines/installation/viagithubapp#configuration) (recommended for most GitHub users).
-2. Using a [machine user](/2.0/docs/pipelines/installation/viamachineusers.md) (recommended for GitHub users who cannot use the GitHub App).
+2. Using a [machine user](/2.0/docs/pipelines/installation/viamachineusers) (recommended for GitHub users who cannot use the GitHub App).
 
 :::note Progress Checklist
 

docs/2.0/docs/pipelines/installation/authoverview.md

@@ -12,7 +12,7 @@ Gruntwork Pipelines requires authentication with Source Control Management (SCM)
 Gruntwork provides two authentication methods:
 
 - [The Gruntwork.io GitHub App](/2.0/docs/pipelines/installation/viagithubapp.md)
-- [CI Users (Machine Users)](/2.0/docs/pipelines/installation/viamachineusers.md)
+- [CI Users (Machine Users)](/2.0/docs/pipelines/installation/viamachineusers)
 
 Both approaches support the core functionality of Pipelines. The GitHub App provides additional features and benefits, making it the recommended method for most customers that can use it. While Gruntwork strives to ensure feature parity between the two authentication mechanisms, certain advanced features are exclusive to the GitHub App, and this list is expected to grow over time.
 

docs/2.0/docs/pipelines/installation/viagithubapp.md

@@ -132,7 +132,7 @@ The following features of the Gruntwork.io GitHub App will be unavailable during
 
 ### Fallback
 
-In order to ensure that the availability of the Gruntwork.io GitHub App is not something that can impair the ability of users to drive infrastructure updates, users can also authenticate with GitHub using [Machine users](/2.0/docs/pipelines/installation/viamachineusers.md).
+In order to ensure that the availability of the Gruntwork.io GitHub App is not something that can impair the ability of users to drive infrastructure updates, users can also authenticate with GitHub using [Machine users](/2.0/docs/pipelines/installation/viamachineusers).
 
 Configuring the `PIPELINES_READ_TOKEN`, `INFRA_ROOT_WRITE_TOKEN` and `ORG_REPO_ADMIN_TOKEN` where necessary (following the documentation linked above) will result in Pipelines using the machine users mechanism to authenticate with GitHub, rather than the Gruntwork.io GitHub App.